PDF tools · batch
Forty scans, one portal limit. Drop the whole folder on the tray, set one target, and every PDF is worked to it in a single run, each with its own result line. On the big suites this job is a paid extra; here it is simply free. One file at a time is on the Compress PDF page.
For a folder of scans, statements, or application documents that all have to fit under one portal limit.
Pick your PDFs
Set one target
Run and download the results
Drop PDFs on the tray, or click to pick them
PDF · tested with 50 files in one run · they stay on this device
Files are processed one at a time, so a big batch does not need a big device. A file that cannot shrink is kept as its original and the result line says why.
Pick PDFs to begin.
Each file runs the Compress PDF engine in turn: the photos inside are read once, a probe picks the starting setting, and the ladder steps down only as far as it must. Results collect on this page with the exact sizes, and the ZIP packs every processed file under its own name. Nothing is uploaded at any point.
The limit is your device, not us: the batch was tested with 50 files in one run, and past that your device's memory is the limit. A very long batch takes as long as it takes, one file at a time, and the page stays honest about progress. A PDF whose bulk is not photos may not shrink at all; it is returned as its original and the result line says so, in the same size type as the successes.
A password-protected PDF cannot be opened by this tool. Take its password off first with the unlock tool, then bring the file back.
Because on a server, every extra file costs the site money, so the big suites sell running-many-files-at-once as a paid extra, or cap a free job at one or two files. Here the work runs on your device, so a folder costs this site nothing. Batch is the ordinary way this page works, not an upgrade.
Yes. Pick the target once (200 KB, 500 KB, 2 MB or your own number) and every PDF on the tray is worked to it, with the same probe-first engine as the Compress PDF page. Each file gets its own result line: the size it reached, or the honest reason it stayed unchanged.
It is listed as failed or skipped, with the reason in plain words, and the rest of the batch carries on. The ZIP holds every file that was processed, including originals that could not shrink, each under its own name.
Nowhere. They are read into this page and processed in your browser, one at a time so the memory stays sane. Watch the network panel while it works if you want to check.