Drop your PDF files here
or click to browse · Up to 20 files at once
PDFMax ~100MB per file
No upload · 100% private
All tools
Atlassian Cloud often caps ticket files near 10 MB. Compress design dumps here with a locked Web preset, then attach on the issue — nothing uploaded to us.
Drop your PDF files here
or click to browse · Up to 20 files at once
Product specs, log dumps, and design exports headed for a Jira ticket often contain roadmap details that should not sit on a stranger’s compress server for “an hour.” This page shrinks the file in the browser with a Web preset aimed at Atlassian Cloud’s common 10 MB per-file limit.
The document is re-encoded in tab memory and never reaches VeloTools. You download the trimmed PDF and attach it on the issue yourself, keeping internal work off unknown SaaS.
Annotations are stripped by default here because a Jira attachment is usually a snapshot for the ticket, not a live review thread — a deliberate contrast with review-oriented mail presets.
Atlassian Cloud commonly caps a single Jira attachment near 10 MB, though site admins can change it. Export a few Figma frames or a verbose log-to-PDF and the ticket rejects the upload just as you are trying to unblock a teammate.
People respond by pasting screenshots into the description, which scatters the detail and makes the issue harder to search later. A locked Web pass keeps the artefact as one attached PDF that reviewers can open in context.
Because the cap is per file rather than a message budget, the fix is straightforward: trim the export under 10 MB before it ever touches the issue.
| Problem it solves | Jira attachment over the 10 MB limit |
|---|---|
| Size check | 10 MB common Atlassian Cloud cap |
| Preset | Web · 96 DPI · 57% JPEG |
| Annotations | Stripped for a clean ticket snapshot |
| Privacy | Local only before the issue attach |
| Sibling pages | Confluence · Asana |
A ticket attachment is typically evidence — a rendered spec or a captured log — rather than a document people redline in place. Dropping the annotation stream shaves weight that would only pad the file and rarely carries meaning inside the issue.
If a particular attachment really is a review artefact, keep the markup by compressing on a preset that preserves annotations instead, such as the Confluence or Box routes, and attach that copy to the ticket.
The 10 MB per-file ceiling makes Jira a per-attachment problem rather than a mailbox one, so the tactic is simply to land each export under the line before upload. Fewer exported frames often beats a harsher quality setting.
Its closest sibling is the Confluence page, which shares the ~10 MB neighbourhood but tunes for embeds that must not stall the editor. For task boards where mobile openability matters more than a hard cap, the Asana page is the better match.
When a spec is genuinely large, divide it with Split PDF and attach the relevant section, or run one more pass on Compress PDF with a firmer preset.
Everything else — merge, reorder, unlock — sits under PDF tools once the ticket accepts the file.
I keep this page because PDF attachment limits for Jira kept failing with upload tools or generic presets. Here you pick the Screen/Web preset that fits the channel, compress locally, then attach. Limits and architecture are documented in Lab Notes — this URL is a micro-instrument for one job, not a keyword clone.