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's API page says PNG images above 10 megapixels are not supported, and sends you to WebP or ZIP (up to 50 megapixels) if you need transparency at that size. Sume's RMBG 1.0 sets its ceiling differently: compressed input is capped at 20 MiB, and the result is a PNG with alpha.
The remove.bg wording is from its API page; the Sume wording is from the API reference and Sume's work-bounds notes, read 2026-10-01. The two limits are measured in different units, so compare them by testing your own files.
What does remove.bg say about large images?
Output resolution is listed as up to 50 megapixels. PNG and the other formats are shown with that ceiling, with one exception: "PNG images above 10 megapixels are not supported". For transparency at that size it recommends WebP or ZIP, and ZIP for the fastest processing. The page also says background removal moves to Leonardo.Ai on December 1, 2026.
What are the Sume RMBG limits?
The route is /v1/rmbg-1.0/remove, and the request needs a public HTTPS image_url. The OpenAPI text says "Completed results expose mirrored PNG artifacts with alpha." Sume's work-bounds notes add that RMBG preparation admits at most two inputs before fetching, that compressed input is capped at 20 MiB, and that alpha decoding and scanning runs in a worker with a 10-second deadline.
| Item | remove.bg | Sume RMBG 1.0 |
|---|---|---|
| Limit unit | Megapixels | Compressed bytes (20 MiB) |
| PNG result | Not supported above 10 MP | Result is PNG with alpha |
| Other transparent formats | WebP, ZIP up to 50 MP | Not listed in the request schema |
| Input | Upload or URL | Public HTTPS image_url |
What should I check before migrating?
List the largest files you send today. If they are PNG-heavy and close to 10 MP, you already use WebP or ZIP on remove.bg; on Sume you would send the source as a public HTTPS URL and receive PNG. Check the compressed size of your biggest originals against 20 MiB and run a few through. See remove image background API for the request shape.
What about a file that is too large?
Resize or recompress it before upload so it stays under the compressed-size cap. Sume's image upscale route is separate if you need pixels back afterward; see AI image upscale API.
Sources
Related posts
More in Developers
- 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.
- Replicate aborted vs canceled prediction: Sume cancel and 409
Replicate bills a canceled prediction for run time, not an aborted one. Sume cancels only before generation starts, then returns 409.
- Replicate webhook_events_filter on Sume: terminal events only
Replicate lets webhook_events_filter pick start, output, logs and completed. Sume webhooks send terminal job events only, so there is no filter to set.
- Replicate webhook URL custom id vs Sume job_id as the key
Replicate suggests a query param like customId on the webhook URL. Sume bodies carry request_id and job_id, and job_id is the receiver's idempotency key.
Written by Sume