Compress a very large PDF (100 MB and up) in your browser

No upload means no server cap

Online compressors cap file size because every byte has to travel to their server and be stored there for a while. A 500 MB upload costs them bandwidth and disk, so they set a limit or charge for a higher one.

Here the PDF is opened and compressed inside your browser, so there is nothing to cap. What remains is a physical limit: the memory your browser lets 1 tab use. A built-in memory guard keeps track of it. In Chrome and Edge the budget is 70 percent of the memory the browser reports, never more than about 1.8 GB; Firefox and Safari do not report memory, so the guard assumes 1.5 GB.

When opening a file would cross that budget, the job stops right there, before any work starts, instead of freezing the tab halfway through. The message gives the numbers. For a 900 MB file it reads “report.pdf is too big for this browser to open: Opening this file needs about 1.8 GB”, followed by how much this browser has to work with. It never calls the file damaged; the file is fine, it is the tab that is too small, and the rescue below is the fix.

What makes a PDF this big, and what it can become

Files over 100 MB are almost always pictures:

The first 2 rows are the common case, and they compress well. The last row is the honest exception: if the size is not pictures, no preset helps, and the result says the file is already as small as this tool can make it. To see what your file is made of before you start, open it in the inspector, and for the causes in more depth, see why is my PDF so big.

Steps

1. Close what you do not need. Other tabs and other big documents in this tab share the memory. On a phone, close other apps.
2. Drop the PDF on the compressor above, or press the button to choose it. The file list shows its page count and size.
3. Pick a preset. Email (pictures at 110 dpi) is the right choice for anything read on a screen and gives the biggest saving. Web keeps 150 dpi for files people zoom into. Print keeps 300 dpi, which saves little on a scan that is already 300 dpi.
4. Press Compress and watch the progress line: it names the stage, the page while it lists pictures, and “Re-encoding picture 37 of 100” while it works.
5. Read the result. It shows the size before and after, how many pictures were re-encoded, and the 5 pages that changed most. Open the result and zoom into 1 of those pages before you send it.
6. Save it. In Chrome and Edge the save dialog lets you pick the folder; other browsers put it in Downloads.

Time to expect. On a mid-range 2024 business laptop, measured on 11 October 2026:

So plan on roughly 1 minute per 100 scanned pages with a preset on a laptop, and longer on a phone or an older computer. A size target takes longer, because the tool tries several settings to find the one that fits; if you only need “small enough for email”, the Email preset is the faster route. (The size next to a target counts 1 MB as 1,000,000 bytes, as the target itself does.)

If the tab runs out of memory: the 3-step rescue

Our 203 MB test file needed about 1.4 GB of memory at its peak. So files of a few hundred MB are near the edge of what a browser tab can hold, and files near 1 GB are refused up front. When a big file will not open or the tab gives up, cut it down to size:

1. Split it. Open Split PDF and cut the file into chunks, for example every 100 pages. Splitting copies pages without decoding their pictures, so it needs less memory than compressing.
2. Compress the parts. Drop all the parts on the compressor at once. It does them 1 at a time, so only 1 part is open at a time. Compressing many PDFs at once covers that mode.
3. Merge them back. Put the compressed parts into Merge PDF in order. The parts are now small, so the merge is quick.

If the result is still too large to send, send it in parts or as a link: send a large PDF compares the routes, and PDF too big to email has the attachment limits.

What this cannot do

• A file of 1 GB or more will not open in the compressor. Opening needs about twice the file’s size in memory, and no browser gives a tab that much. Split may still manage it, because it does not decode the pictures; if it cannot, use a computer with an installed PDF app.
• A big file on a phone is a gamble. Phones give a tab less memory, and a phone browser may close the tab with no message. For anything over 100 MB, use a computer if you can.
• The compressor holds the whole file while it works. It does not stream page by page to disk, which is why splitting helps.
• It does not shrink fonts, video or attachments. Only pictures are re-encoded. A file that is big for other reasons comes back unchanged, with a line that says so.
• Cloud tools with very large caps exist. If you accept that the file is uploaded and stored on someone else’s server for a while, they can take files your browser cannot. For confidential documents, splitting and compressing here is the safer route because nothing leaves your device.