remove.bg crop and roi parameters: what Sume RMBG does instead

Sume's RMBG request has no crop or region-of-interest field. It takes a public HTTPS image_url and returns a PNG with alpha. If you used crop, roi or crop_margin on remove.bg, do that work on the image before you send it or on the PNG after it comes back.

remove.bg's changelog lists crop and roi (2019-06-03) and crop_margin, scale and position (2019-06-26). Sume's side is from the API reference, read 2026-10-01.

What do the remove.bg parameters do?

Per the changelog, crop crops off empty regions and roi specifies a region of interest. crop_margin, scale and position came a few weeks later. Together they decide where the subject sits in the output.

What does Sume accept?

The request schema is marked "additionalProperties": false, so an unlisted field such as crop is not part of the contract. The fields it does list are image_url, sync_mode, metadata and delivery fields such as mode. Completed results are PNG artifacts with alpha.

Is there a Sume way to resize?

Upscale is its own route, /v1/image-upscale-1.0/upscale, with an upscale_factor described as "Upscale factor (default 2)" and a maximum of 4. It enlarges; it does not crop. The order of cutout and upscale matters, and remove background and upscale: which first covers it.

What should I do about a tight crop?

Find the bounding box of the non-transparent pixels in the returned PNG and crop to it plus the margin you want. That is a few lines in any image library and keeps the margin under your control.