AnyTool
Your files never leave your device. All processing happens locally in your browser.

How do I compress a PDF to 300KB (under 300 KB) online without uploading the file?

Open Compress PDF to 300KB and drop your PDF onto the page — the target is already locked to 300 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 and rebuilds the document with pdf-lib, aiming to land at or just under 300 KB. Because 300 KB is a generous target — roomier than 150 KB or 200 KB — the compression can be gentle, so scanned pages usually keep most of their sharpness and a light PDF may fit without heavy re-encoding. It produces three quality variants in one pass — Best Quality, Balanced and Smallest — and marks each with a check when it meets the 300 KB cap, then shows the before/after sizes and the exact percentage saved. A text PDF drops under 300 KB with plenty of room; a scanned or image-heavy one is squeezed as far as it will go, and if it cannot quite reach 300 KB 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 300 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 300 KB
  • A generous target, so compression stays gentle — scans keep more detail than at a 150 KB or 200 KB squeeze
  • Runs entirely in the browser with pdf.js and pdf-lib — no upload, no install, no account
  • Matches common 300 KB caps on portals like UPSC and IBPS banking — ideal for exam forms, certificates and mark sheets

What is

Compress PDF to 300KB

Compressing a PDF to 300KB means reducing the document’s file size until it is at or under 300 kilobytes, an upload ceiling used by portals such as UPSC and IBPS banking and a comfortable margin under a 500 KB 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 300 KB the compression is gentler than at 150 KB or 200 KB, so a scanned certificate usually stays crisp and a lighter document can fit without whole pages being rasterised. Whether 300 KB is achievable depends on the content: a text-only or single-page PDF slips under 300 KB comfortably, whereas a long multi-page scan of photographs may bottom out somewhat above 300 KB before the pages become unreadable. This tool locks the target to 300 KB, 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.

PDF Tools

Related terms

PDF300KBfile sizecompressionlossyDPIJPEG qualitydownsamplinggrayscalemetadatapdf.jspdf-libscanned PDFupload limitUPSCIBPSexam form

Frequently Asked Questions

No. The PDF is read and compressed to 300 KB 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 certificates, ID scans, mark sheets and private paperwork 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.

Usually, yes. The target is 300 KB and the tool gets as close as the content allows — text PDFs drop under it easily, and 300 KB is generous enough that most scans and even short multi-page documents fit; only a heavy photo-laden scan may bottom out a little above 300 KB, in which case the smallest size achieved is shown.

It depends on what is inside the PDF, but 300 KB is a comfortably roomy target. The real savings come from re-encoding images, so a text-only or lightly formatted document falls well under 300 KB, and a typical certificate, mark-sheet or short multi-page scan reaches it 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 300 KB, 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 when 300 KB is comfortably met.

At 300 KB the compression is often gentle: a light PDF can fit with its text left live and selectable, and scans stay noticeably crisper than at 150 KB — only when whole pages must be rasterised to hit the cap does their text become part of the image.

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 300 KB leaves far more room than 100 KB or 150 KB, so the sweep can stop early: scans usually stay sharp, and a lighter document may meet 300 KB without whole pages being rebuilt as images, which keeps its 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 heavier document does need its pages rasterised to reach 300 KB, 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, choose a larger target or a lossless PDF tool. For most certificates and forms headed to an upload box, the 300 KB result stays perfectly legible.

300 KB is a common cap on government and exam application forms — UPSC and IBPS banking use a 300 KB upper limit, and it is a safe margin under a 500 KB field while keeping scans sharper than a tighter squeeze.

A 300 KB ceiling appears on several government recruitment and examination portals — UPSC allows document uploads up to 300 KB and IBPS banking forms use the same generous limit, while scholarship sites, certificate-verification portals and many sign-up flows cap uploads at similar sizes to keep their databases lean. Because 300 KB is roomier than a 100 KB, 150 KB or 200 KB cap, the tool can compress more gently, so scanned certificates and mark sheets keep more of their detail while still clearing the field. This tool is built for exactly that: the target is fixed at 300 KB 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 250 KB, 200 KB and below, and larger presets (400 KB, 500 KB and up) exist for looser limits.

Detailed Explanation

How It Works

Compressing a PDF to 300 KB — Entirely in the Browser

