Local processing · GDPR-friendly

Compress PDF — smaller without uploading.

Reduces file size by 70–90% on average. Your PDF is re-encoded locally in the browser — no server, no cloud, no upload wait. Finally fits in every email and portal.

~80%
Typical savings
150 DPI
Screen reading
0 B
Uploaded

PDF Compressor

Drop your PDF — we'll show you instantly how much smaller it gets.

↓

Drop PDF here

or click to browse — .pdf

See all PDF tools →

Why this PDF compressor?

Real size savings. Zero data risk. No upload wait.

🔒

Confidential stays confidential

Contracts, HR files, tax records, client documents — none of it leaves your browser. There's technically no upload, so nothing can be leaked, logged, or read by anyone else.

📧

Fits any mail limit

Gmail (25 MB), Outlook (20 MB), Yahoo (25 MB), iCloud Mail (20 MB) — but your recipients' inboxes are stricter. 5 to 10 MB is the realistic ceiling, and we almost always land below it.

🏛️

Portal-friendly

USCIS uploads, IRS Form-fillable PDFs, Common App, Workday, Greenhouse, SAP SuccessFactors — most expect 5 to 10 MB per attachment. Compression saves the awkward split into multiple uploads.

🎯

70 to 90 percent smaller

Each page is rendered at 150 DPI and re-embedded as JPEG at quality 65. The ratio between readability and file size hits the sweet spot that crushes scan-heavy PDFs the most.

⚡

Instant savings preview

After compression you immediately see the saved percentage and the new file size. No guessing — you know right away whether you're under your target.

♾️

Unlimited, no account

No daily quotas like the classic online PDF services, no "upgrade for more" wall, no email verification. Run a hundred invoices through it back-to-back.

How to compress a PDF

Drag, click, save.

1

Drop the PDF

Drag it into the drop zone or pick it from the file dialog. The file lands only in your browser memory.

2

Compress

Click "Compress now". Each page is rendered separately and re-embedded as a JPEG at reduced density into a new PDF.

3

See savings & save

Status line shows the percentage saved. One click saves the new file with a `_compressed` suffix.

Real-world use cases

Where PDF compression actually matters in the US/global context.

💼

Job applications as a single PDF

Workday, Greenhouse, Lever, BambooHR, Common App and most ATS portals accept just one file, often with a 5 MB limit. A combined résumé + cover letter + transcripts blow past that fast — compression saves the application.

🏛️

IRS, USCIS, FAFSA, state portals

The IRS upload limit for taxpayer-supplied PDFs is around 7 MB. USCIS evidence PDFs: 6 MB per file. FAFSA tax docs: 4 MB. Smartphone-scanned receipts get to 20–30 MB instantly — one compress run puts them under the cap.

⚖️

Law firms and accountants

Court e-filing systems, IRS e-file, CPA workpapers — all have strict attachment limits. Confidential client data must not pass through unknown cloud compressors (state-bar ethics rules, IRS Circular 230). Local compression is the clean path.

📚

University paper submissions

Universities accept dissertations and theses via Canvas, Blackboard, or Brightspace — typically 20 MB ceilings, sometimes 10 MB. Papers with embedded source scans, charts, and appendices hit 30+ MB easily. Compress before submission.

🛒

Sharing invoices and contracts

Freelancers, contractors, small businesses — every invoice with a scanned letterhead bloats. Recipients on slow or capped internet (or on phones) thank you for sending 800 KB instead of 12 MB.

📱

WhatsApp, Telegram, iMessage

WhatsApp caps document attachments at 100 MB, iMessage at 100 MB on iCloud-linked accounts, Telegram at 2 GB. The number isn't the issue — recipients on mobile data won't download 30 MB PDFs. Compressed = actually opened.

Frequently asked questions

Typically 70 to 90 percent smaller. A 20-MB invoice with embedded scans usually lands at 2 to 4 MB. Pure text PDFs shrink less (often 30–50 percent) because they were already compact. The exact ratio is shown right after compression.

Yes. Each page is rendered at 150 DPI and encoded as JPEG at quality 65. That's the threshold where body text down to 8 pt remains crisp. It's perfect for email attachments, screen reading, and government upload portals — only A3 print posters would need more.

Embedded photos are re-encoded at JPEG quality 65. For illustrations, scanned receipts, and screenshots that's a great trade. If you have print-grade halftones or line art, keep the original and only compress the email copy.

No. Because each page is re-embedded as an image, clickable links, form fields, and bookmarks are lost. If you need editable structure, use a PDF editor for targeted cleanup instead of raster recompression.

Compress once — in 95 percent of cases the file is under the limit afterward. If not, see whether you can reduce page count (blank pages, ad pages, repetitive boilerplate). For very large scan stacks, split the PDF into two parts and submit them separately.

No. The whole process runs in your browser via pdf.js and pdf-lib. Your PDF is never sent to a server, cloud, or third party. You can even load this page offline once and it keeps working — the best proof.

Yes. Because no data reaches our infrastructure, there is no data-processor relationship to manage. That makes it particularly suitable for law firms, accountants, healthcare staff, HR teams, and any context where confidential documents must stay on the device.

Yes — iPhone, Android, tablet, Chromebook. Very large PDFs (over 50 MB) can hit browser memory limits on older devices; in that case compress on a desktop first.

Compress PDF without the data risk

PDFs get large fast in modern workflows. A single smartphone scan of a letter-sized page is often 2 to 5 MB; a ten-page job application bundle can easily run 30 MB — and bounce off email and portal size limits the moment you try to send it. Our online PDF compressor solves that without making you trust a stranger's cloud. The compression runs entirely in your browser via the JavaScript libraries pdf.js and pdf-lib.

How the compression actually works

We open your PDF with pdf.js and render each page to a canvas at 150 DPI (1.5× the typical PDF native resolution of 100 DPI). Each canvas is encoded as JPEG at quality 0.65 and embedded into a new PDF via pdf-lib — one JPEG per page. This image-pipeline approach is much more aggressive than pure stream-filter compression (Flate, LZW) and is the reason scan- and image-heavy PDFs shrink so dramatically.

When this method is great — and when it isn't

Great for: scanned applications, photographed receipts, screenshots, spec sheets with embedded diagrams. Not great for: PDFs with fillable form fields (fields are lost), interactive bookmarks, clickable tables of contents, or machine-readable text for screen readers. For those, use a PDF editor to remove content selectively instead of running raster recompression.

Why compress in the browser instead of online?

Classic online compressors upload your file to a server in Ireland, the US, or India, process it there, and send the result back. Three problems: first it's slow (twice the full file size over the wire), second it creates server logs, third you have to trust the provider's privacy policy. With BrowserCrunch none of that happens — no upload means no wait, no log, and no policy question.

Common size limits worth knowing

Reference values: Gmail / Outlook attachment: 20–25 MB. Yahoo, iCloud Mail: 20–25 MB. IRS Document Upload Tool: about 7 MB per file. USCIS evidence upload: 6 MB. FAFSA: about 4 MB. Workday application: 5 MB. Common App: 500 KB per essay PDF. Greenhouse / Lever: 5 MB. ProQuest dissertations: 1 GB max. PACER court filings: 35 MB max. Most of these limits are reachable in a single compression run.

Free, no account, no watermarks

No daily quota. No premium wall. No "verify your email for the pro version". No watermarks in the output. The page is free because it has no recurring server cost — your browser CPU does the work, not ours. That's the model behind client-side processing.