By PDFKits Team — Published February 19, 2026
TL;DR: To optimize PDF for web delivery, do four things: downsample images from 300 to 144 dpi, subset embedded fonts, linearize the file for Fast Web View, and strip orphaned objects. A 12 MB marketing PDF typically lands at 1.5–2.5 MB with no visible loss, and a linearized file renders page 1 in about 400 ms instead of after the full download. PDFKits runs all four steps free in your browser; Adobe Acrobat Pro charges $14.99/month for the same result.
A 12 MB whitepaper takes about 8 seconds to download on a 12 Mbps mobile connection — long enough that a meaningful share of visitors abandon before page 1 renders. The same file optimized weighs 1.8 MB, downloads in 1.2 seconds, and shows its first page within 400 ms because linearization streams page 1 before pages 2–40 arrive. When a PDF is served directly, the file itself becomes the Largest Contentful Paint element that Google's performance guidance measures, so optimization is not cosmetic — it shows up in Core Web Vitals.
Most PDFs on the web are unoptimized exports from Word, InDesign, or Photoshop: full-resolution images, complete font files, no linearization. Cloud compressors like Smallpdf will shrink them, but only after you upload the file. PDFKits' Optimize PDF applies image downsampling, font subsetting, linearization, and object cleanup locally — a typical marketing PDF drops from 8–15 MB to 1–3 MB at no perceptual cost.
Images account for 70–95% of a typical PDF's weight. A brochure photo at 300 dpi costs roughly 600 KB per page; at 144 dpi — still sharp on Retina screens — it costs about 140 KB. For screen-only documents, 300 dpi is wasted bandwidth. If a brochure serves both print and web, host two versions.
Embedding Helvetica Neue with all 11 weights adds about 1.1 MB. Subsetting keeps only used glyphs — typically 200–400 of a font's 2,500+. Modern exporters subset by default, but concatenated PDFs from mixed sources often carry full fonts.
A linearized PDF (Adobe calls it Fast Web View) restructures the file so page 1 sits first, followed by an index. The browser renders the opening page after roughly 80 KB instead of waiting for the entire file — on slow connections, perceived first-render drops from 6 seconds to under half a second.
Multi-session documents accumulate orphaned objects: deleted images still in the object table, unused form definitions, stale thumbnails. Stripping them — plus creator metadata that leaks usernames and file paths via Clean Metadata — reclaims modest space and improves privacy.
Best for: marketing, documentation, and communications teams that publish PDFs visitors actually have to download.
| Feature | PDFKits | Adobe Acrobat Pro | Smallpdf | iLovePDF |
|---|---|---|---|---|
| Cost | Free | $14.99/month | $9/month | $48/year Premium |
| Files stay on your device | Yes | Yes (desktop) | No — cloud | No — cloud |
| Linearization (Fast Web View) | Yes | Yes | Yes | No explicit control |
| Target-dpi image downsampling | Yes | Yes (granular) | Preset-only | Preset-only |
| Font subsetting | Yes | Yes | Yes | Yes |
| Free-tier limits | None | 7-day trial | 2 tasks/day | Limited tasks |
For batches of 100+ assets, a Ghostscript one-liner (-dPDFSETTINGS=/screen) is the fastest route if you have a command line. For single files — or for drafts that cannot be uploaded anywhere — browser processing produces equivalent output without the vendor in the path.
Three measurements tell you the optimization worked. File size: aim for 50%+ reduction on image-heavy PDFs. Perceived render: throttle Chrome DevTools to "Slow 4G" and confirm a linearized PDF paints page 1 within ~500 ms. Visual check: 200% zoom on text and photos.
The classic failure mode is downsampling line art. Photos survive 144 dpi; architectural drawings and circuit schematics do not — keep diagrams at 200 dpi or use Lite. Also know what optimization cannot do: it will not shrink a scanned image dump to text-PDF sizes (rebuild from source instead), it will not add accessibility tags, and it conflicts partially with PDF/A, which requires fully embedded fonts — archival files run 30–50% larger than web-optimized ones, per the PDF Association. For hard upload caps, pair with Compress PDF, which targets explicit sizes like 1 MB.
For teams that ship PDFs through a website repository, add an automated regression: a CI check that fails the build when a file exceeds its size budget (3 MB for whitepapers, 1 MB for one-pagers). This catches the intern who re-uploads the unoptimized InDesign export eight months from now. One number worth remembering when arguing for the budget: PDFKits processes 100% of the file in the browser and costs nothing, while a five-person marketing team on Acrobat Pro pays about $900 per year for the equivalent optimization features.
No. Text is stored as vector glyphs and stays sharp at any zoom. Only embedded images are downsampled, and only when their resolution exceeds the target dpi.
Not with PDFKits — the work runs in your browser on pdf-lib and PDF.js, and no network request carries the file. Cloud tools like Smallpdf do upload the file as part of their pipeline.
Compression reduces bytes (image downsampling, font subsetting, stream compression). Linearization rearranges the same bytes so page 1 renders before the full download completes. They solve different problems and you usually want both.
Open the file in Adobe Reader → File → Properties → Description. "Fast Web View: Yes" confirms linearization. "No" usually means the source file had structural issues — re-run the optimization.
The Web preset (around 144 dpi) is right for 30–60 page whitepapers with photos. Target 2–4 MB final size: below 1 MB usually shows photo degradation, above 5 MB wastes bandwidth for screen reading.
No. Links, bookmarks, and outlines live in the object table independently of page content streams and are preserved through optimization.
Yes — interactive objects are preserved while surrounding images and fonts are optimized. Expect smaller savings on form-heavy files, since there are fewer image bytes to reclaim.
Partially. PDF/A demands fully embedded fonts and restricts some compression, so an archival file cannot be as small as a web file. If you need both, publish a web-optimized copy and archive the PDF/A original.
PDFKits processes one file at a time; for dozens of files, open multiple tabs, and for hundreds, script Ghostscript. The downsampling and linearization logic is the same — only the batching mechanism differs.
No. Encryption and permission settings carry through to the optimized output. To remove a password you know, unlock the file first, then optimize.
Optimize PDF — downsampling, subsetting, and linearization in one pass. Compress PDF — hit explicit size targets for upload limits. Clean Metadata — strip creator info before publishing. OCR PDF — make scanned PDFs searchable before optimizing. Merge PDF — combine assets before the final pass. Split PDF — serve large documents as per-chapter files.