BackgroundErase can be used in two main ways: through the web interface (Studio) or via the API. Both use the same underlying models, but they are designed for very different workflows.
Quick summary: Studio is best for manual, one-off edits. The API is best for automation, scale, and production integrations.
Web (Studio)
The web experience is designed to be simple and fast. You upload an image, BackgroundErase removes the background, and you download the result.
- Manual upload and manual download.
- No coding required.
- Great for quick tests, previews, and small batches.
- Full-resolution PNG downloads available.
- Output format is always PNG.
Limitations: The web UI is not designed for automation or high-volume processing.
API
The BackgroundErase API lets you integrate background removal directly into your own applications, services, or pipelines.
- Fully automated and programmable.
- Supports batch and high-volume workflows.
- Control output format (PNG, JPG, WebP).
- Optional flags like despill, crop, size, etc to tune your results.
- Ideal for production systems and scale.
Best for: Developers, automation, backend services, and large-scale image processing.
API Playground
If you want to experiment with API behavior without writing code, use the API Playground . It lets you reproduce API results directly from the browser.
- Test API flags and options interactively.
- See exactly how different parameters affect output.
- Match Playground results to real API calls.
Which should I use?
- Just removing a few images manually? → Studio
- Building a product or workflow? → API
- Want to test API flags visually? → API Playground