Convert ProRes to H.264 on Windows (Without Final Cut Pro)

A lot of footage starts its life on a Mac. Someone shoots on a camera that records ProRes, or an editor cuts the first pass in Final Cut Pro and exports a ProRes master. Then the file lands on a Windows machine for finishing, review, or delivery. The colorist is on a PC. The client only opens things in Windows Media Player. The delivery spec asks for an MP4. Suddenly you are holding a codec that Windows was never really built to handle.

This is the cross-platform editorial reality, and Expi exists partly because of it. Here is what is actually going on and how to get a clean, playable file out the other side.

What ProRes is, and why it is so heavy

Apple ProRes is an intermediate codec. It is designed for editing, not delivery. That distinction matters.

ProRes keeps quality high and stays easy to scrub, cut, and color grade. It is visually near-lossless, and it decodes cheaply, so your editor stays responsive even on long timelines. The tradeoff is size. A few minutes of ProRes 422 HQ can run into gigabytes. ProRes 4444 is heavier still.

That is a good deal on an editing workstation with fast local storage. It is a bad deal for anything you actually hand off:

• Storage: ProRes masters eat disk fast, especially at 4K.
• Playback: Most consumer players struggle or refuse to open it.
• Sharing: Uploading or emailing a multi-gigabyte file is a non-starter.

ProRes is the right format to edit in and archive from. It is the wrong format to send to anyone.

Why Windows and ProRes do not get along

On a Mac, ProRes support is built into the operating system. On Windows, it historically has not been. That gap is the whole problem.

If you try to play an Apple ProRes file on Windows, you often get one of a few outcomes: audio with no video, a black frame, stuttering playback, or a player that simply will not open the file. ProRes playback on Windows has never been a given.

The usual workaround is to install extra codec support. Depending on your Windows version and player, that might mean a codec pack, a paid decoder, or a specific media framework component. Codec packs are a well-known source of trouble. They can conflict with each other, break other playback, or quietly stop working after an update. For ProRes editing on Windows, some NLEs bundle their own decoder, but that does not help the client, the reviewer, or anyone who just wants to double-click and watch.

The point is simple. Getting reliable ProRes playback on Windows through codec installs is fragile, and it does nothing to shrink the file.

The fix: convert for delivery, keep the master

The clean solution is to stop trying to make ProRes behave like a delivery format. Convert it.

• For delivery and playback, encode to H.264. It plays everywhere: browsers, phones, Windows out of the box, every consumer player. File sizes drop dramatically.
• For newer targets or 4K/HDR, consider H.265 (HEVC). Better compression at the same quality, at the cost of slightly less universal support.
• Keep the ProRes file as your archive master. Convert copies for delivery. Never throw away the high-quality source.

This is the standard editorial pattern. Edit and archive in ProRes, deliver in H.264 or H.265. You are not choosing one format over the other. You are using each for what it is good at.

Quality tradeoffs and sensible settings

H.264 is lossy, so the question is how much compression you can accept before it shows. For a good FFmpeg-based encoder, the main lever is CRF (Constant Rate Factor). Lower CRF means higher quality and a bigger file.

• CRF 18: Visually very close to the source. Good for high-value delivery where size is not tight.
• CRF 20 to 23: The practical sweet spot for most delivery. 23 is the common default.
• CRF 26 and up: Noticeably smaller, with visible compression on detailed footage.

For most work, a ProRes to MP4 conversion on Windows at CRF 20 to 23 gives you a file that looks clean and shares easily. If you were doing this by hand, the FFmpeg call underneath looks roughly like this:

ffmpeg -i master.mov -c:v libx264 -crf 20 -preset slow -c:a aac -b:a 192k delivery.mp4

Expi runs this kind of pipeline for you, with the settings exposed as plain controls instead of flags.

How Expi handles ProRes on Windows

Expi is a native Windows and macOS app built on FFmpeg, and it ships with full FFmpeg ProRes decoder support. On Windows, that means you do not install a codec pack, hunt down a decoder, or hope your media framework cooperates. You open the ProRes file in the app and it reads it directly.

Because everything runs locally, your footage never leaves your machine. There is no upload, no cloud queue, and no file-size limit. For gigabyte-scale ProRes masters, that alone saves real time. You are not waiting on a browser to push 8 GB to a server before anything happens.

Expi is a native app, not an Electron or Java wrapper, so it starts fast and stays out of your way. It also does batch conversion, which matters when you have a folder of ProRes clips rather than a single hero shot.

Hardware acceleration on the output side

Decoding ProRes is cheap. Encoding H.264 or H.265 is where the time goes, and that is where your GPU earns its keep.

On Windows, Expi can encode using hardware acceleration:

• NVIDIA NVENC on GeForce and RTX cards.
• AMD AMF on Radeon GPUs.
• Intel Quick Sync on supported Intel chips.

Hardware encoding is dramatically faster than software x264, especially on long timelines and 4K. The tradeoff is that a well-tuned software encode at a given CRF can still edge out hardware for pure compression efficiency. For everyday delivery, the speed is usually worth it. For a final master where every bit counts, a software encode is defensible. Both paths are available.

The edge case: HDR ProRes to SDR H.264

If your ProRes master is HDR (for example, an HLG or PQ grade), converting straight to a standard SDR H.264 file without handling the color can wreck it. You get washed-out, gray, or oddly desaturated footage, because the wide-range HDR values are being crammed into an SDR container with no translation.

The fix is tone mapping: deliberately mapping the HDR range down into SDR so the image still looks right. If your delivery target is a normal SDR MP4 and your source is HDR ProRes, make sure the conversion tone-maps rather than just relabeling the file. This is easy to overlook and expensive to catch late.

How to do it

1. Copy your ProRes master to the Windows machine, or point the app at it on shared storage.

2. Open Expi and add the ProRes file (or a whole folder, for batch).

3. Choose H.264 for maximum compatibility, or H.265 for better compression on modern targets.

4. Set CRF around 20 to 23, or pick a quality preset.

5. Enable hardware acceleration (NVENC, AMF, or Quick Sync) if you want speed, or leave it on software for maximum efficiency.

6. If the source is HDR and the target is SDR, confirm tone mapping is applied.

7. Run the conversion and keep the original ProRes file as your archive.

Convert once, deliver the H.264, and file the ProRes master away for the next time someone needs the high-quality source.