How-to guide · LocalPDF
How to compress a PDF under 1MB (without uploading)
Some job boards, visa portals, and app forms cap attachments at 1MB — half the common 2MB limit. Hitting that number with a multi-page scan is hard if every online tool wants your file first. This guide shows a private, browser-only path with LocalPDF Compress, plus what to do when Strong compression still leaves you over 1MB.
By: LocalPDF Team · Updated 2026-07-31
Step-by-step
- Open LocalPDF Compress PDF on https://www.openlocalpdf.com/compress/ (www canonical).
- Drop your PDF into the browser. It is read locally — not uploaded for processing.
- If the packet is long, open Split first and export only the pages the form lists.
- On Compress, choose Strong. Click Compress PDF and wait for local re-encode.
- Check the size summary. If still over 1MB, remove more pages or rescan, then retry Strong.
- Open the result at 100% zoom, verify critical text, then upload to the portal.
Advertisement
1MB vs 2MB: why the limit feels brutal
A 1MB cap is often aimed at mobile apps or legacy portals. One phone photo embedded in a PDF can already be 2–4MB before you add a second page. Text-only exports may already be under 1MB; image-heavy scans almost never are without re-encoding.
Treat 1MB as a hard engineering limit, not a quality target. You will trade resolution. The goal is a readable signature and legible print — not archival photo quality.
- 1MB ≈ strict mobile / some visa & scholarship forms
- 2MB ≈ many government and university uploads
- Email is often 10–25MB — do not over-compress for email alone
Why browser-only compression matters at 1MB
When the file is an ID, bank letter, or medical form, uploading to a random compressor is the wrong trade for a few hundred kilobytes. LocalPDF re-encodes pages in your tab with client-side libraries so processing bytes never need to hit our origin.
You still load the static site over HTTPS like any web app. The privacy wedge is simple: the PDF content is not posted to a conversion API.
A practical recipe to land under 1MB
Start with the fewest pages the form actually needs. Then compress Strong. If still over, split out optional annexes or rescan at lower DPI.
- Delete blank and duplicate pages before compressing
- Use Split to keep only required pages (often 1–3)
- Run Compress on Strong; inspect signatures at 100% zoom
- If still >1MB: rescan at 150 DPI grayscale when you control the source
- Avoid re-compressing an already heavily JPEG-based PDF twice without splitting
Quality checks before you submit
Open the download and zoom names, dates, and stamps. If text is muddy, you may need fewer pages rather than harsher compression. Portals reject unreadable IDs even when the size is perfect.
Keep the original file. 1MB workflows are lossy by design; you may need a second attempt with different page sets.
When 1MB is impossible in one file
A 20-page color scan will not magically become 1MB and stay crisp. Ask whether the portal allows multiple uploads, or whether an official lower-DPI template exists. Sometimes the honest answer is two files or a fresh scan.
FAQ
Can every PDF go under 1MB? +
No. Long color scans may stay above 1MB even on Strong. Reduce page count or source DPI first.
Is this free and private? +
Yes for personal use. Compression runs in your browser with no LocalPDF account. Ads may appear after AdSense approval; file processing still does not upload to our servers.
Should I always use Strong? +
For a hard 1MB cap, yes start Strong. If the form allows 2MB, Balanced often looks better.
Why did a text PDF barely shrink? +
Vector text PDFs are already efficient. Rasterizing them can even grow size. Split image pages instead of crushing clean text.
Does LocalPDF store my file? +
Processing is in-tab. Closing the tab clears the working copy from that session.
What is different from Smallpdf-style tools? +
Many compressors upload first. LocalPDF’s wedge is no-upload processing for privacy-sensitive packets.