Convert HEIC to JPG with curl
Convert an image to JPG, PNG, WebP, AVIF, GIF, TIFF or BMP. Reads HEIC (iPhone photos) and ICO too. Here is the whole call with curl, with the output it produced when we ran it.
Before you start
- An API key. Create a free account; it comes with free tokens every month. Put the key in an environment variable so it stays out of your code:
export BLOODWEB_KEY=your_key - curl 7.76 or later (for
--fail-with-body, which makes curl stop on an error and still show the reason). - The input file in the same folder:
photo.heic. Use your own; that is the name the code expects.
The code
Save it as image-convert.sh and run bash image-convert.sh.
curl -sS --fail-with-body \
-H "Authorization: Bearer $BLOODWEB_KEY" \
-F file=@photo.heic \
-F to=jpg \
https://bloodweb.net/api/v1/image-convert \
-o photo.jpg
What you get
Tested 19 October 2026: this exact code ran against our test copy of the API, which runs the same service code as bloodweb.net, and produced this.
It writes photo.jpg: a JPEG image, 1600 × 1200 pixels, 36 KB.
Change the call
Every option the Image converter takes. Add or change them the same way as the ones in the code.
torequired: The output format. One of: jpg, png, webp, avif, gif, tiff, bmp.quality: For JPG, WebP and AVIF.strip: Remove metadata such as camera details and GPS location.background: Fills transparent areas when the output format has no transparency (JPG, BMP).rotate: Turn the image clockwise, in degrees, after it is put the right way up. One of: 0, 90, 180, 270.flip: Mirror the image. One of: none, horizontal, vertical.grayscale: Convert to black and white.
If it fails
A failed call is not charged. The answer is JSON with an error object; curl stops with an error, and that JSON lands in photo.jpg instead of the result, so open it as text to read the reason. The usual ones:
- 401
missing_keyorinvalid_key:BLOODWEB_KEYis not set in the shell that runs the code, or the key was revoked. - 415
unsupported_type: the file is not a type this service reads. The type is read from the file itself, so renaming a file does not change it. - 413
file_too_large: the file is over the limit on the service page. - 402
insufficient_tokens: the balance does not cover the call. Top up in the dashboard. - 429
rate_limited: too many calls at once. Wait the seconds in theRetry-Afterheader and send it again.
Every code and its fix is in the docs.
Next
- The Image converter page: every option, the limits, and Try it now in your browser.
- Getting started: keys, errors and rate limits for all the services.