Last updated

HEIC to Text

Free HEIC OCR — iPhone photos read directly, no JPG conversion first.

VisionParse converts HEIC photos — the iPhone camera default since iOS 11 — to editable text free, with no account and no converting to JPG first.

HEIC needs a decode step most OCR tools skip, which is why so many reject iPhone photos outright. We measured it end to end: a quality-85 HEIC (87.8 KB) and a quality-30 HEIC (24.5 KB) both read at 100% character accuracy. Decoding adds about half a second — 1.0 to 1.2 seconds total against 0.6 for a JPEG.

Last updated: 2026-08-02 · Measured by VisionParse engineering

  • Free · no account
  • HEIC · HEIF
  • 3 MB · 3 pages
  • Deleted within 1h
No file yetReady

Drop an image to read it

HEIC, HEIF — up to 3 MB. Your file is read on our servers in Frankfurt and deleted within the hour.

5 files a day3 an hour3 MB a file3 pages a filedeleted after 1h

What this tool does, in numbers.

  • ACCURACY

    HEIC at quality 85 and quality 30 both read at 100% character accuracy in our measurement.

  • LANGUAGES

    VisionParse recognises 161 languages in HEIC photos, decoded on our servers with no JPG conversion first.

  • SPEED

    A HEIC page read in 1.0–1.2 seconds — the HEVC decode adds about half a second over JPEG.

  • LIMIT

    HEIC holds the same photo in roughly half the bytes of JPEG, so the 3 MB free limit goes further with iPhone photos.

  • ACCESS

    The HEIC to text tool requires no account, no email address and no payment card.

  • RETENTION

    VisionParse deletes free-tool HEIC files one hour after conversion.

Where the 100% at q85 and q30 comes from.

Every figure on this page traces to a dated run on hardware we name. Nothing here is a vendor estimate.

Measured 2026-08-02

Claim
iPhone HEIC reads directly at full accuracy: quality 85 and a 3.6× smaller quality 30 both scored 100%.
Method
VisionParse standard recognition tier, single-threaded. Full methodology.
Sample
One synthetic invoice encoded with heif-enc (x265) at quality 85 (87.8 KB) and quality 30 (24.5 KB), each decoded and read through the production pipeline and scored against ground truth.
Measured
2026-08-02 on Contabo Cloud VPS 8 — 8 vCPU AMD EPYC, 24 GB RAM, Ubuntu 24.04.4
Limitations
Synthetic render, not a handheld photo — real iPhone shots add focus, shadow and perspective effects that are about the camera, not the format. A single synthetic document per variant is a small sample and is not a substitute for a corpus. These figures describe format behaviour, not general accuracy. A 500-document corpus run is scheduled and will supersede them.
Contact
VisionParse@senithu.lk

What this tool gets wrong

HELD UP

The format is not the problem — HEIC reads like any other image. Once decoded, HEIC scored identically to JPEG and PNG on the same document. If an OCR tool rejects your iPhone photo, it is missing a decoder, not fighting a harder format.

KNOWN LIMIT

Decoding costs real time. HEVC decode roughly doubles per-file processing time: 1.0–1.2 seconds against 0.6 for JPEG. For one photo it is invisible; for a bulk archive, exporting to JPEG first halves the wait.

KNOWN LIMIT

Arabic-Indic numerals come back wrong. VisionParse reads Arabic script cleanly on the free tier, but ١٢٣ returned as 1#|. Numeric Arabic documents should use the AI extraction tier instead.

Three steps, no account.

  1. Drop your HEIC

    Straight from the iPhone — AirDrop, cable or cloud. No conversion needed.

  2. We decode and clean it up

    The HEVC image is decoded server-side, then deskew and contrast normalisation run — phone photos benefit most.

  3. Take the text

    Text appears with a confidence score. Copy it or download a .txt; the file is deleted within the hour.

What this tool accepts.

PropertyFree tool
Input formatsHEIC, HEIF
OutputPlain text, UTF-8
DecodeServer-side HEVC — no client conversion
Maximum file size3 MB (roughly double the photos of JPEG)
Rate limit5 files per hour, per IP address
Languages161
File retentionDeleted 1 hour after conversion
Processing locationFrankfurt, Germany

When to use the API instead.

This page converts one file now. To convert files from your own software, the same engine runs over HTTP from Starter upward.

# same engine, from your code
curl -X POST https://api.visionparse.app/v1/ocr \
  -H "x-api-key: $VISIONPARSE_KEY" \
  -F "file=@image.jpg"

→ 202 { "jobId": "c0df8e2c…" }

Use the API when

You convert more than a few files, convert on a schedule, or need results inside another system. Batch, webhooks and bounding boxes are API-only.

Frequently asked

Why do other OCR tools reject my iPhone photos?

HEIC needs an HEVC decoder that many tools do not ship. We decode it server-side — we measured the full path at 100% accuracy — so your photo works as-is.

Should I convert HEIC to JPG before OCR?

Not for accuracy — both read at 100% here. Convert only if you are processing a large batch and want the roughly 2× faster per-file time JPEG gives.

How do I get a HEIC file off my iPhone without converting it?

AirDrop and cable transfer keep HEIC as HEIC. If your phone silently converts on share, set Settings → Photos → Transfer to “Keep Originals”.

Is the HEIC to text tool free?

Yes — 5 files a day with no account, no email and no card. A free account raises the allowance to 100 pages a month.

Do you keep my HEIC photo?

Free-tool files are deleted one hour after conversion, and no customer file is ever used to train models.

Measured by VisionParse engineering. Method and raw data are published.Updated Benchmark · Method · Data handling