How to convert h.264 to prores for davinci resolve
- Step 1Open the ProRes encoder — Load the ProRes encoder. It is a Pro-media tier tool (
minTier: pro_media); confirm your plan before transcoding a large H.264 source, since ProRes output is much bigger than the input. - Step 2Drop the H.264 source — Drag in your H.264 MP4 (or HEVC, VP9, MKV, WebM, MOV, AVI, M4V, TS). One file per run. It is read into the browser only — no upload happens.
- Step 3Keep Profile on 422 for the edit — The only setting is Profile. Use
422for cutting in Resolve — it is the default and the right weight for editorial. Step up to422hqfor a colour/finishing master and4444only when you need alpha (see the 4444 + alpha guide). - Step 4Choose the save location — The tool streams output, so the browser prompts for a save target (a
…-prores.movfilename is suggested). On browsers without the File System Access API, the MOV downloads at the end. - Step 5Run the transcode — FFmpeg.wasm decodes the H.264 and re-encodes with
prores_kslocally. This is a full re-encode (not a stream copy), so it takes real CPU time and the file grows substantially — expected when moving to an intra-frame format. - Step 6Import into Resolve as native ProRes — Add the
.movto your Resolve media pool — it appears as ProRes 422 and scrubs natively. You no longer need Resolve's Optimized Media for that clip. If you want to merge several same-codec clips first, use the video merger before transcoding.
H.264 source vs ProRes 422 output
What changes when you transcode. The encoder always re-encodes (no stream copy) because H.264 and ProRes are different codecs.
| Property | H.264 source (typical) | ProRes 422 output |
|---|---|---|
| Frame structure | Long-GOP (I/P/B frames) | Intra-frame (every frame a key frame) |
| Resolve scrub | Stutters / decode lag | Instant |
| Codec | H.264 (libx264-class) | ProRes 422 (prores_ks, profile 2) |
| Pixel format | 8-bit yuv420p (usual) | 10-bit yuv422p10le |
| Audio | AAC | Uncompressed pcm_s16le |
| Container | MP4 | QuickTime .mov |
| File size | Baseline | ~5–20× larger |
Profile picker values for Resolve
The three exposed profiles and their internal mapping. There is no Proxy/LT option; 422 is the lightest.
| Picker value | `-profile:v` | Pixel format | Use in Resolve |
|---|---|---|---|
422 (default) | 2 | yuv422p10le | Editorial timeline, the everyday choice |
422hq | 3 | yuv422p10le | Grade/finishing master, 4K |
4444 | 4 | yuva444p10le | Alpha for Fusion/VFX comps |
Tier limits for the transcode
ProRes encoding needs Pro-media minimum. Caps are file size and batch count; output streams so there is no duration limit.
| Tier | Max file size | Files / batch | ProRes access |
|---|---|---|---|
| Free | 1 GB | 1 | No |
| Pro | 10 GB | 5 | No |
| Pro-media | 100 GB | 50 | Yes |
| Developer | 100 GB | Unlimited | Yes |
Cookbook
Real H.264→ProRes transcodes for the Resolve colourist/editor. The commands are the FFmpeg.wasm equivalents the Profile picker drives — you do not type them.
Mirrorless H.264 clip that lagged in Resolve
A long-GOP H.264 clip from a mirrorless camera scrubbed poorly in Resolve. Transcoding to ProRes 422 makes the timeline immediate.
Input: C0021.MP4 (H.264, 4K, 25fps, 8-bit yuv420p)
Profile: 422
In-browser equivalent:
prores_ks -profile:v 2 -pix_fmt yuv422p10le \
-vendor apl0 -c:a pcm_s16le
Output: C0021-prores.mov (ProRes 422, instant scrub in Resolve)HEVC clip the free Resolve refused to decode cleanly
Resolve's free edition can struggle with some HEVC variants depending on the OS decoder. Transcoding to ProRes gives Resolve a format it reads everywhere.
Input: drone.mov (HEVC, 10-bit) Profile: 422 Output: drone-prores.mov (ProRes 422) → media pool reads it natively; no Optimized Media pass needed.
Replace Resolve's slow Optimized Media for one clip
Instead of waiting for Resolve to generate Optimized Media, transcode the single problem clip to ProRes in a browser tab while you keep working in Resolve.
Resolve workflow before: right-click clip → Generate Optimized Media (slow) This tool: drop clip → Profile 422 → save ProRes MOV → relink the timeline clip to the ProRes file; scrub is instant.
Merge same-codec clips, then transcode once
If you have several same-codec H.264 segments, concatenate them losslessly first, then do a single ProRes encode of the whole reel.
Step 1 — video-merger (concat demuxer, stream copy): reel-a.mp4 + reel-b.mp4 + reel-c.mp4 → reel.mp4 Step 2 — prores-encoder, Profile 422: reel.mp4 → reel-prores.mov One ProRes encode instead of three.
422 for editing, 422 HQ for the grade
Cut on ProRes 422 for speed; if you hand the project to a colourist, re-export the conform on 422 HQ for extra bitrate headroom.
Edit pass: Profile 422 (-profile:v 2) Finishing: Profile 422hq (-profile:v 3) Same yuv422p10le pixel format; HQ is a higher-bitrate variant.
Edge cases and what actually happens
This is a re-encode, not a fast stream copy
By designH.264 and ProRes are different codecs, so the source must be fully decoded and re-encoded — there is no -c copy shortcut. That is why it takes CPU time and produces a much larger file. If you only need to cut without changing codec, the lossless trimmer stream-copies instead.
ProRes output dwarfs the H.264 input
ExpectedIntra-frame ProRes is typically 5–20× the size of long-GOP H.264 at the same resolution. That is normal and is the reason Resolve scrubs it instantly. Pro-media's 100 GB cap leaves plenty of headroom; trim first if a clip is enormous.
Resolve free edition couldn't decode the source H.264/HEVC
MitigatedResolve's free build relies on OS hardware decoders for some H.264/HEVC variants and can choke. Transcoding to ProRes here is exactly the fix — the browser decodes the source via FFmpeg.wasm, and you hand Resolve an intra-frame ProRes file it reads consistently across platforms.
Not available on Free or basic Pro
403 tier-gatedProRes encoding requires the Pro-media tier (minTier: pro_media). On lower tiers the tool is locked. Pro-media also raises the video limit to 100 GB per file and 50 files per batch, which suits ProRes-sized output.
Variable frame rate source
HandledVFR H.264 (common from screen recorders and phones) is decoded and re-encoded into a ProRes MOV; Resolve generally prefers constant-frame-rate media, and an intra-frame ProRes pass gives it cleaner timing than the raw VFR file. Check the clip's reported frame rate in Resolve after import.
Source over the tier file-size cap
413 too largeA source above your tier's video limit (Pro-media/Developer 100 GB) is rejected before transcoding. Split a very long source with the video splitter or trim it down first, then transcode the pieces.
Audio drifts after transcode
Check sourceIf audio appears out of sync in Resolve, the usual cause is the source being VFR or having a non-standard audio timestamp, not the ProRes encode. Audio is carried as pcm_s16le; if drift persists, re-examine the original or extract audio separately with the audio track extractor.
Wanted Proxy media, picked 422
PreservedThe picker has no ProRes Proxy or LT setting — 422 is the lightest available. For lighter offline media in Resolve, transcode to 422 here and let Resolve generate its own proxy resolution media pool entries if you need even smaller files.
Image sequence or audio-only file dropped in
Invalid inputThe encoder needs a single video container, not an image sequence or an audio file. A file with no video stream fails. Feed a video; to grab still frames instead, use the frame grid maker.
Frequently asked questions
Why transcode H.264 to ProRes for Resolve at all?
Long-GOP H.264 forces Resolve to decode a group of frames to show one, so scrubbing and frame-stepping lag. ProRes 422 is intra-frame — every frame is a key frame — so the playhead and trims are instant. ProRes also decodes more reliably across platforms than some H.264/HEVC variants, especially on the free Resolve edition.
Will Resolve recognise the output as ProRes?
Yes. The file is true Apple ProRes 422: prores_ks with -profile:v 2, 10-bit yuv422p10le, vendor tag apl0, in a QuickTime .mov. Resolve's media pool tags it as ProRes 422 and treats it as native media.
Is this faster than Resolve's Optimized Media?
For a single clip it is usually quicker and more convenient, and it runs in a separate browser tab so Resolve stays free. Both are full re-encodes; the advantage here is no Mac requirement, no upload, and a portable ProRes file you can reuse on any system.
Does anything get uploaded?
No. FFmpeg.wasm decodes and encodes entirely in your browser. The H.264 source and the ProRes output never touch a server, which matters for client and embargoed footage.
Can it stream-copy instead of re-encoding?
No — H.264 and ProRes are different codecs, so a re-encode is mandatory. If your goal is to cut or join without changing codec, use the lossless trimmer or video merger instead, which stream-copy where possible.
Which profile is right for a Resolve edit?
Keep it on 422 (default) for cutting. Use 422hq for a finishing/grade master and 4444 only when you need an alpha channel for Fusion or VFX. Those three are the only options.
How much bigger will the file get?
Plan for roughly 5–20× the H.264 size. ProRes stores each frame independently, which is what makes Resolve scrub it instantly. Trim or split the source first if storage is tight.
What input codecs does it accept?
Any video the browser can decode in a recognised container — MP4, MOV, MKV, WebM, AVI, M4V, TS. H.264, HEVC, VP9, and similar all decode and re-encode to ProRes.
Why is the encode using a lot of CPU?
It is a full intra-frame re-encode running in WebAssembly on your processor. There is no upload or cloud queue, but the compute is local, so a long 4K source works the CPU hard for a while. Keep the tab focused.
Can I change resolution or bitrate during the transcode?
No. The Profile picker is the only control. To resize first use the video resizer; for arbitrary codec/bitrate output use the video transcoder.
Can I transcode a whole folder at once?
ProRes encoding is one file per run here. Pro-media allows up to 50 files per batch across the video tools, but queue ProRes encodes individually for predictable output.
What tier do I need?
Pro-media or higher (minTier: pro_media). Free and basic Pro cannot run the ProRes encoder. Pro-media also unlocks the 100 GB per-file video limit you will likely need for ProRes output.
Privacy first
Every JAD Video tool runs entirely in your browser via WebCodecs and FFmpeg (WebAssembly). Your video files never leave your device — verified by zero outbound network requests during processing.