Your files never leave your device. All processing happens locally in your browser.
How do I compress a PDF to 1MB (under 1 MB) online without uploading the file?
Open Compress PDF to 1MB and drop your PDF onto the page — the target is already locked to 1 MB (1024 KB), so there is nothing to configure. The tool renders every page in your browser with Mozilla’s pdf.js, re-encodes the images at a lower resolution and JPEG quality where needed and rebuilds the document with pdf-lib, aiming to land at or just under 1 MB. Because 1 MB is the most generous of the common upload caps — far roomier than 200 KB, 300 KB or 500 KB — the compression is very gentle: most text PDFs are already under 1 MB and pass almost untouched, and even a multi-page colour scan usually fits while staying crisp and keeping its text selectable, because whole pages rarely need to be rebuilt as images to reach so roomy a target. It produces three quality variants in one pass — Best Quality, Balanced and Smallest — and marks each with a check when it meets the 1 MB cap, then shows the before/after sizes and the exact percentage saved. Only a very heavy scanned or image-packed file is squeezed hard, and if it still cannot reach 1 MB the tool tells you the smallest size it achieved. Everything runs in the tab, so nothing is uploaded and your PDF never leaves your device; the result downloads as your file name with a -compressed.pdf suffix.
Target locked to 1 MB (1024 KB) — drop a PDF and it compresses to fit that cap, with no settings to pick
Three quality variants in one pass (Best Quality, Balanced, Smallest), each tagged with a check when it lands under 1 MB
The most generous common target, so compression is very gentle — scans stay crisp and text usually stays selectable
Runs entirely in the browser with pdf.js and pdf-lib — no upload, no install, no account
Ideal for CV / resume and document uploads on job portals, visa and university application forms that cap files at 1 MB — and a safe margin under a 2 MB limit
What is
Compress PDF to 1MB
Compressing a PDF to 1MB means reducing the document’s file size until it is at or under 1 megabyte (1024 kilobytes) — one of the most common single-file upload ceilings on the web, used by job portals for CVs and resumes, visa and immigration forms, university admission systems, court e-filing and older web platforms, and a comfortable margin under a 2 MB cap. Because most of a PDF’s weight is usually its images and scanned pages, a compressor reaches such a target mainly by down-sampling those images to a lower resolution (DPI) and re-encoding them with lossy JPEG compression; stripping metadata and converting pages to grayscale free up further bytes. At 1 MB the compression is far gentler than at 200 KB, 300 KB or 500 KB, so a scanned certificate stays sharp and a lighter document usually meets the cap without whole pages being rasterised, keeping its text selectable and searchable. Whether 1 MB is achievable is rarely in doubt: a text-only PDF is almost always already under 1 MB, and most multi-page or colour scans reach it comfortably; only a long scan packed with photographs may bottom out somewhat above 1 MB before the pages become unreadable. This tool locks the target to 1 MB, renders the pages with Mozilla’s pdf.js and rebuilds the file with pdf-lib entirely on your device, so no cloud service is involved and the PDF is never uploaded.
No. The PDF is read and compressed to 1 MB entirely in your browser, so the file never leaves your device — there is no upload, server or account.
Nothing is uploaded. When you drop or pick a PDF, the tool reads it locally with the browser’s File API, renders its pages in memory with the pdf.js engine (whose worker is bundled locally, not fetched from a CDN) and rebuilds the compressed file with the pdf-lib library on your own machine. There is no server, upload, database, API or tracking in the processing path, so CVs, certificates, ID scans, visa paperwork and other private documents you are shrinking for a form stay on your device; the tool works offline once cached, and closing the tab discards everything. The only optional network use anywhere on the site is consent-gated advertising, which never sees your files.
Rarely. 1 MB is a very roomy target, so the compression is gentle: most PDFs fit with their text left live and selectable, and scans stay sharp — only a heavy image-packed file that has to be rasterised to hit the cap loses selectable text.
Reaching a target uses lossy compression — images are down-sampled to a lower DPI and re-encoded as JPEG, which is how a large file becomes small. But 1 MB leaves far more room than a 200 KB, 300 KB or 500 KB cap, so the downward sweep usually stops very early or is not needed at all: a text-only PDF is often already under 1 MB and passes almost untouched, scans stay noticeably crisp, and most documents meet 1 MB without whole pages being rebuilt as images, which keeps their text selectable and searchable. Three variants are generated in one pass (Best Quality, Balanced and Smallest) and the tool defaults to the best one that still fits. One honest note: when a very heavy, photo-laden document does need its pages rasterised to reach 1 MB, the text on those pages becomes part of the picture and is no longer selectable; if you need the text to stay live on such a file, a 2 MB target or a lossless PDF tool is gentler still. For almost every document headed to a 1 MB upload box, the result stays perfectly legible.
Almost always, yes. 1 MB is generous, so text PDFs are usually already under it and most multi-page or colour scans reach it easily; only a long photo-heavy scan may bottom out a little above 1 MB, in which case the smallest size achieved is shown.
It depends on what is inside the PDF, but 1 MB is one of the easiest common targets to hit. The real savings come from re-encoding images, so a text-only or lightly formatted document usually already weighs less than 1 MB and needs little or no compression, and a typical certificate, mark sheet or multi-page scan reaches the cap with legibility to spare. A long scan full of photographs still has a floor: past a certain point the pages would turn to mush, so the tool stops at the smallest readable size it can reach and reports that figure with a note rather than producing an unusable file. If you are stuck above 1 MB, enabling grayscale, removing pages you do not need, or splitting the document first will usually get you under the cap. The three variants let you take the Smallest one when you need every byte, or Best Quality — the default — when 1 MB is comfortably met.
1 MB is one of the most common per-file caps on job portals, visa forms and admission systems, and keeps email attachments light — it clears those limits while keeping the document far sharper than a tighter 200 KB or 500 KB squeeze would.
A 1 MB ceiling turns up constantly: many job portals require a CV or resume in PDF under 1 MB, visa and immigration forms and university admission systems cap individual documents at around 1 MB, court e-filing and older web forms reject anything larger, and a sub-megabyte attachment sends and delivers far more reliably than a multi-megabyte one that bounces off an inbox or gateway limit. A flatbed scanner on default settings produces roughly 2–4 MB per full-colour A4 page, so an untouched scan of a transcript, offer letter or ID can still exceed 1 MB — compression is the fastest fix that keeps the whole document. Because 1 MB is the roomiest of the common caps, the tool can compress very gently, so scanned certificates and photos keep their detail and text usually stays selectable while still clearing the field; it is also a safe margin under a 2 MB limit. This tool is built for exactly that: the target is fixed at 1 MB so you can drop the PDF and download a version that clears the limit, without hunting through compression settings. If the portal wants a smaller file, sibling tools target 500 KB, 300 KB and below, and larger presets (2 MB, 3 MB and up) exist for looser limits.
Detailed Explanation
📖How It Works
Compressing a PDF to 1 MB — Entirely in the Browser
Compress PDF to 1MB shrinks a document to a fixed 1 megabyte (1024 KB) target without uploading a single byte. The 1 MB target is read from the page URL and locked, so there is nothing to choose — drop your PDF and the tool goes to work. It renders every page in the browser with Mozilla’s pdf.js, re-encodes the embedded images at a lower resolution and JPEG quality where needed, and rebuilds the file with pdf-lib, aiming to land at or just under 1 MB. Because 1 MB is the most generous of the common upload ceilings — far roomier than 200 KB, 300 KB or 500 KB — the downward sweep of DPI and quality usually stops very early or is not needed at all, so most text PDFs are already under 1 MB and pass almost untouched, scanned pages keep their sharpness, and most documents meet the cap without whole pages being rasterised, leaving their text live and selectable. Three quality variants are produced in a single pass — Best Quality, Balanced and Smallest — and each is tagged with a check when it clears the cap, alongside the original versus new size and the exact percentage saved. Only a very heavy scanned or image-packed file is squeezed hard, and if 1 MB is genuinely out of reach the tool reports the smallest size it achieved rather than producing an unreadable file. Everything runs on your device, so the PDF never leaves the tab.
1 MB (1024 KB) target locked from the URL — drop a PDF, no settings to pick
Renders with pdf.js, re-encodes images at lower DPI/JPEG quality where needed, rebuilds with pdf-lib in the browser
Three variants in one pass (Best Quality, Balanced, Smallest), each marked when it meets 1 MB
The most generous common target, so compression is very gentle — text PDFs often pass almost untouched and scans keep their text selectable; reports the smallest achievable size when a heavy scan cannot reach 1 MB
📋Use Cases
When a 1 MB PDF Is Required
The 1 MB ceiling is one of the most common single-file upload caps on the web. Many job portals require a CV or resume in PDF under 1 MB, visa and immigration application forms and university admission systems cap individual documents at around 1 MB, court e-filing and older web platforms reject anything larger, and email is the everyday case — a sub-megabyte attachment sends and delivers far more reliably than a multi-megabyte scan that bounces off an inbox or gateway limit. The trouble is that a flatbed scanner on default settings produces roughly 2–4 MB for a single full-colour A4 page, so an untouched scan of a transcript, offer letter, ID or proof of residence can still exceed 1 MB; compressing it is the fastest fix that keeps the whole document intact. A 1 MB version clears a 1 MB or 2 MB box while keeping the document far more legible than a 200 KB, 300 KB or 500 KB squeeze would, so it is the sweet spot for CV and resume uploads, application forms and general web submissions where quality still matters. This tool targets that exact number: you drop the PDF and download a version that clears 1 MB, then attach it with confidence. When a portal specifies a tighter cap, 500 KB, 300 KB and smaller tools are one click away, and looser limits (2 MB, 3 MB and beyond) have their own presets.
1 MB is a widespread cap on job-portal CV/resume uploads, visa and immigration forms and university admission systems, and keeps email attachments light enough to send reliably
A default 300 DPI colour scan runs 2–4 MB per A4 page, so even a single-page scan can exceed 1 MB and need compression
Keeps documents far sharper than a 200 KB, 300 KB or 500 KB target while still clearing the field; a safe margin under a 2 MB limit
Sibling presets cover 500 KB, 300 KB and below for tighter caps and 2 MB, 3 MB and up for looser ones
🔧Technical Details
How the 1 MB Target Is Reached
When the page loads at /compress-pdf-to-1mb, a URL parser (getPdfPresetFromPath) extracts the number and unit and fixes the target at 1 MB (targetKB 1024), showing a locked-target banner instead of the usual preset grid. On drop, the PDF is read into an ArrayBuffer with the File API and pdf.js (pdfjs-dist) renders a first-page thumbnail and the page count, its worker bundled with the app locally rather than fetched from a CDN. Smart Compress hands the buffer and options { targetKB: 1024, grayscale, removeMetadata } to the smartCompressPDF routine (src/lib/workerClient.ts), which pursues two strategies and keeps whichever yields the smaller file that still meets 1 MB: it re-encodes the PDF’s embedded images at reduced JPEG quality and scale, and, when a target needs it, rasterises whole pages by having pdf.js paint each page onto an HTML canvas at a chosen DPI, encoding the canvas as JPEG and assembling a fresh PDF from those images with pdf-lib. Because 1 MB is such a roomy ceiling, the sweep of DPI and JPEG quality often stops very early or is skipped entirely — the Best variant frequently lands under the cap with no visible loss, and a lighter or text-only file may already fit with its text left live, so it is kept as the default. Three configurations run in one pass — Best Quality (highest DPI and JPEG quality), Balanced, and Smallest — and metadata is stripped by default. Each variant is measured, tagged when it lands under 1 MB, and the chosen one downloads from a local Blob with a -compressed.pdf suffix.
getPdfPresetFromPath parses the URL and locks the target at 1 MB (targetKB 1024)
pdf.js (pdfjs-dist) reads the page count and renders the thumbnail; its worker is bundled locally, not from a CDN
smartCompressPDF re-encodes images and, when needed, rasterises pages via canvas, rebuilding with pdf-lib
Three variants generated and measured in one pass; the chosen file downloads from a local Blob
⚠️Limitations
Honest Limitations
Whether 1 MB is reachable is rarely in doubt: a text-only PDF is almost always already under 1 MB and needs little or no compression, and because the target is so generous most single- and multi-page scans reach it while staying crisp; but a long scan packed with photographs still has a physical floor, so past a point the tool stops at the smallest legible size it can produce and surfaces a warning naming that figure rather than returning junk. The real savings come from lossy compression, so there is a genuine trade-off — when the tool must rebuild pages as JPEG images to hit the target, the text on those pages becomes part of the picture and no longer selectable or searchable; but 1 MB is roomy enough that most documents meet it without that step, keeping their text live, and when live text matters a 2 MB target is gentler still. Everything runs in browser memory, so a very large or high-page-count PDF is bounded by your device’s RAM, and the tool compresses one PDF at a time rather than a batch. The file must be openable by pdf.js and pdf-lib — a password-protected or corrupt document reports a clear, auto-dismissing error instead of a broken result. If a heavy scan will not fit, enabling grayscale, removing spare pages or splitting the document first usually gets you under the cap.
Text PDFs are usually already under 1 MB and most scans reach it while staying sharp; only a heavy photo-laden scan may bottom out above it, and the smallest achieved size is reported
Aggressive rebuilds rasterise pages, so their text becomes part of the image; at 1 MB most files fit without this, keeping text selectable
In-browser processing bounded by device RAM; one PDF at a time, not a batch
Password-protected or corrupt files report a clear error; grayscale, removing pages or splitting helps a stubborn scan fit
🔒Privacy & Security
Privacy: Your PDF Never Leaves the Tab
The documents people compress for a 1 MB job, visa or admission upload are often the sensitive kind — CVs, transcripts, ID scans, certificates, offer letters, signed forms — and this tool is built so none of it leaves your machine. The file is read with the browser File API, rendered entirely in memory with pdf.js (whose worker is bundled locally, so no third-party CDN is contacted), and the compressed document is rebuilt with pdf-lib on your own device. There is no server, upload, database, logging, API or CDN anywhere in the processing path, and the finished PDF is generated locally and downloaded straight from a Blob. The tool works offline once the page has been cached, and closing the tab discards every byte. There is no login and no telemetry, and the only optional network use anywhere on the site is consent-gated advertising, which never sees your files.
PDF read, rendered and rebuilt entirely in the browser; nothing uploaded
No server, upload, database, API or CDN in the processing path; pdf.js worker bundled locally
Compressed PDF built on-device and downloaded from a local Blob; works offline once cached
No login or telemetry; closing the tab discards everything
Compress PDF to 1MB — target, quality and limits
Capability
Support
Notes
Target size
Locked at 1 MB (1024 KB)
Parsed from the URL; a banner replaces the preset grid so there is nothing to configure
Quality variants
Best, Balanced, Smallest
Three generated in one pass; each tagged with a check when it lands at or under 1 MB
Method
Image re-encode + page rasterise
pdf.js renders pages, images are down-sampled and JPEG-re-encoded, and pdf-lib rebuilds the file
Fidelity
Very generous, so gentler than 200/300/500 KB
The sweep often stops early or is skipped at 1 MB, so scans keep their detail and most files keep selectable text
Hard cases
Reports smallest achievable
Text PDFs and most scans clear 1 MB easily; only a heavy photo-laden scan stops at the smallest legible size with a warning
Privacy & scale
In-browser, bounded by RAM
Compressed with pdf-lib on-device, one PDF at a time; 100% client-side, no upload
Compress PDF to 1MB locks the target at 1 MB (1024 KB, parsed from the URL) and rebuilds the document in the browser: pdf.js renders the pages, images are down-sampled and JPEG-re-encoded, and pdf-lib assembles the result, producing three variants (Best, Balanced, Smallest) each marked when it clears 1 MB. Because 1 MB is the most generous of the common caps — far roomier than 200 KB, 300 KB or 500 KB — most text PDFs are already under it and scans keep their detail, so most files meet the cap without rasterising pages and their text stays selectable; only a heavy multi-page scan stops at the smallest legible size with a warning. Reaching the target is lossy, so any rasterised pages lose selectable text. Everything runs on-device; nothing is uploaded.