XPRTIX Video

Convert MOV to MP4.

Get an MP4 that plays on iPhone, iPad and the web. Usually repackaged in your browser without re-encoding.

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

Convert MOV to MP4: how it works

MOV and MP4

MOV and MP4 are both containers, boxes that hold video and audio. MOV is Apple's, MP4 is the standard one the web uses. Often the video inside a MOV is already H.264 or HEVC, which MP4 can hold as it is, so converting is a matter of repackaging rather than re-encoding.

How XPRTIX handles it

Drop a MOV (or MP4, or M4V). The tool reads the file, tells you what is inside, and returns an MP4. If the video is playable on iPhone it is repackaged in your browser, and quality is identical. If it holds a codec iOS cannot play, such as ProRes or MPEG-4 Part 2, or audio such as AC-3, that part is converted to H.264 or AAC on the server, which handles files up to 50 MB.

What to expect

Repackaging takes seconds. A re-encode takes longer and depends on the length and size of the video.

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

Will the quality change?

Not when the video is only repackaged, which is the usual case. Re-encoding is used only for codecs iOS cannot play.

Can I convert a large MOV?

Repackaging in the browser has no practical limit. Files that need re-encoding are limited to 50 MB.

Does it keep the sound?

Yes. Audio that iOS cannot play, like AC-3, is converted to AAC so the sound still works.

Does it convert ProRes MOV files?

Yes. ProRes is converted to H.264 on the server, which handles files up to 50 MB.

Is my video uploaded?

Only when it needs re-encoding. Repackaging happens in your browser and the file never leaves your device.

Will my MP4 play on Android and Windows too?

Yes. H.264 or HEVC video with AAC audio in MP4 plays on nearly every device.