Remove background from a PNG that already has transparency on Sume
Sume's rmbg route accepts a PNG that already has alpha. Substantial-alpha inputs are flattened onto mid-gray #808080 first, and it is billed once.

Yes: run it through the cutout route anyway. In Sume's tool description for rmbg_create, the route is for any cutout request including when the source already has alpha, and it says not to skip. Inputs with substantial alpha are automatically flattened onto mid-gray #808080 before the background model sees them, and it is one bill. The output is a cutout PNG with alpha.
What Sume's description says
From the Sume MCP tool description for rmbg_create, which maps to POST /v1/rmbg-1.0/remove, model id sume/rmbg-1.0.
| Item | Fact |
|---|---|
| Route | POST /v1/rmbg-1.0/remove |
| Input | image_url, public HTTPS |
| Output | Cutout PNG with alpha |
| Already transparent | Do not skip; substantial alpha is flattened onto #808080, one bill |
| Cost | About $0.0198 per image after margin |
Why flatten
A background model works on pixels it can see. A mostly transparent image can hide the subject edge, so the route puts it on a neutral gray first. That is why a gray fringe is worth checking on semi-transparent regions such as glass or soft shadows.
Send it
Submit the hosted PNG and read the job result.
import os, requests
r = requests.post(
"https://api.sume.com/v1/rmbg-1.0/remove",
headers={"Authorization": f"Bearer {os.environ['SUME_API_KEY']}"},
timeout=60,
json={"image_url": "https://example.com/already-transparent.png"},
)
print(r.status_code)
print(r.json())Check the edges
Open the result on a dark and a light background. If you see gray halos, the source probably had soft alpha near the edge; clean that mask in the source and run again.
Sources
Related posts
More in Developers
- Retry an avatar video request without paying twice
A timed-out avatar video submit can be retried safely with the same Idempotency-Key. What Sume returns, what causes a 409, and how to build the key.
- Ruby Net::HTTP: submit and poll a Sume job with one key
A Ruby recipe using only Net::HTTP: submit a Sume image job with an Idempotency-Key, set open and read timeouts, poll status_url, and return the artifact URLs.
- Runway ephemeral uploads: 24 hours, 200 MB vs Sume HTTPS inputs
Runway ephemeral uploads give a runway:// URI valid for 24 hours and up to 200 MB. Sume takes public HTTPS URLs instead. What that changes in your pipeline.
- Runway input limits: 16 MB image, 32 MB video, HEAD required
Runway URL inputs need HTTPS, a hostname, valid Content-Type, HEAD support and no redirects. A checklist, and how it applies to Sume input URLs.
Written by Sume