

Batch background removal for photographers
For product, headshot, school and event work, background removal is a step between culling and delivery, not a retouch done one photo at a time. Cull and colour-correct first, export JPEGs, remove the backgrounds in batches, then place the cutouts on the client's colour or template. Bulk upload takes up to 100 images per batch; the API and n8n handle jobs that run every day.
Developers: one API callor drop a file, paste image Ctrl/⌘+V or
Processed on our servers. Previews are deleted right after.
No image?
Try one of these:
At a glance
| Where it fits | After culling and colour correction, before layouts, crops and delivery |
|---|---|
| Input | JPG, PNG or WebP up to 25 MB each |
| Output | Transparent PNG or WebP, or JPG on any solid colour |
| Bulk | Up to 100 images per batch, one colour, size and crop for the batch |
| Automation | REST API, or n8n through the HTTP Request or MCP Client node |
| Retention | Images are deleted from our servers after 48 hours |
How to do it
- Cull and export firstPick the selects and colour-correct in your editor, then export full-size JPEGs. Removing backgrounds after culling means you only pay for and check the frames the client will see.
- Run the batchUpload up to 100 images per batch. Choose transparent PNG if the cutouts go into a layout, or JPG on the client's colour for direct delivery, and crop to the subject with padding if every frame should match.
- Check edges and deliverZoom in on hair, fur, glasses and fine product parts. Re-shoot or hand-mask the few that need it, then drop the cutouts into your templates, galleries or the client's folder.
Tips and common mistakes
- Product jobs: deliver per marketplaceKeep one transparent master per SKU, then export the white JPEGs each marketplace wants. Amazon, Walmart and Google each set their own size and fill rules, so read the client's channels first.
- Headshots and school days: shoot for the cutoutA plain light backdrop a few steps behind the subject, with even light, gives the cleanest hair edges. Then any background the client picks later is a re-export, not a re-shoot.
- Events: keep originals untouchedFor event and sports work, deliver the original frames as well as the cutouts. Cutouts are for composites, badges and social graphics; the client may still want the real scene.
- Automate repeat clientsFor a retailer that sends new products every week, an n8n workflow can pick up each new file, send it to the API and save the result back. The API can also crop to the subject with padding and an aspect ratio in the same call.
- Price it as a line itemEach image costs 1 credit (2 for HD in the web editor), failed images are free and credits never expire, so you can work out the cost per frame and pass it on clearly.
Questions
When in my workflow should I remove backgrounds?
After culling and colour correction, and before layouts or crops. That way you only process the final selects, and the colours in the cutout match the rest of the gallery.
How many images can I process at once?
Bulk upload takes up to 100 images per batch, processed on our servers so you can close the tab. For more, run several batches or use the API.
Can I automate background removal for clients?
Yes. Call the REST API from your own scripts, or use n8n with the HTTP Request node or the MCP Client node and an API key. Each image costs 1 credit.
What happens to my clients' photos?
Images are deleted from our servers after 48 hours. Download your results within that time.
Which output format should I deliver?
Transparent PNG for designers and layouts, WebP when the client needs smaller transparent files for the web, and JPG on a solid colour for marketplaces and print.
Try it on your own image
New accounts get 50 free credits. One credit per image, no subscription, and credits never expire.
Remove a backgroundSources
Updated October 24, 2026