HEIC Converter API

POST

Deliver iPhone photos in formats every browser can display.

HEIC Converter transforms Apple HEIC and HEIF images to web-friendly formats. Perfect for processing iPhone photos that need to be converted for websites, apps, or services that don't support HEIC.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/heicconverter

Body

outputFormatstring

image

Click or drag a file to upload.heic, .heif · max 400KB for live testing

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "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
}

About the HEIC Converter API

HEIC (High Efficiency Image Container) is Apple's default photo format since iOS 11. While it offers great compression, many platforms don't support it. This API converts HEIC to universally supported formats like PNG, JPG, or WebP.

What people use it for

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.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Questions.

Common questions about the HEIC Converter API.

Read the docs →

Which formats can this API convert between?

The API accepts raw Apple .heic and .heif image files and converts them into PNG, JPG, or WebP formats. You can also specify an output quality setting when converting to JPG or WebP.

What is the maximum file size for image uploads?

You can upload HEIC or HEIF files up to 10 MB in size. Files must be passed as an image upload in your POST request.

Can I resize images and read file sizes on the Free plan?

No. Custom resizing via maximum width and height parameters, as well as the input and output size byte counts in the response, require a paid subscription. Any paid plan starting with Starter unlocks these features.

Which plan fits converting 5,000 iPhone photos a month?

The Starter plan fits this volume comfortably. Each conversion consumes 10 credits, meaning the Starter plan's 200,000 monthly credits cover up to 20,000 conversions, which works out to about $0.0015 per image. The Free plan includes 20 conversions each month for testing.

How long are converted image download links valid?

The API returns a temporary download URL along with an expiration timestamp in milliseconds. You must fetch and store the converted file before that expiration window passes.

Request parameters — POST /v1/heicconverter

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`image`Required	string		Upload a HEIC or HEIF image file to convert
`outputFormat`Required	string	`png`	Target format `pngjpgwebpgiftiff`

Optional

Parameter	Type	Example	Description
`quality`Optional	integer	`90`	Output quality (applies to jpg/webp) default 90 · range 1-100
`maxWidth`OptionalPremium	integer	`1920`	Maximum width in pixels (maintains aspect ratio) range 1-10000
`maxHeight`OptionalPremium	integer	`1080`	Maximum height in pixels (maintains aspect ratio) range 1-10000

Example request

curl -X POST "https://api.apiverve.com/v1/heicconverter" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"outputFormat":"png","quality":90,"maxWidth":1920,"maxHeight":1080}'

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

401 is the only auth verdict

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.

Response — POST /v1/heicconverter

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "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
`inputSize`Premium	number	`3145728`	Original image size in bytes
`outputSize`Premium	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

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	HEIC Converter calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — POST /v1/heicconverter

No SDK to install — this is a plain HTTPS call to /v1/heicconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/heicconverter" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/heicconverter-apiSource, issues and the examples this page is built from.ReferenceHEIC Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/heicconverternpm apiverve-heicconverterPyPI APIVerve.API.HEICConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — POST /v1/heicconverter

Install the Node.js SDK, then call the HEIC Converter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/heicconverter

Node.js

const res = await fetch("https://api.apiverve.com/v1/heicconverter", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/heicconverterThe published Node.js client, versioned and signed.GitHubapiverve/heicconverter-apiSource, issues and the examples this page is built from.ReferenceHEIC Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-heicconverterPyPI APIVerve.API.HEICConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/heicconverter

Install the Python SDK, then call the HEIC Converter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — PyPI

pip install apiverve-heicconverter

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/heicconverter",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-heicconverterThe published Python client, versioned and signed.GitHubapiverve/heicconverter-apiSource, issues and the examples this page is built from.ReferenceHEIC Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/heicconverternpm APIVerve.API.HEICConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — POST /v1/heicconverter

Install the C# / .NET SDK, then call the HEIC Converter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.HEICConverter

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/heicconverter");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.HEICConverterThe published C# / .NET client, versioned and signed.GitHubapiverve/heicconverter-apiSource, issues and the examples this page is built from.ReferenceHEIC Converter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/heicconverternpm apiverve-heicconverterPyPI

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/heicconverter

No SDK to install — this is a plain HTTPS call to /v1/heicconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/heicconverter", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/heicconverternpm apiverve-heicconverterPyPI APIVerve.API.HEICConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/heicconverter

No SDK to install — this is a plain HTTPS call to /v1/heicconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/heicconverter");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/heicconverternpm apiverve-heicconverterPyPI APIVerve.API.HEICConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/heicconverter

No SDK to install — this is a plain HTTPS call to /v1/heicconverter with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/heicconverter")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/heicconverternpm apiverve-heicconverterPyPI APIVerve.API.HEICConverterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

QR Codes Are Back (And This Time It's Different)Remember when QR codes were a punchline? Now they're everywhere. Here's why this time it stuck.Read

QR Codes: More Useful Than You ThinkURLs, WiFi passwords, contact cards, payment links—QR codes do more than you'd expect. Here's how to generate and read them programmatically.Read

Content Moderation: Protect Your Platform From UGCUser-generated content is a liability until it's moderated. NSFW detection, profanity filtering, spam detection—here's how to automate it.Read

HEIC Converter API

Try it — live request, no key required

About the HEIC Converter API

What people use it for

Ways to call it

Questions.

Request parameters — POST /v1/heicconverter

Required

Optional

Authentication

Response — POST /v1/heicconverter

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — POST /v1/heicconverter

Resources

Also published for

Call it from Node.js — POST /v1/heicconverter

Resources

Also published for

Call it from Python — POST /v1/heicconverter

Resources

Also published for

Call it from C# / .NET — POST /v1/heicconverter

Resources

Also published for

Call it from Go — POST /v1/heicconverter

Resources

Also published for

Call it from PHP — POST /v1/heicconverter

Resources

Also published for

Call it from Ruby — POST /v1/heicconverter

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — HEIC Converter API

Images

Related articles

Ready to build with HEIC Converter? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog