Compress PDF Online

PDFs embed fonts, high-resolution photos, vector graphics, and sometimes entire spreadsheets as images. Scanners often produce 300 DPI color pages that look crisp on screen but balloon file size. Multiple edits can leave orphaned objects in the file that no longer display yet still occupy bytes.

Compression rewrites or simplifies these streams. Lossless techniques remove duplication and apply Flate encoding. Lossy steps downsample images when you accept moderate quality trade-offs for much smaller output.

Not every PDF compresses dramatically. A text-only export from Word may already be tiny; a photography portfolio may shrink only if image quality is reduced. Set expectations based on content type.

Color scans consume more bytes than monochrome forms. Converting color scans to grayscale in the scanner app before PDF creation often beats compressing a full-color file after the fact.

Linearized PDFs optimized for web fast-start may re-save differently than non-linearized archives—either form compresses, but compare open time in browsers if you distribute widely.

Recommended balance suits most office documents: forms, letters, mixed text and screenshots. Extreme compression chases minimum bytes for web previews or strict attachment limits. Light compression preserves near-original image sharpness when you mainly need a modest trim.

If a portal specifies a megabyte cap, compress once at recommended, check size, then retry at a stronger level only if needed. Repeated extreme passes rarely help text-heavy files but can visibly soften photos.

Target-size options, when available, iterate toward a goal file weight. They are guides, not guarantees—highly graphical PDFs may not reach an aggressive target without unacceptable blur.

• Recommended: everyday email attachments and intranet uploads
• Less compression: presentations with fine charts or maps
• Extreme: maximum shrink when visual fidelity is secondary
• Re-compress only when the first pass missed your size goal

Page count, reading order, and selectable text should remain unless the compressor rasterizes pages—a approach this tool avoids for standard documents. Bookmarks and hyperlinks usually persist, though poorly formed links in the source may still break.

Password protection is applied after compression, not before. Compress an unencrypted file, verify readability, then use the protect tool if you need AES encryption on the smaller output.

PDF/A archival compliance can be lost if compression strips required metadata or embeds incompatible color profiles. For regulated archives, validate against your compliance checker after compressing.

Financial statements, HR records, and unreleased designs benefit from local processing. No queue, no retention policy to read—files exist in memory only for the session.

Because work happens client-side, speed scales with your CPU. A fan-heavy laptop moment is normal on hundred-page scanned books. Close unused tabs to free RAM before starting.

If a scan is fundamentally oversized, re-scan at lower DPI or grayscale before compressing. Splitting a deck into two PDFs beats over-compressing slides until text is illegible.

Compare before-and-after on a representative page zoomed to 100%. If chart labels blur, step down to a lighter compression preset or split the file instead of pushing quality further.

Job applicants compress portfolio PDFs before applicant tracking systems reject oversized uploads. Check readability of typography on the first page after compression—recruiters notice blurry headers faster than they notice file size.

Nonprofits compress annual reports for email newsletters while keeping print-ready masters archived losslessly on internal drives. Two versions—web and print—prevent quality compromises on the version donors actually frame.

Developers compress generated PDF invoices in CI artifacts before attaching to ticket systems with storage quotas. Script the human review step until you trust preset levels for your template.

When compression barely shrinks a file, the PDF may already be optimized or consist mostly of vector text. Investigate embedded high-resolution images in the authoring app instead of expecting miracles from another pass.

Compare original and compressed byte sizes side by side before distributing. Percentage reduction matters less than clearing a concrete gate—under 10 MB for Gmail, under 25 MB for many portals.

Listen for stakeholder feedback on chart legibility after aggressive presets. Operations teams accept smaller files; executives reject slides where axis labels require squinting in conference rooms.

Archive masters uncompressed on durable storage; compress only distribution copies. Future re-edits start from lossless sources rather than re-compressing already lossy outputs.

Batch compress quarterly report folders during off-peak hours on desktop machines. Laptops on battery may throttle CPU and stretch processing time for hundred-megabyte archives.

Document which preset you used in file metadata or folder README notes so colleagues do not re-compress an already optimized copy expecting further gains.

Scanned books compress well; vector annual reports compress modestly. Set expectations in team wikis so colleagues do not blame the tool when a text-only export shrinks only five percent.

Print shops sometimes request uncompressed masters—compress only the email-friendly copy you send clients, not the plate-ready file destined for offset presses.