XPRTIX Video

Fix hev1 video for iPhone.

Turn an hev1 HEVC video into hvc1 so it plays on iPhone, iPad and Safari. No re-encode, and the file stays on your device.

moov → fronthev1 → hvc1ProRes → H.264AC-3 → AAC
Drop your videos here or click to browse MP4MOVM4V Up to 50 MB when a re-encode is needed

XPRTIX Video

Fix hev1 video for iPhone: how it works

The problem

HEVC (H.265) video can be labelled hev1 or hvc1 inside an MP4. They describe identical video; only the label differs. Apple's players play hvc1 and refuse hev1, so a perfectly good video shows a black screen or will not play at all on iPhone, iPad or in Safari. Many cameras, screen recorders and editors write hev1.

The fix

Because the video itself is fine, the fix is to rewrite the label, not to re-encode. XPRTIX Video does that in your browser: drop the file and it shows hev1 in the report, then gives you a corrected MP4. Quality is bit-for-bit identical to the original, and it takes seconds.

If that's not the cause

The same check also looks for the moov atom at the end of the file, codecs iOS does not support and audio that plays as silence. The report lists whatever it finds.

Why it fails

Why videos don't play on iPhone

A video can be perfectly valid and still refuse to play on iOS. These are the four usual causes. XPRTIX Video repairs all of them.

  1. 01

    The moov atom is at the end

    An MP4 keeps its metadata (track layout, codecs, sample offsets) in a box called moov. Written after the media data, a player must download the entire file before it can start. Moving it to the front is faststart.

    Fixed in your browser
  2. 02

    HEVC tagged hev1, not hvc1

    Both tags describe identical HEVC video; only the label differs. Apple plays hvc1 inline and refuses hev1. The video itself is unchanged, so this is a tag rewrite and quality is untouched.

    Fixed in your browser
  3. 03

    A codec iOS won't decode

    MPEG-4 Part 2, ProRes and VP9 need converting to H.264, as do the H.264 High 4:2:2 and 4:4:4 profiles: valid H.264 that iOS still refuses to play.

    Re-encoded on the server
  4. 04

    Audio that plays as silence

    AC-3, E-AC-3 and PCM tracks leave you with a video that plays with no sound at all on iOS. They are converted to AAC.

    Re-encoded on the server

Transparency

What leaves your device

Said up front, before anything is dropped.

Stays on your device

  • Checking every video. Only the atom headers and the moov box are read: a few kilobytes, whatever the file size.
  • Faststart and hev1 → hvc1 repairs. They are container rewrites, so the video is never uploaded.

Sent to the server

  • Only a video that needs re-encoding: an unsupported codec, profile or audio track.
  • The upload is deleted as soon as the encode ends, and the result shortly after you save it.

Recorded

  • Anonymous usage data: the file name, size and format details, what was done and whether it worked.
  • Never the video itself. No account, no tracking across sites.

Video guides

Common Video jobs

Questions

Asked often

Does changing hev1 to hvc1 reduce quality?

No. Only the tag changes; the encoded video is copied across untouched.

Is my video uploaded?

No. The tag change is a container edit that runs in your browser.

How can I tell if my video is hev1?

Drop it here. The report names the tag it found.

Why does my HEVC video play on Windows but not on iPhone?

Windows and Android players accept both tags. Apple only plays hvc1 inline, so the same file fails only on Apple devices.

Can I fix hev1 with ffmpeg instead?

Yes: ffmpeg -i in.mp4 -c copy -tag:v hvc1 out.mp4 does the same thing. This page does it without installing anything.

Does the fix work for MOV files?

Yes. MP4, MOV and M4V are accepted, and you get an MP4 back.