One operation per run, deliberately
A queue that does four things to every file is a queue nobody can debug. Run resize, download, then run convert if you need both. Each pass is legible and each result is traceable to a setting.
Batch
Batch edit a folder without uploading any of it.
Queue a set of photos, pick one operation, and let the tab work through them. One file out for every file in.
One file out per file inNothing uploadedNo model to download
The short answer
To batch edit photos, add the files to the queue, choose one operation, resize, crop, compress or convert, and run it. Every photo is processed on your own device, one at a time, and comes back as its own download. Files that cannot be read fail on their own row and the rest of the queue finishes without them.
Run a batch now
Select several photos at once, or drop a whole selection onto the panel. Pick the operation and its settings, then run the queue. Each row shows what came out.
Before
Presets
Do this to every file
Size by
Add a photo first.
Checking what this device can do. Nothing is uploaded.
Add a photo and run the tool. The download appears here.
Try another tool on the same photo
The short version
What to know before you start
Batch work is where the on-device argument stops being philosophical. Four hundred listing photos through a cloud editor is four hundred uploads, four hundred downloads and a bill that scales with the folder. The same four hundred through a browser tab is your own processor, running for a while, for nothing.
The engineering constraint is memory rather than speed. Decoding four hundred photographs at once would exhaust any tab, so the queue processes strictly one at a time: peak usage is a single decoded image plus a single drawing surface, whatever the length of the list. That is why the queue is a queue and not a parallel pool.
Files are processed one at a time
Peak memory is one photo, not the whole folder. That is the difference between a batch tool that works on a laptop and one that crashes the tab at file forty.
One bad file does not lose the run
A HEIC in a folder of JPEGs fails on its own row with the reason attached. Everything else finishes. You fix the one file rather than starting the batch again.
Mixed shapes need thought
A ratio crop applied to a folder of portraits and landscapes will cut them differently. Longest edge is the safer setting for a mixed folder, because it bounds both orientations the same way.
Names carry what happened
The output keeps the original stem and picks up the dimensions or a marker, so a folder of results is self-documenting. Nothing is renamed to a hash.
Nothing is uploaded, at any scale
The privacy claim does not weaken with volume. Four hundred client photographs are four hundred files that never left the machine they were already on.
Step by step
How do you batch edit a set of photos?
Four steps. Everything runs on this device, and the queue keeps working if the connection drops.
- 1
Add the files
Select several photos in the file picker, or drag a whole selection onto the panel. Each one gets a row showing its name and current size.
- 2
Choose the operation
Resize, convert, compress or crop to a ratio. One operation applies to every file in the queue, which is what keeps the result predictable.
- 3
Set it once
Configure it exactly as you would for a single photo: a longest edge, a target file size, an output format or a ratio and anchor. The same settings apply to the whole list.
- 4
Run and collect
Press run and watch the progress move through the queue. Save files individually from their rows, or press download all to save every finished file in turn.
Which operation should a batch run?
Longest edge resize is the safest thing to do to a mixed folder. It bounds portraits and landscapes identically and never crops, so nothing comes back framed in a way you did not choose.
Convert is the second most useful, and usually means everything to JPG for a portal that will not take anything else, or everything to WebP for a site you control.
Compress to a target works per file, so each photograph gets its own quality search and each one lands under the limit. That is different from applying one quality setting to the folder, which leaves some files over the line and others needlessly small.
Crop to a ratio is the one to think about twice. It is excellent for a set shot the same way on a tripod and unpredictable on a folder of mixed framing. Consider running the single-photo cropper on the awkward ones instead.
What limits the size of a batch?
Two things, and only one of them is a plan. The technical limit is your device: each photo is decoded, drawn and encoded in turn, so a long queue takes time rather than memory, and a phone will simply be slower than a laptop.
The product limit is the queue size on the Free plan, currently 25 files at a time. There is no daily cap behind it and no credit counter: run the queue, clear it, load the next set. Resolution is not capped at all, on any plan, because nothing here costs us anything per image.
Unattended queues over a whole folder, and an API for the same operations, are what Pro is being built to add. Neither is on sale yet, and the pricing page says so plainly.
What happens when a file in the queue fails?
It stops, and nothing else does. The row turns red and carries the reason in the same words the single-photo tools use, so a HEIC that this browser cannot decode says that rather than reporting an unknown error.
The rest of the queue continues and its results are yours. That behaviour is a deliberate choice: a batch tool that aborts on the first bad file punishes you for the contents of a folder you did not curate.
Remove the failed rows, fix the files, and run a second queue with just those. The results from the first run stay where they are until you clear the queue.
| Property | Detail |
|---|---|
| Input formats | JPG, PNG, WebP, AVIF, GIF, BMP. HEIC where the browser can decode it. |
| Operations | Resize, crop to a ratio, compress to a target size, or convert format. |
| Queue size | 25 files at a time on the Free plan. |
| Concurrency | One file at a time, so peak memory stays flat as the queue grows. |
| Failures | Reported per file. The rest of the queue completes. |
| Output | One file per input, named from the original with the operation's marker. |
| Download | Individually per row, or all in sequence. |
| Model download | None. Every batch operation is a canvas operation. |
| Export limits | Full resolution, no watermark, no credit counter. |
Slide the table sideways to see every column.
Worth avoiding
Where this usually goes wrong
Running a ratio crop over a mixed folder
Portraits and landscapes crop to the same shape from very different starting points. Check a couple of results before you trust the whole run, or resize by longest edge instead.
Chaining operations in your head
One queue does one thing. If you need a resize and a convert, run two passes and download in between, so each result is traceable to the settings that made it.
Loading the folder before deciding the setting
Work out the operation on one representative photo in the single-photo tool first. A batch is for repeating a decision, not for making one.
Navigating away mid-run
The work happens in this tab. Closing it stops the queue. Results already finished stay downloadable until you clear the queue.
Expecting a zip
Files download individually, in sequence. Some browsers ask once for permission to save multiple files; allow it and the rest follow.
Assuming quality settings transfer between formats
Quality 80 in JPG and quality 80 in WebP are different pictures and different sizes. If you switch format, check one result before you run the folder.
Questions
What people ask about this tool
Every answer is in the page source, so a reader and an answer engine get the same words.
How many photos can I process at once?
The Free plan runs 25 files in a single queue. Run it, clear it, and load the next set: there is no daily counter and no per-image credit. Larger unattended queues are one of the things Pro will add when it goes on sale.
Do the photos get uploaded to a server?
No. Each file is read from disk into this tab's memory, processed by your own device, and written back out. That is also why a queue keeps working after the connection drops, and why the time it takes depends on your hardware rather than on somebody else's queue.
What happens if one file in the batch fails?
It fails on its own row and the rest of the queue carries on. The row turns red and carries the reason, which is usually a HEIC the browser cannot decode or a file that is not an image. Nothing else in the run is affected.
Can I apply more than one operation in a single run?
Not yet. One queue does one operation, which keeps what happened to each file legible. To chain two, run the queue, download the results, and load them back in for the second pass. Chained recipes are on the list.
Does batch processing use more memory than one photo?
Barely. Files are processed one at a time rather than all at once, so peak memory is one decoded photo plus one drawing surface, whatever the length of the queue. That is the design decision that lets a queue of hundreds run in a browser tab at all.
Are the results downloaded as a zip?
No, they download as individual files. Building a zip in the browser means shipping a compression library to every visitor for something the browser already does well, so the download all button saves each file in turn with a short pause between them.
Will the file names change?
The stem is kept and the extension follows the format that was actually written. Resize and crop add the output dimensions, and compress adds a marker, so a folder of results tells you what happened without opening anything.
Work out the setting on one photo first.
The single-photo tools use the same engine and the same options. Get it right once, then point the queue at the folder.
Keep reading
Where to go next
Resize image
Exact pixels, marketplace presets and an aspect lock, run on your own device.
Read itPlatform image rules
Image size, file type and background rules for 22 selling platforms, each one sourced.
Read itCompress image
Name a file size limit and the tool re-encodes until the photo fits it.
Read itAll the tools
The whole toolbox in three families, with what each one needs before it can run.
Read it