ProRes to MP4
ProRes 422, 422 HQ, 4444, 4444 XQ, LT, Proxy — all to H.264 MP4 in your browser. The master file stays on your disk. The MP4 lives only in your tab until you download it.
drop a ProRes file here
or click to choose — .mov, .mxf with ProRes inside
ProRes flavors, briefly
- Proxy — lowest bitrate, ~36 Mbps at 1080p. For rough cut.
- LT — ~102 Mbps. Light editing.
- 422 — ~147 Mbps. Standard editing master.
- 422 HQ — ~220 Mbps. Broadcast and color-graded delivery.
- 4444 — ~330 Mbps. Alpha channel + higher chroma fidelity.
- 4444 XQ — ~500 Mbps. Highest, for VFX masters.
All of them transcode to the same H.264 MP4 output here. The difference is purely the size and speed of the input read.
Why people transcode ProRes → MP4
- Upload — YouTube accepts ProRes but takes hours to process. H.264 MP4 uploads in minutes.
- Client review — ProRes files are too large to email or share via consumer chat. MP4 fits.
- Final delivery — brand and editorial clients almost always specify H.264 MP4 for the final.
- Archive proxies — keep the ProRes master, distribute a small MP4 reference copy.
Why convert in the browser instead of using Compressor or Handbrake?
Three reasons:
- No install. Useful on locked-down work laptops where you can't run new apps. Open a browser, drop a file.
- No upload. ProRes files often contain unfinished client work, NDA footage, or color-graded looks that aren't ready for public eyes. Browser-based conversion means the master never leaves your machine.
- Cross-platform. The same workflow on Mac, Windows, Linux, Chromebook. No platform-specific tooling.
The trade-off is speed. FFmpeg-WASM is roughly 10–20× slower than native FFmpeg. A 5-minute ProRes master might take 5–10 minutes to transcode in browser. For final delivery, that's usually fine. For batch work, use Compressor or native FFmpeg.
Large file handling
WebAssembly caps memory at ~2 GB. A typical 5-minute ProRes 422 HQ file fits. A 20-minute master will not. For multi-gigabyte ProRes, either split the file with our trim tool in pieces, or use native FFmpeg on the desktop.
FAQ
Does this work with ProRes 4444 alpha channel?
The alpha channel is dropped — H.264 MP4 doesn't support alpha. For alpha-preserving conversions, output to WebM with our convert tool (VP9 supports alpha).
What about ProRes RAW?
ProRes RAW is the camera raw flavor. It uses different decoding and isn't fully supported by FFmpeg yet. Convert to ProRes 422 first in Final Cut, then bring it here.
Will my LUT / color grade be preserved?
The H.264 output captures whatever was baked into the ProRes pixels. If the LUT was applied destructively in the export, it's in the output. If it was an adjustment layer in Resolve / Premiere, it was already baked at ProRes export.
I get "out of memory" errors. What can I do?
Split the file with trim into pieces under 2 GB, convert each, then merge the MP4s.
Does this work with MXF wrappers around ProRes?
Yes — the tool detects the ProRes stream inside MXF too.
Does the file get uploaded anywhere?
No. The page runs FFmpeg via WebAssembly. Disconnect after loading to verify.