Overview
HEIC Converter runs on the same conversion service as Image Converter. The file must be sent as a multipart upload in the `image` field; URLs are not fetched, and files over 10MB are rejected with a 413. The service is ImageMagick-based, so HEIF and other image formats are accepted too, and the source format is taken from the file extension.
`outputFormat` is required; jpeg is treated as jpg, and a missing or unsupported value returns a 400 listing the accepted formats. `quality` defaults to 90 and applies to lossy targets such as jpg and webp; PNG output is lossless and ignores it. `maxWidth` and `maxHeight` (paid) fit the image inside those bounds while keeping its aspect ratio; setting either adds `resized: true` to the response.
The converted file is stored for two days. `downloadURL` points to it and `expires` is the deletion time in milliseconds since the Unix epoch, so download or copy the file before then. `id` is the identifier of the stored file. `inputFormat` and `outputFormat` report what the converter read and wrote, `mimeType` is the content type of the result, and `inputSize` and `outputSize` (paid) are in bytes. Each conversion has a 25-second limit on the conversion service, and a file it cannot decode returns a 400 saying the file could not be read as an image. `outputWidth` and `outputHeight` (paid) are the pixel dimensions read from the converted file.
Live Test HEIC Converter API →
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl -X POST https://api.apiverve.com/v1/heicconverter \
-H "x-api-key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"outputFormat": "png"
}'const res = await fetch('https://api.apiverve.com/v1/heicconverter', {
method: 'POST',
headers: {
'x-api-key': 'your_api_key_here',
'Content-Type': 'application/json',
},
body: JSON.stringify({
"outputFormat": "png"
}),
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.post(
"https://api.apiverve.com/v1/heicconverter",
headers={"x-api-key": "your_api_key_here"},
json={
"outputFormat": "png"
},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
"strings"
)
func main() {
body := strings.NewReader(`{
"outputFormat": "png"
}`)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/heicconverter", body)
req.Header.Set("Content-Type", "application/json")
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Parameters
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
imageRequired | string | Upload a HEIC or HEIF image file to convert |
outputFormatRequired | string | Target formatpngjpgjpegwebpgiftiff |
qualityOptional | integer | Output quality (applies to jpg/webp) default 90 · range 1–100 |
maxWidthOptionalPremium | integer | Maximum width in pixels (maintains aspect ratio) range 1–10000 |
maxHeightOptionalPremium | integer | Maximum height in pixels (maintains aspect ratio) range 1–10000 |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"id": "f8e7d6c5-4321-09ab-fedc-ba0987654321",
"inputFormat": "heic",
"outputFormat": "jpg",
"inputSize": 3145728,
"outputSize": 892456,
"mimeType": "image/jpeg",
"expires": 1707350400000,
"downloadURL": "https://storage.googleapis.com/apiverve/heicconverter/f8e7d6c5.jpg"
},
"code": 200
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
id | string | "f8e7d6c5-4321-09ab-fedc-ba0987654321" | Unique conversion task identifier |
inputFormat | string | "heic" | Original image format (HEIC or HEIF) |
outputFormat | string | "jpg" | Converted image output format |
inputSizePremium | number | 3145728 | Original image size in bytes |
outputSizePremium | number | 892456 | Converted image size in bytes |
mimeType | string | "image/jpeg" | MIME type of converted image file |
expires | number | 1707350400000 | Download URL expiration timestamp (milliseconds) |
downloadURL | string | "https://storage.googleapis.com/apiverve/heicconverter/f8e7d6c5.jpg" | Temporary download URL for converted image |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Classifieds Photo Ingestion
- When mobile sellers submit listings from iPhones, e-commerce marketplaces convert uploaded HEIC files to WebP and fetch the converted images via temporary download links.
- Accident Claim Evidence
- Insurance claim portals convert damage photos uploaded by drivers from HEIC to standard PNG files before attaching verified visual evidence to adjusters' case files.
- Telehealth Photo Submissions
- Patient portals transform medical rash and wound snapshots from HEIF to JPG so consulting physicians can view records on clinic desktop browsers.
- Photobook Print Production
- To prepare customer snapshot submissions for print presses, photo printing platforms turn uploaded HEIF camera files into TIFF images before starting print runs.
Set up HEIC Converter
Ready to put it to work? Set up HEIC Converter on APIVerve.
Related
More in Images: