Compress multiple PDFs at once
Drop a folder full of documents, set one size limit, get them all back. Nothing is uploaded — which is the entire reason this is usable for CVs, invoices and ID documents.
What this is for
One file at a time is fine when you are filing your own visa application. It is not a workflow when you are an HR coordinator with fifty CVs to get under an applicant tracking system's per-file cap, or a bookkeeper with a month of invoices to fit a portal limit.
That case is also exactly where uploading is least acceptable. CVs carry addresses and phone numbers; invoices carry bank details; ID scans carry everything. Compressing them in the browser means a folder of other people's personal data never leaves your machine — which is a materially easier thing to justify to whoever is responsible for it.
How the queue behaves
| Situation | What happens |
|---|---|
| File already under the target | Handed back untouched — no quality lost for nothing |
| Lossless repack reaches the target | Marked text kept; nothing is rasterised |
| Lossless is not enough | Falls back to rasterising, marked rasterised |
| Target is impossible | Marked over target, smallest sensible version kept |
| File is password-protected | Marked and skipped; the rest of the batch continues |
Files run one after another rather than together. Each one holds all of its pages as images while it works, so processing several at once is the fastest route to running a phone out of memory.
Common questions
How many files can I do at once?
There is no fixed limit, because there is no server enforcing one. Twenty ordinary documents are comfortable on a laptop. The constraint is your device memory, and it is driven by page count rather than file size - fifty single-page files are far easier than five fifty-page scans.
Why are files processed one at a time?
Each file holds every one of its pages as an image in memory while it is being compressed. Running several at once is the quickest way to exhaust a phone, so they are queued deliberately rather than parallelised.
Does every file get the same target?
Yes - one target applies to the whole batch, which is the case that matters when a portal enforces the same cap on every attachment. Files already under the target are handed back untouched rather than compressed for no reason.
What if one file fails?
The rest continue. A file that cannot be read - usually because it is password-protected - is marked in the list and skipped, and you still get everything else.
Are my files uploaded?
No. Every file in the batch is compressed in your browser and none of them leave your device. For a folder of CVs, invoices or ID documents that is the whole point.