Identify which limit the job actually exceeds
A print designer asks for a transparent cutout from a 6000 × 5000-pixel product photograph. That is a fictional 30-megapixel source, not a measured provider result. Asking for PNG does not establish that the service can deliver those dimensions. Separate source dimensions, requested processing size, output format and the file the designer will receive.
remove.bg documents a 10 MP PNG cap and transparent WebP or ZIP outputs up to 50 MP. Its changelog identifies a 25 MP compatibility maximum for auto and a separate 50MP size value. Choosing a large-capable format while retaining an insufficient size request can still miss the brief. Check current accepted values and inspect the actual returned dimensions; an upper limit is not a guarantee that every source produces that many useful pixels.
Choose a handoff the designer can use
Ask whether the receiving application can place the intended WebP result with its alpha intact. If so, verify that route on an actual copy before delivery. If the integration uses ZIP, do not rename the archive to PNG or send its color file alone as a transparent cutout.
The documented ZIP contains color.jpg and alpha.png. The color image includes edge-color corrections, while the grayscale matte carries opacity: white foreground and black background. Compose the supplied pair, with the correct alignment, rather than applying the matte to an unrelated or differently cropped source. An exported PNG produced after composition is a separate local file; it does not mean the API’s PNG-output limit has disappeared.
| Receiving workflow | Candidate delivery | Required check |
|---|---|---|
| Application accepts the large transparent WebP | Verified returned WebP | Actual dimensions and alpha survive placement |
| Integration receives color and matte in ZIP | Correctly composed output plus original pair if required | Alignment, opacity and edge appearance |
| Designer receives only color.jpg | Incomplete transparency handoff | Supply or compose the matching matte |
| Result is smaller than the specification | Hold for request and source review | Size parameter, source pixels and actual output |
Inspect the composition rather than its filename
For the fictional product, compare the delivered cutout with the authorized photograph on both a light and a dark review background. Inspect handles, narrow gaps, soft edges and printed labels. A 30 MP canvas can contain a poor mask or an enlarged low-detail subject. Pixel count therefore answers a different question from whether the product is depicted correctly.
Keep the original returned pair if ZIP was used, the composition method, the final dimensions and the designer’s actual placement result in the handoff record. No ZIP was downloaded from a generation request and no compositing test was executed for this illustration.
Agree on the final production asset
The product-photo delivery-format guide covers the general receiving-format choice. The transparent versus white-background guide covers the intended background. This specific problem adds a provider’s size-by-format boundary and a two-file composition requirement. Close it only when the receiving designer has the correct usable file, adequate source-supported detail and an accepted mask—not merely an archive labeled “high resolution.”