Image
Pixelcut Background Remover
Prepare an image cutout with Pixelcut Background Remover.
- Image editing
Sign in to create. Review the credit cost in the studio before running.
Catalog preview for Pixelcut Background Remover. Review your own result before publishing.
A starting point.
Prepare an image cutout with Pixelcut Background Remover. Start from a clear source whose foreground you can inspect around fine edges.
Before you publish.
Check jewelry gaps, hair and translucent areas against the original. Test the result on the background where it will be used.
Review the quote before running. A failed generation releases its reserved credits. Download the results you want to keep; stored media is retained for 30 days.
Settings and model questionsCheck the available settings and guidance when preparing your input.
Inputs and settings
Provide image_url with a JPEG or PNG source. This Raywake operation exposes the source image as its user input.
Inspect the delivered cutout rather than relying on the catalog preview. Keep transparency when exporting for a composite; JPEG cannot retain it.
Inputs, all modes and APIModel IDs, current input limits and the API generation workflow.
Supported inputs
These fields come from the current studio form for pixelcut/background-removal. Other modes may require different inputs.
| Input | Type | Requirement |
|---|---|---|
image_url | Text | Required |
Check the full model schema for all options and cross-field rules. Request a quote for your selected settings before generating.
Use Pixelcut Background Remover through the API.
Start with this model ID for the endpoint featured on this page:
pixelcut/background-removal
Input requirements belong to this model ID. Check a different mode’s schema separately when switching modes.
Check the current model schema for supported inputs and options. Other tasks may use different model IDs.
From quote to result.
Request a credit quote for your input and settings before submitting a generation. A sample output or the price of another model is not a quote for your request.
Follow the generation workflow, then poll the job for its status and result. The API and studio use the same balance.