Try to compress a PDF to 200 KB
Rasterizes pages at a low DPI and steps quality down until the file lands near 200 KB. Files stay on your device.
How this works locally
- You choose a file; the page reads it from your device.
- The matching engine is loaded from fileslimmer.com and runs in a Web Worker.
- The result is written back to a location you choose on this device.
Before or choose files from your device
Original size —
Accepted formats
- Reads
- Writes
Estimated memory
Your browser reports only a coarse memory hint, so this figure is an estimate.
| Device profile | Largest PDF | Most pages |
|---|---|---|
| Minimal | 40 MiB | 100 |
| Low | 80 MiB | 250 |
| Balanced | 180 MiB | 500 |
| High | 300 MiB | 1000 |
Your browser is placed in one of these profiles from the coarse hints it exposes. A file above the limit is refused before it is read, rather than after the tab has run out of memory. On an iPhone or iPad a further ceiling applies whatever the profile — most pages: 100 — because mobile Safari reclaims a tab's memory far more abruptly than the hints can predict.
Limitations
- A text-only PDF is already close to its smallest useful size, so a structural save usually changes it by a few per cent. Large reductions mean the document was carrying images.
- The target size is what the search aims at, not what the result is promised to be. The search stops at the configured quality floor and reports the smallest file it reached.
- Rasterized output replaces the text layer with pixels. Search, selection, links, forms, annotations, accessibility structure and any digital signature are lost.
Target size
Best-effort local compression. If the target cannot be reached safely, FileSlimmer returns the smallest acceptable result.