Inspect the input representation first
A developer submits a vector logo to Recraft Remove Background with image_format set to png, then receives an SVG URL. This is not necessarily an ignored API setting. The provider documents a format-dependent response: SVG inputs produce SVG, while raster inputs can produce the selected raster output format. The service is not a universal SVG-to-PNG conversion endpoint. Preserve the exact submitted file type and response object before changing code.
Use the correct request and response contract
The documented endpoint is POST /v1/images/removeBackground. For JSON input, image_url identifies a reachable URL or data URL; multipart upload uses file. For raster results, image_format defaults to lossless webp and may be set to png. For SVG, that setting does not change the result type. The response contains one image object with a url, not a data array of candidates. Returned URLs are temporary, so an authorized integration should retrieve and retain the approved result according to its storage policy.
Illustrative integration matrix
A fictional packaging system processes two assets: LOGO-V5.svg and BOTTLE-FRONT.png. Request A sends LOGO-V5.svg with image_format png; the expected documented result type is SVG, not PNG. Request B sends the PNG bottle source and explicitly requests png; that is the raster-to-PNG route to evaluate. Request C sends an unsafe or oversized SVG and expects the format field to bypass validation: reject that assumption. These are request-planning examples, not executed API calls, observed HTTP responses or billed jobs.
Validate the source before blaming output format
Recraft lists PNG, JPG, WebP and SVG as accepted input types, with size, dimension and pixel limits. The current page specifies under 20 MB, up to 16 megapixels and side lengths between 256 and 4096 pixels; small SVGs may be scaled during processing. Do not assume a malformed SVG can be made safe by requesting PNG. If a request fails, retain the actual error body and distinguish unsupported input from a successfully returned SVG. If a product requires exact label pixels, inspect the cutout and alpha or vector paths rather than treating an accepted response as approval.
Choose conversion and retention separately
If the downstream poster truly requires PNG, convert an approved SVG output through a separately validated rasterization workflow at the intended dimensions, or begin from a suitable raster source. Do not imply the remove-background endpoint performed that conversion. Store the returned artifact before its temporary link expires, record actual MIME type and dimensions, and compare it with the approved original. The Canva SVG/raster guide explains a different export boundary; the temporary-link guide covers why a result URL is not permanent campaign hosting. No CartVisual API integration is asserted.