How to Convert MOV to Text: iPhone, ProRes & QuickTime (2026)

To convert a MOV file to text, upload it to a transcription tool that reads the QuickTime container format. Most tools extract the audio track automatically, ignoring the video entirely. The tricky part is not the upload, it is knowing which kind of MOV you have, because the codec inside determines whether a direct upload works or whether audio extraction is the smarter first step.

What Is Actually Inside a MOV File?

MOV is a container, not a codec. Apple's QuickTime container can hold wildly different video streams depending on where the file came from, but the audio story is simpler: almost every MOV you will encounter carries either AAC (for iPhone and QuickTime recordings) or PCM (for ProRes exports from Final Cut Pro). Both audio formats transcribe cleanly.

The variable is the video codec:

For transcription, the video codec column determines whether you can upload directly or should extract audio first. The audio codec column determines quality, and it is always fine.

Why Do HEVC MOVs Fail in Some Tools?

iPhone has recorded HEVC by default since iOS 11 (iPhone 8 / 2017). If you share that MOV with a web-based tool running on a Linux server that was not compiled with HEVC decoding, the tool cannot demux the video track. Some tools fail the job entirely on this error rather than falling back to audio-only processing.

The workaround is clean: extract the audio before uploading.

ffmpeg -i video.mov -vn -c:a copy audio.m4a

This copies the AAC stream out of the MOV container without re-encoding anything. A 30-minute iPhone 4K video (around 12 GB) becomes a 14 MB M4A file. Upload time drops from minutes to seconds.

To toggle what codec iPhone uses: Settings, Camera, Formats. "High Efficiency" = HEVC. "Most Compatible" = H.264. High Efficiency gives smaller files but can cause the compatibility problems described above. H.264 avoids them at the cost of storage.

What Makes ProRes MOVs Different?

ProRes is a post-production intermediate codec, not a distribution codec. Apple designed it to preserve maximum quality through editing roundtrips, not to be small. ProRes 422 at 4K 30fps runs roughly 540 MB per minute. ProRes 422 HQ runs around 1.2 GB per minute. iPhone 15 Pro shooting ProRes clips can hit 5.5 GB per minute.

The audio inside ProRes MOVs is Linear PCM, which is lossless. This is good for transcription accuracy but irrelevant to file size, the PCM audio track is typically under 10 MB/min even when the video is enormous.

The correct path for ProRes MOVs is always audio extraction first. In Final Cut Pro: File, Share, Master File, then select Audio Only. This produces an M4A. From the command line:

ffmpeg -i prores_export.mov -vn -c:a copy output.m4a

Uploading raw ProRes to a transcription tool is wasteful. The tool discards the video anyway; you are just waiting for a 10 GB file to upload so the tool can extract the 50 MB audio stream it actually needs.

What About QuickTime Screen Recordings?

macOS QuickTime Player's built-in screen recorder (Cmd+Shift+5) saves H.264 video with AAC audio in a MOV container. These files are usually small (screen content compresses well) and universally compatible.

There is one consistent gotcha: QuickTime cannot capture system audio natively on macOS. Without a virtual audio device like BlackHole installed and routed, your screen recording contains only microphone audio. If you recorded a video call demo, the audio you hear during QuickTime playback might be just your own voice, not the other participants. Check this before transcribing, there is nothing to recover if the system audio was never captured.

Screen recording MOVs from QuickTime work fine as direct uploads. File sizes are modest, H.264 is universally supported, and the microphone audio (when present) is high quality.

How to Inspect a MOV Before Uploading

If you are not sure what is inside a MOV file, ffprobe reads the QuickTime atom structure and tells you:

ffprobe -v error -show_streams -select_streams a in.mov

Look for codec_name in the output. aac is AAC, pcm_s16le or pcm_s24le is uncompressed PCM, ac3 is the Dolby Digital codec some older DSLRs used. All three transcribe well. If codec_name shows mp4a, that is AAC with an alternate tag, also fine.

For the video streams, the same command without -select_streams a shows the video codec. hevc means you may want to extract audio first if the target tool has HEVC compatibility issues. prores means you definitely want to.

When to Upload Directly vs. Extract Audio First

Upload directly when: the file is under your tool's upload cap, the video codec is H.264 or H.265 and the tool advertises MOV support, and you want the simplest possible workflow.

Extract audio first when: the file is a ProRes MOV (almost always too large), the tool rejects the file or errors out (likely an HEVC codec issue), the file is over 2 GB, or you need fast turnaround and the video adds nothing.

For converting video to text generally, audio extraction is the reliable path. The transcript does not care whether the video was 4K or 720p.

Specific Situations Worth Knowing

