remove.bg bg_color replacement: Sume RMBG gives a transparent PNG
remove.bg's API has bg_color and bg_image_url. Sume RMBG 1.0 takes only an image_url and returns a PNG with alpha, so the new background is a second step.

Sume RMBG 1.0 has no bg_color or bg_image_url. Its request takes an image_url and the completed result is a PNG with alpha, so a background color or scene is something you add in a second step.
remove.bg's changelog lists bg_color (added 2019-04-15) and bg_image_url (added 2019-06-03). Sume's side is from the API reference and image docs, read 2026-10-01.
What does the Sume removal request accept?
The schema is described as "Sume RMBG 1.0 background-removal request. Provide a public HTTPS image_url." The required field list is image_url and nothing else; the other fields are sync_mode, metadata, and delivery fields such as mode. Unknown fields are not accepted by the schema.
How do I get a colored or scene background?
Two documented paths. For a flat color, composite the transparent PNG over that color in your own code or editor. For a generated scene, pass the cutout's public HTTPS URL in input_references of an image request and describe the new background in the prompt; the field is described as "Reference images for image-to-image". White background to lifestyle scene walks through that second step.
| remove.bg parameter | On Sume |
|---|---|
bg_color | No equivalent field; composite the PNG yourself |
bg_image_url | No field on RMBG; use an image request with input_references |
format | Result is PNG with alpha |
Does the input need to be opaque?
No special handling is required, but the OpenAPI description notes that when the input already has substantial fully transparent pixels, Sume flattens it onto mid-gray #808080 before provider submission so edges stay clean, still as one billed removal.
What should I do first?
Find where your code sets bg_color. If it is a plain color, move that into a compositing step after download. If it is an image, plan the second request.
Sources
Related posts
More in Developers
- remove.bg crop and roi parameters: what Sume RMBG does instead
remove.bg has crop, roi, crop_margin, scale and position. Sume RMBG takes an image_url only and rejects other fields, so cropping happens before or after.
- remove.bg PNG over 10 MP unsupported: Sume RMBG limits
remove.bg does not support PNG above 10 megapixels; use WebP or ZIP up to 50 MP. Sume RMBG returns PNG with alpha and caps compressed input at 20 MiB.
- remove.bg type parameter (car, product, person) vs Sume RMBG
remove.bg's API has a type parameter and an X-Type header. Sume RMBG 1.0 has no foreground-type hint: send an image_url and Sume selects the model.
- gen3a_turbo no longer available on Runway: re-read Sume's model list
Runway now fails requests for gen3a_turbo and gen4_aleph. Avoid the same break on Sume: read /v1/videos/models instead of hard-coding ids.
Written by Sume