Compress a PDF Exported From Word

Three reasons compound. Word embeds entire font families rather than only the glyphs used, it stores inserted images at full original resolution even when displayed at thumbnail size, and it writes extensive metadata including tracked-change and author information. Together these easily account for 90% of the file.

It helps, but it is blunt — it downsamples everything to 96 DPI with no control, which can make screenshots hard to read. Exporting at Standard quality and compressing here gives you a better result because you choose the trade-off, and you can target an exact size.

No. Link annotations, bookmarks, the table of contents and internal cross-references are all preserved. Only the encoding of images and content streams changes — the document's navigational structure is left intact.

Any modern browser with WebAssembly support: Chrome, Edge, Firefox, Safari, Brave, Opera and Vivaldi, on desktop and mobile alike. There is no minimum specification beyond that — older or lower-powered devices simply take longer on large documents.

Very well, because the file itself is never transmitted. Only the page and the compression engine are downloaded, once, and they are then cached. Uploading a 100 MB PDF to a server-based tool would consume 100 MB of your data allowance; here it consumes none.

Both, layered. Structural optimization — removing duplicate objects, dead revisions and metadata — is entirely lossless. Image downsampling and JPEG re-encoding are lossy, which is where the substantial savings come from. Text and vector graphics are never touched by either stage.

Yes, with no file limits, no watermarks and no account. Because processing happens on your device rather than our servers, there is no per-file cost to recover and therefore no reason to meter your usage.

Text always stays sharp because it remains real vector text rather than an image. Embedded photographs are downsampled and re-encoded, so quality loss scales with how aggressive a preset you choose. Less Compression is visually near-identical to the original.

Yes. The interface is fully responsive and the engine runs on iOS and Android. Bear in mind that mobile devices have less memory, so very large files (over roughly 50 MB) may be slow or fail on older phones.

Your PDF was probably already optimized — for instance exported by Acrobat with compression enabled, or generated as pure text with subset fonts. When we cannot beat the original we deliberately return your untouched file rather than a worse one.