DSLR MOVs with AC3 Audio

Older Canon and Nikon DSLRs recorded MOV files with H.264 video and AC3 (Dolby Digital) audio. AC3 is a broadcast-grade codec that many transcription tools handle, but if you hit compatibility problems, re-encode the audio track:

ffmpeg -i dslr.mov -vn -c:a aac -b:a 192k output.m4a

More importantly: professional DSLR shoots often recorded scratch audio on camera while using a separate audio recorder (a Zoom H5, a Sound Devices field recorder) for the real take. If you have synced separate audio files, transcribe those. The DSLR onboard mic is typically mediocre, and the scratch audio exists only for sync reference in the edit.

Multi-Track Audio in MOV

Professional MOV files sometimes carry multiple audio tracks: a stereo mix on track 0, a split-channel (L=interview subject, R=interviewer) on track 1. Some transcription tools default to the first track without asking.

If the transcript sounds like only one side of a conversation, check the file:

ffprobe -v error -show_streams -select_streams a -of json in.mov

Count the streams entries. If there are two, extract the one you want by specifying the stream index:

ffmpeg -i in.mov -map 0:a:1 -c:a copy track2.m4a

Then transcribe the extracted track. For content with two speakers on split channels, speaker diarization after mixing both channels works better than transcribing one channel alone.

iPhone Portrait MOV

iPhone portrait videos have the same audio quality regardless of orientation. Some older transcription pipelines tripped over vertical video dimensions (checking aspect ratio before processing). Modern tools handle this fine. The audio track is identical whether the phone was held portrait or landscape.

What "Cannot Transcribe This File" Actually Means

Most MOV-specific tool errors fall into three categories:

1. Video codec unsupported (HEVC): Extract audio, upload the M4A instead.
2. File too large: Extract audio, which is usually under 50 MB even for hour-long recordings.
3. No audio track: Open in QuickTime (Window, Show Movie Inspector) and verify an audio track exists. Screen recordings with no microphone selected, or silent B-roll, have nothing to transcribe.

Practical Tips for Better Results

Use a separate mic when you can. iPhone built-in mics are excellent up close but drop off fast beyond 6 feet and pick up room reverb aggressively. A lavalier (via Lightning or USB-C adapter) doubles effective range. The transcription accuracy difference between built-in mic at 10 feet versus lavalier at 6 inches is substantial.

Trim before uploading. iPhone recordings often have 15-30 seconds of dead air while you press record and walk into position. Trim in Photos or QuickTime before uploading; it saves processing time and avoids blank segments at the start of the transcript.

Record in airplane mode for long takes. Notifications and background app refreshes can introduce dropouts in iPhone recordings longer than 30 minutes.

My take: MOV is a well-designed container that holds extremely different content depending on the source. The 30 seconds you spend running ffprobe to see what codec is inside saves the frustration of a failed upload or a corrupted transcript from a tool that silently mishandled an HEVC file. Extract audio for anything ProRes. For everything else, upload directly.

If you just need a clean transcript without fussing over codec details, ConvertAudioToText handles MOV natively and extracts the audio track server-side regardless of video codec.

MOV vs. Sibling Formats for Transcription

FAQ

Is MOV better than MP4 for transcription?

Functionally the same. Both containers carry AAC audio (and MOV often carries PCM for ProRes exports), which ASR engines handle identically. Choose based on convenience, not transcription quality.

Why does my MOV play in QuickTime but fail in other tools?

Almost always the video codec: HEVC (H.265) requires a decoder that not every tool ships with. The audio track is unaffected. Extract audio with ffmpeg and upload that instead: it sidesteps the video-decoder issue entirely.

Can I transcribe MOV files for free?

Yes. ConvertAudioToText accepts MOV on its free tier (10 minutes per month). For longer recordings, the Pro plan is $9.99/month billed yearly with unlimited transcription.

What is the best way to handle a huge ProRes MOV?

Export audio only from Final Cut Pro (File, Share, Master File, choose Audio Only) to get a small M4A. For files already on disk, run: ffmpeg -i in.mov -vn -c:a copy out.m4a. A 30-minute ProRes 422 export at 1080p shrinks from several GB to under 50 MB.

Sources

• Using HEIF or HEVC media on Apple devices - Apple Support
• ConvertAudioToText pricing page
• ProRes 422 codec family - Library of Congress
• QuickTime Video, Apple ProRes 422 - Library of Congress
• iPhone ProRes maximum bitrate - Y.M.Cinema
• ffprobe documentation - FFmpeg.org
• HEVC codec errors on Windows - WinXDVD
• How to record the screen on Mac - Apple Support