SEO Tutorial Guide
Learn how to remove backgrounds from multiple images at once.
How to Batch Remove Image Backgrounds for Free
Batch mode is for when you have more than one image and don't want to run them through one at a time. Select or drag multiple image files onto ZeroBG and each one gets its own card, its own progress bar, and its own result, all processed in your browser with nothing uploaded anywhere.
Loading a batch
Drag several files onto the drop area, or click it and select multiple files in the picker (both support the usual multi-select with Ctrl/Cmd or Shift). Mixed formats work fine together: PNG, JPG, WEBP, GIF and BMP can all sit in the same batch. There's no folder-drop support, so if your files are in a folder, open it and select the files inside rather than dragging the folder itself; dropping a folder directly adds nothing.
As soon as valid files are accepted, a card appears for each one and processing starts immediately, working through the queue from the first card to the last. There's no separate step where the batch sits queued for review before you tell it to go.
The queue processes one image at a time
Cards run through the model in sequence, not all at once. Whichever card is currently processing shows a progress overlay; the rest sit at "Queued" until their turn comes. This keeps the tab responsive and each card's status legible, but it also means a large batch takes as long as the sum of its images, not the time of the slowest one.
ZeroBG doesn't publish a time-per-image figure, and it depends heavily on your hardware: image resolution, CPU or GPU, and whether your browser supports WebGPU. Where WebGPU is available the model runs noticeably faster than the plain WebAssembly fallback: worth checking your browser supports it if you plan to run large batches often.
Fixing one bad card without losing the rest
Each finished card has two buttons: download that single result, or remove the card from the batch. If the model has made a mess of one image (busy backgrounds and hair against a similarly-toned surface are the usual culprits), delete just that card rather than redoing everything.
One warning worth taking seriously: loading a new file or a new batch resets the workspace. If you drop a single image back in to fix it in the full editor, that clears the current batch queue, including any completed results you haven't downloaded yet. Download whatever you want to keep before you load anything new, not after.
Format and background apply to the whole batch
The export format (transparent PNG, JPG, or WEBP) and any background you've picked in the editor apply to every image in the batch when you export, not per image. There's no way to give image 3 a white background and image 7 a transparent one within a single run; if you need different treatments, change the setting and run the affected files through as a separate batch.
Downloading results
Two ways to get your files out. "Download all" bundles every completed result into a single ZIP. Or download individual cards as they finish, useful if you only need a couple of results now and the rest can wait.
The ZIP is worth understanding properly, because it's not just a bundle of raw cutouts. When you build it, ZeroBG checks your current editor settings against the defaults (transparent PNG, original scale and position, no shadow, no glow, brightness/contrast/saturation all untouched). If everything is still at default, it zips the raw AI result directly. If you've changed the background, added a shadow or glow, adjusted the crop or ratio, or nudged brightness or contrast, it re-composites every single image in the batch with those settings before zipping, using each image's own cutout against the same background and effects. In other words, style one result the way you want in the editor, then hit "download all" and every image in the batch gets that treatment, not just the one you were looking at.
Product photos for marketplaces
The most common reason to reach for batch mode is a stack of product shots that all need the same background treatment before going on a marketplace listing. Load the batch, set your background and format once, and let the queue run. For the specifics of getting a clean, marketplace-ready solid white background, including why JPG rather than PNG for that case, see how to change a photo background to white; the settings described there apply to a full batch exactly as described above.
Limits: up to 50 images, 40MB each
A single drop accepts up to 50 images; each file must be 40MB or under. Anything that isn't a supported image type, or is over 40MB, is skipped and listed by name with the reason. If you drop more than 50 valid images at once, ZeroBG queues the first 50 and tells you how many were left out; it does not reject the whole drop, and it does not raise the ceiling, so the extra files simply aren't added. If you have more than 50 images to get through, split them and run the batches one after another. There's no account and no usage quota, so nothing stops you running as many batches as you need.
Before you start a big batch
A few practical notes. Closing or reloading the tab mid-batch loses any results you haven't downloaded yet; ZeroBG doesn't save progress anywhere, so there's no resume. Don't navigate away or let your laptop sleep until you've grabbed what you need.
A batch of large, high-resolution images will use a meaningful amount of memory while it runs, since decoding is done in your browser rather than on a server. On an older machine, or one with several other heavy tabs open, expect it to run slower than on a fresh browser with nothing else competing for resources.
If this is the first time you've used ZeroBG in this browser, hovering over or clicking the drop area starts the one-time model download in the background before you've even chosen files, which is normally enough of a head start that it finishes before the queue needs it. On a slow connection it might not, in which case the first card waits a little longer than the rest. See the offline guide for the full breakdown of what that download contains and how to make sure it's cached.