The server says the image is missing
The multipart field must be named image. Sending a raw file body, JSON, or a field named file will not satisfy this endpoint. In cURL, use --form 'image=@logo.png'.
Multipart data cannot be read
Do not manually set Content-Type: multipart/form-data in a Fetch request. The browser or HTTP library must add its boundary. Let it generate that header from the FormData body.
A small file exceeds the image limit
Compressed file size and decoded pixel count measure different things. Check the width multiplied by the height. Resize the image to 4,000,000 pixels or fewer and upload it again.
The SVG will not open
Save the svg property from the JSON response, not the whole response object. A usable file starts with SVG markup, rather than an opening JSON brace. Write the file as UTF-8 with a .svg extension.
Edges or small text look different
Try a cleaner source image and compare at the intended display size. Tiny text, soft gradients, compression artifacts, and photographic detail can turn into shapes you may want to edit manually. SVG conversion cannot recover information absent from the source image.
Fetch works on the server but fails in the browser
Check whether your page and the API are on different origins. The current endpoint does not declare CORS headers. Send the conversion request through your application’s server rather than disabling browser security or using an untrusted public proxy.
The preview has unexpected space around it
Inspect the SVG’s viewBox and the source canvas. Empty pixels around the original can remain part of the output’s coordinate area. Crop the source before converting, or adjust the output in your vector editor.
The service does not respond
Keep the selected file available, display a useful error, and offer a retry. Check the HTTP status and network response before debugging SVG rendering. An aborted request in your application is different from an invalid image response from the API.