PDF File Too Large? Get It Under 5 MB Free
If your PDF file is too large and you need it under 5 MB free of charge, the fastest route is not the compression slider most tools show you first. On a document that is mostly text, that slider can hand you back a file many times larger than the one you started with. Here is what is actually happening, and the setting that does the job.
The 5 MB limit almost never comes from your email provider
Worth establishing first, because it changes what you should do. A personal Gmail account accepts attachments up to 25 MB, and when you exceed that Gmail does not reject the message. It removes the attachment and inserts a Google Drive link instead (source: Google Workspace Help). So a 6 MB PDF is not what is blocking a personal Gmail.
The 5 MB number nearly always comes from the form on the other end. Job portals, tender and government submission pages, university applications, insurance claim uploads, and bank document-upload flows routinely cap individual files at 5 MB, and unlike Gmail they simply refuse the file. Corporate mail gateways are the other common source: the mail service behind them may allow 25 MB while the gateway is configured for less.
This matters because it tells you the target is a hard number, not a vague "make it smaller". You need the file at or under a specific size, and a tool that offers you Low, Medium and High is not answering that question.
Why a quality level can multiply a text PDF
A PDF does not store a page as a picture. It stores instructions: use Helvetica at 9 point, place this string at these coordinates, draw this line here. Those instructions are extraordinarily compact. That 40-page document averaged barely over a kilobyte per page, because forty pages of text is a small amount of information once it is expressed as font references and character positions.
A quality level does something quite different from what the word "compress" suggests. It renders each page into a bitmap at a fixed resolution and stores that bitmap as a JPEG. On our tool, Medium renders at 144 DPI with JPEG quality 0.65, and High renders at 96 DPI with quality 0.45. For a scanned document that is a genuine improvement, because the page was already a photograph and you are storing it more efficiently.
For a text document it is a catastrophe. You are replacing a kilobyte of drawing instructions with a full-page photograph of the result. An A4 page at 144 DPI is roughly 1190 by 1684 pixels, and a JPEG of that at quality 0.65 lands in the low hundreds of kilobytes no matter how little ink is on the page. Multiply by forty pages and you get the 7.97 MB we measured. The text also stops being text: it becomes part of the image, so it can no longer be selected, copied, or searched.
Use a target size instead: the exact steps
The compressor has a second mode that most people never switch to, and it is the one built for this job. Rather than applying a fixed recipe, it works backwards from a number you give it.
- Open the PDF compressor and drop your file in. Nothing is uploaded; the file is read by the page in your own browser.
- Under Compression, click To a target size instead of leaving it on By quality level.
- Type 5120 into the target field. The field is in kilobytes, and 5 MB is 5120 KB. It defaults to 1024, so this is a change you have to make deliberately.
- Press Compress PDF and read the sentence it gives you back. It states the size it reached, whether that met your target, and how many passes it needed.
On the same 40-page text document that the Medium level inflated to 7.97 MB, the target-size mode with 5120 KB returned: "Hit 46.26 KB, under your 5.00 MB target, in 1 pass." One pass, no rasterisation, text still selectable, file essentially unchanged in size because it was never the problem.
What the target-size search actually does
It is worth knowing the sequence, because it explains why the result is sometimes instant and sometimes takes a while.
- Lossless pass first. The file is re-saved with object-stream compression, structural tidying only, no pages redrawn. If that already fits under your target, the tool stops immediately and your text layer survives. This is the single-pass result above.
- Then a first render. If the lossless file is still too big, pages get re-rendered at 144 DPI and JPEG quality 0.65, the Medium settings, and measured against your target.
- Then it adapts. If that is still over, it calculates how much further it needs to go and adjusts, spending roughly two-thirds of the reduction on resolution and the rest on JPEG quality. Dropping DPI degrades a page more gracefully than heavy JPEG artefacting at the same byte saving.
- And it has floors. The search will not go below 50 DPI or JPEG quality 0.2, and it gives up after five attempts. Below those numbers the pages stop being readable, which is not a result worth returning.
If it cannot reach your number, it says so and hands back the smallest version it managed, rather than quietly returning something that still will not upload. For a large scan that message is usually accurate: the file is big because it has a lot of pages, and no quality setting fixes a page count.
When compression is the wrong answer
If the tool reports that it could not reach your target, the honest next move is usually to send less rather than to squeeze harder. A 200-page scanned bundle compressed to within an inch of legibility serves nobody, and the person on the other end generally wants specific pages.
Two routes are usually better. You can split the PDF into smaller documents and send the relevant one, or you can extract just the pages you need and send those. Both keep full quality on the pages that matter, which a heavy compression pass cannot.
There is also a case for doing nothing. If your file is 6 MB and the real limit turns out to be the 25 MB on a personal Gmail rather than a 5 MB form, the correct action is to check the actual requirement before degrading a document.
Which mode for which file
Text document: invoice, resume, contract, statement. Use a target size. It will almost certainly finish on the lossless pass and leave your text selectable. Never pick Medium or High here; that is the case that inflates.
Scanned document: photographed or scanned pages. Either mode works, because the pages are already images. A target size is still the better choice when you have a hard limit to meet, since it stops as soon as it fits instead of over-compressing.
Large multi-page bundle. Split or extract first, compress second. Page count, not page quality, is what is making the file large.
The file never leaves your device
The documents people need to force under 5 MB are rarely trivial ones. They are bank statements for a loan application, salary slips for a rental agreement, Aadhaar and PAN copies for a KYC form, medical reports for an insurance claim, signed contracts for a client.
Compression here runs entirely in your browser tab. The pages are rendered by pdf.js and the new file is written by pdf-lib, both executing in JavaScript on your own machine. There is no upload step, no copy of your document sitting in a queue on a server somewhere, and no account to create. Closing the tab is all the cleanup there is.
This is also why the tool can be honest about failure. A service that has already taken your file has an incentive to return something. A tool running on your own machine can simply tell you the target was not reachable and let you decide what to do next.
Frequently asked questions
My PDF file is too large. How do I get it under 5 MB free?
Open the compressor, switch from 'By quality level' to 'To a target size', and type 5120. The field is in kilobytes, and 5 MB is 5120 KB. The tool then works backwards from that number instead of applying a fixed quality setting, trying a lossless pass first and only re-rendering pages if that is not enough. It is free, there is no account, and the file never leaves your browser.
Why did compressing my PDF make it bigger?
Because a quality level rasterises the pages, and rasterising text is the opposite of compression. A page of text is stored as a compact set of drawing instructions ('use Helvetica 9pt, put this string here'), which is far smaller than a photograph of that same page. We measured this on a 40-page text document: at the Medium level a 46.25 KB file came back as 7.97 MB, and the tool reported the result honestly as a reduction of -17547.4%.
What is the difference between the quality levels and the target size?
A quality level is a fixed recipe applied once: Low re-saves the file without redrawing pages, Medium redraws every page at 144 DPI as a JPEG, and High redraws at 96 DPI with heavier JPEG compression. A target size is a search: the tool tries the lossless route, and if the file is still over your number it re-renders and keeps adjusting resolution and JPEG quality across up to five passes until it fits or runs out of room.
Is 5 MB actually the limit for email attachments?
It is rarely the provider's own limit. A personal Gmail account accepts attachments up to 25 MB, above which Gmail substitutes a Google Drive link instead of attaching the file (source: support.google.com/mail/answer/6584). The 5 MB figure usually comes from somewhere else: a job portal, a government or banking upload form, a university submission page, or a corporate mail gateway configured more tightly than the mail service behind it.
Will compressing to a target size make my text unselectable?
Only if it has to. The target-size mode runs a lossless pass first, and when that already fits under your number it stops there and hands the file back with the text layer intact. In our test on a 40-page document it reported 'Hit 46.26 KB, under your 5.00 MB target, in 1 pass'. Text only becomes part of an image if the lossless result is still over your target and the tool has to re-render pages to get there.
What if the tool cannot reach the size I asked for?
It tells you rather than silently handing back something that does not fit. The search stops at 50 DPI and JPEG quality 0.2, because below that the pages stop being readable, and it will not loop on settings that have no room left to move. When it gives up it reports the smallest size it managed and suggests splitting the document or removing pages, which for a large scan is usually the honest answer.
Does my file get uploaded to a server to be compressed?
No. The compression runs in JavaScript in your own browser tab, using pdf.js to render pages and pdf-lib to write the new file, so the document never travels to us. That matters most for exactly the files people need to shrink for upload forms: bank statements, salary slips, Aadhaar and PAN copies, medical records, signed contracts.
My scanned document is still too big after compressing. What now?
A scan that will not fit is usually a page-count problem rather than a quality problem, because every page carries its own image. Splitting the document and sending the relevant pages is often both smaller and more useful to whoever receives it. If the requirement is a specific set of pages, extracting those directly avoids the compression trade-off entirely.