Compress PDF to 300KB shrinks a document to a fixed 300 kilobyte target without uploading a single byte. The 300 KB 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, and rebuilds the file with pdf-lib, aiming to land at or just under 300 KB. Because 300 KB is a generous ceiling — roomier than 150 KB or 200 KB — the downward sweep of DPI and quality can stop early, so scanned pages usually keep most of their sharpness and a lighter document can meet the cap without whole pages being rasterised. 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. A text-only PDF slips under 300 KB comfortably; a scanned or image-heavy one is squeezed as far as it will go, and if 300 KB 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.

  • 300 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, rebuilds with pdf-lib in the browser
  • Three variants in one pass (Best Quality, Balanced, Smallest), each marked when it meets 300 KB
  • Generous target, so compression is gentle — scans keep detail and a light PDF can fit with text left live; reports the smallest achievable size when a heavy scan cannot reach 300 KB
Use Cases

When a 300 KB PDF Is Required

The 300 KB ceiling shows up on government recruitment and examination portals — UPSC allows document uploads up to 300 KB and IBPS banking application forms use the same generous limit — and it is also a comfortable safety margin under a 500 KB cap. Applicants shrink scanned certificates, mark sheets and category or experience documents to fit an upload box, and a 300 KB version clears a 300 KB or 500 KB field while keeping the scan more legible than a 100 KB, 150 KB or 200 KB squeeze would. Beyond exam and banking forms, scholarship applications, certificate-verification portals, university admissions and many sign-up flows impose similar limits to keep their databases lean. This tool targets that exact number: you drop the PDF and download a version that clears 300 KB, then attach it with confidence. When the portal specifies a tighter cap, 250 KB, 200 KB and smaller tools are one click away, and looser limits (400 KB, 500 KB and beyond) have their own presets.

  • UPSC and IBPS banking portals use a 300 KB upper limit, and 300 KB is a safe buffer under a 500 KB field
  • Keeps scans sharper than a 100 KB, 150 KB or 200 KB target while still clearing strict upload boxes
  • Also used for scholarship, admissions, certificate-verification and sign-up uploads
  • Sibling presets cover 250 KB, 200 KB and below for tighter caps and 400 KB, 500 KB and up for looser ones
Technical Details

How the 300 KB Target Is Reached

When the page loads at /compress-pdf-to-300kb, a URL parser (getPdfPresetFromPath) extracts the number and unit and fixes the target at 300 KB, 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: 300, grayscale, removeMetadata } to the smartCompressPDF routine (src/lib/workerClient.ts), which pursues two strategies and keeps whichever yields the smaller file that still meets 300 KB: 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 300 KB is a roomy ceiling, the sweep of DPI and JPEG quality often stops early — the Best variant frequently lands under the cap without heavy loss, and a lighter file may 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 300 KB, and the chosen one downloads from a local Blob with a -compressed.pdf suffix.

  • getPdfPresetFromPath parses the URL and locks the target at 300 KB
  • 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 300 KB is reachable depends entirely on the content. A text-only or single-page PDF drops under 300 KB with room to spare, and because the target is generous most scans and even short multi-page documents reach it while staying crisp; but a long multi-page scan or a file full of 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 300 KB is roomy enough that a lighter document often meets it without that step, keeping its text live, and when live text matters a larger 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, removing spare pages or splitting the document first usually gets you under the cap.

  • Text PDFs and most scans reach 300 KB while staying sharp; a heavy multi-page 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 300 KB a lighter file often fits 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; removing pages or splitting helps a stubborn scan fit
Privacy & Security

Privacy: Your PDF Never Leaves the Tab

The documents people compress for a 300 KB upload box are often the sensitive kind — ID scans, certificates, mark sheets, bank statements, 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 300KB — target, quality and limits
CapabilitySupportNotes
Target sizeLocked at 300 KBParsed from the URL; a banner replaces the preset grid so there is nothing to configure
Quality variantsBest, Balanced, SmallestThree generated in one pass; each tagged with a check when it lands at or under 300 KB
MethodImage re-encode + page rasterisepdf.js renders pages, images are down-sampled and JPEG-re-encoded, and pdf-lib rebuilds the file
FidelityGenerous, so gentler than 150/200 KBThe sweep can stop early at 300 KB, so scans keep more detail and a light PDF can keep selectable text
Hard casesReports smallest achievableText PDFs and most scans clear 300 KB; a heavy photo-laden scan stops at the smallest legible size with a warning
Privacy & scaleIn-browser, bounded by RAMCompressed with pdf-lib on-device, one PDF at a time; 100% client-side, no upload

Compress PDF to 300KB locks the target at 300 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 300 KB. Because 300 KB is roomier than 150 KB or 200 KB, scans keep more detail and a lighter PDF can meet the cap without rasterising pages, so its text stays selectable; text PDFs and most scans reach it easily, while 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.