Batch background removal for folders, scripts, and CI#
One-off demos are easy. Catalogs, shoots, and pipelines are not. You need a path that runs over a folder or a job queue without babysitting each file.
When this applies#
- You have dozens to thousands of images per run
- You prefer local unlimited processing for straightforward cutouts
- You automate via CLI, Python, Docker, or Mac Local API
- A subset of SKUs need Pro-level edges (hair, mesh, reflective products)
Which path to use#
| If you… | Use |
|---|---|
| Creators on Mac, drag-and-drop folders | withoutBG for Mac (batch UI) |
| Python scripts or notebooks | withoutbg package, open_weights or api |
| Headless servers / Kubernetes | Docker service-cpu or service-gpu |
| Highest precision at volume | Pro Model API with your own worker pool |
How withoutBG fits#
- Mac app: drop a folder, export transparent PNGs on-device. Optional Local API on 127.0.0.1:8000 for scripts and GIMP.
- Python: initialize the model once, then loop remove_background over paths. Local mode caches weights (~495MB) after first download.
- Docker: point batch jobs at the local FastAPI service. Same /v1.0/image-without-background contract as cloud.
- Pro API rate limit (product): 30 requests/minute per API key. Plan workers accordingly; 1 credit per successful paid image.
FAQ#
What is the fastest local path for a photo folder?#
On Apple Silicon, the Mac app batch flow. For Linux servers, Docker GPU if available, otherwise service-cpu or Python open_weights.
Can I mix local and Pro in one pipeline?#
Yes. Run Open Weights for the bulk, then route hard cases to Pro. Python can flip modes; HTTP clients can target local Docker or api.withoutbg.com.
Is there a CLI?#
The Python package includes CLI-oriented usage. A dedicated CLI docs page is still coming; use the Python docs for batch examples today.
Will batch uploads be stored on Pro?#
No. API images are processed in RAM and discarded after the response. Metadata logs do not include image bytes.
Next steps#
Pick an entrypoint. All product paths are linked from the use cases hub.