Split a PDF locally
Cut a PDF into separate files by page range. 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
A run that produces several files is packaged as one ZIP on your device.
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.
- A password-protected PDF is not modified here. FileSlimmer will not open one by ignoring its encryption, so this tool is unavailable for an encrypted document.
- Several outputs are packaged into one ZIP inside the browser. No server assembles it, so a very large set is bounded by the memory this tab has.