How to Compress a PDF for a Website: Fast Loading and Fast Web View
The situation
You have a PDF to publish on your website: a brochure, a price list, a white paper, a menu. You upload the original straight from the design tool, and now that page is the slowest thing on your site. Visitors on phones wait, bounce, and leave.
A heavy PDF behind a download link quietly drags down the whole page it sits on. The fix has two parts that work together: make the file smaller, and structure it so the viewer can start reading before the whole thing arrives.
Why website PDFs hurt page speed
Every byte of a linked PDF is a byte someone has to download, often over a mobile connection. A 50 MB brochure is 50 MB of waiting, and if it opens inline in the browser, the reader stares at a blank viewer until enough has loaded. Unlike an image, a PDF is usually not something the browser can show progressively unless the file is built for it.
There is a second, subtler cost. A normal PDF stores its structure at the end of the file, so a viewer generally needs most of the file before it can render page one. Over the web that means the reader waits for the full download even though they only wanted the first page. For a long document on a slow connection, that is the difference between instant and unusable.
Method one: linearize for Fast Web View
Linearization, also called Fast Web View, reorganizes the PDF so the data for the first page sits at the front of the file, along with a structure the server can stream. The viewer can then display page one while the rest downloads in the background.
- First compress the file so there is less to send overall (see method two).
- Save or export the PDF with Fast Web View or linearization enabled. Many PDF tools expose this as a single checkbox in save or preferences; some do it as a dedicated optimize step.
- If your host supports byte-range requests (most do), a linearized file lets browsers fetch just the first page's bytes first.
- Verify by opening the hosted link on a slow connection or throttled browser tab and confirming the first page appears quickly.
Linearization does not by itself make the file smaller; it changes the order so reading can start sooner. Pair it with compression for the full effect.
Method two: compress to a web-sensible size
Smaller is almost always better on the web, within reason.
- Decide a target. For a short brochure or flyer aim low, often a few megabytes or less; for a longer illustrated document a little more is acceptable, but treat anything above roughly 10 MB as something to justify.
- Downsample images to screen resolution. Web viewers display around 72 to 150 dpi, so print-resolution images are wasted weight behind a web link.
- Compress to your target. Open the file in PDF300, type the size you want, and download the fitted copy to host.
- Re-check the pages that matter most at normal zoom to confirm quality held.
Embedding versus linking
If the PDF is short and central to the page, embedding it inline can be convenient, but it still downloads the whole file, so compression and linearization matter just as much. For anything long or occasional, link to the PDF rather than embedding it: the page itself stays light, and only readers who click pay the download cost. Either way, host the compressed, linearized copy, never the raw export.
Checklist
- Compress first, then linearize so reading starts before full download.
- Enable Fast Web View or linearization when saving the final file.
- Downsample images to screen resolution; print dpi is wasted on the web.
- Keep short documents to a few megabytes; justify anything over roughly 10 MB.
- Link to long PDFs rather than embedding them inline.
- Always publish the optimized copy, not the original export.
FAQ
What is Fast Web View and do I need it?
Fast Web View is a way of saving a PDF, also called linearization, that puts the first page's data at the front and adds structure a server can stream. It lets the reader see page one while the rest downloads. You need it for any longer PDF you expect people to open in the browser; for a tiny file it matters less because the whole thing arrives almost instantly anyway.
Does linearizing make the file smaller?
No. Linearization reorders the existing data so reading can start sooner, but it does not reduce the byte count on its own. To make the file smaller you compress it, usually by downsampling images to screen resolution. Do both: compress for a lighter download, linearize so the first page appears fast.
What file size should a website PDF be?
There is no single rule, but lighter is better for page speed. A short brochure or flyer should sit comfortably in the low single-digit megabytes; a long illustrated report can be larger but is worth questioning past roughly 10 MB. Set your chosen number as the target in PDF300 and compress to fit.