Batch file processing means one set of instructions applied to every file in a folder. On Doneload it takes three moves: build a recipe, drop the folder, download it done.
The recipe is called a pipeline. A tool page does one job; a pipeline strings several jobs together and runs all of them on every file, in the same order and with the same settings. A folder of product photos that each need resizing, a watermark and new names gets all three in one pass and comes back as a single ZIP.
How to batch process a folder
- Start in the pipeline builder with an empty recipe or a house preset.
- Add steps and configure each one.
- End with a rename pattern if the files need new names.
- Drop the folder and check the live preview of the first file.
- Run the recipe and download the results as one ZIP.
How a recipe works
Think of a pipeline as a chain in which every link is one tool with its settings. A file enters at the top, and whatever comes out of one step becomes the input of the next, down to the end. The only rule is compatibility: each step must accept the output of the one before it. Image tools follow image tools, and a PDF that has just been compressed can feed straight into OCR.
Take the Listing photos preset. Every photo is resized to 1200 pixels, watermarked and saved as a JPG at quality 85. End the recipe with a rename pattern such as listing-{n:03}, and a folder of camera files comes back as listing-001.jpg, listing-002.jpg and onward.
Before the whole batch runs, the live preview shows the result on the first file, so a wrong setting shows up before the full run instead of after it.
Presets to start from
- Web images resizes to 1600 pixels, converts to WebP and strips metadata.
- Social makes a centered 1080 by 1080 JPG.
- Listing photos resizes to 1200, adds a watermark and saves a JPG at 85.
- Scan cleanup compresses a scanned PDF, then reads its text with OCR.
- Email-safe PDFs compresses each PDF.
- Archive strips metadata and zips the set.
Run a preset as it is, change its steps, or start from an empty recipe. Recipes you build can be saved as presets too: one on a free account, as many as you want on Pro.
Try free, then scale
Every pipeline runs free on 3 files or fewer, which is enough to check a recipe on real files. Bigger folders have two routes:
- Pro (EUR 7.99 a month or EUR 59 a year) lifts the limit to 500 files per run and 500 MB per file, and removes the daily allowance.
- Credits pay for one big run without a subscription. One credit covers 25 files, packs cost EUR 4.99 for 20, EUR 14.99 for 100 and EUR 49 for 500, and credits never expire.
Before a run starts, the page tells you how many credits it will use.
Where the work happens
Pipelines always run on our servers, even when a step also exists as an in-browser tool on its own page. Uploads travel over an encrypted connection, the processing takes place in Germany, and files and results alike are deleted automatically within two hours.
The finished set can be downloaded file by file or as one ZIP.
FAQ
Is there an API for pipelines?
Yes. Requests describe the pipeline in exactly the format the builder uses. A free account includes 20 API calls a day with the same 3-file limit per run; Pro includes 1,000 calls a day and runs of up to 500 files.
What happens when one file fails?
Every other file completes normally. The results mark the failed file and give the reason.
How long does a run take?
Files are handled one after another, with progress shown for each. Image and document work takes seconds per file and video takes longer. Keep the page open and download once the run is done.
Is Pro required to process a folder?
Only above 3 files. Past that, either subscribe to Pro or pay for the run with credits.