Available now
Reliable
Batch processing
Run the file-producing tools across many documents and collect the results.
Run this tool
Each file becomes a job on this server. A batch small enough to finish inside the request is finished before you land on its status page; a larger one waits there for the worker. Your upload is deleted the moment its result exists — the status page says for how long the results themselves are kept.
How to use Batch processing
- Select your document: Choose the file you want to process with Batch processing. Your upload is validated immediately against strict format and size limits.
- Configure batch processing options: Adjust any page ranges, compression targets, passwords, or layout settings required for your task. Run the file-producing tools across many documents and collect the results.
- Run and receive your result: Submit the form to run any tool, queued directly on this server. Output: A status page holding one download per file. Temporary input files are deleted automatically when processing completes.
Frequently asked questions
- How does Batch processing work on MakeOverPDF?
- Run the file-producing tools across many documents and collect the results. MakeOverPDF runs any tool, queued on the server and returns: A status page holding one download per file.
- Is Batch processing free and private to use?
- Yes. MakeOverPDF requires no user account, watermarks nothing unless you use the watermark tool, and deletes your uploaded document from the private working directory as soon as the request finishes.
- What are the file size and page limits for Batch processing?
- The batch offers the tools whose whole answer is one file: compress, repair, flatten, optimise images, remove metadata, PDF to text, PDF to Word, PDF to spreadsheet, OCR text extraction and PDF to searchable PDF. Tools that need an answer about a particular document — a page range, a password, a crop rectangle — keep their own pages, because one answer cannot be honest across a folder of documents. Options are each tool's defaults. The checkboxes on a tool's own page (keep the layout, the spreadsheet format) are not asked here; for anything particular, run that tool directly. Up to 20 files, adding up to 100 MiB — the same ceilings every multi-file tool uses, refused before submission with the numbers that caused it. A batch small enough to finish inside the request is finished before the response is sent, so its status page already shows results. A batch over that threshold waits in this server's queue for the worker (php spark makeoverpdf:worker) to drain it, and the page says exactly that while it waits — it never claims work is done that is not. One file failing does not stop the others: the status page shows each file's outcome, and a failure carries the words written for you at the time — never engine output. Your upload is deleted the moment its result exists. A finished result stays on the status page for the retention window (60 minutes by default), then everything the job recorded is deleted with it. No tool that needs a password is offered: a password would have to be written into the queue's database row, which is exactly where a secret should not sit. A password-protected file fails its job with that explanation instead of waiting in the queue.