ProRes 422 vs 422 HQ vs 4444: Which ProRes Should You Export?

Export ProRes 422 for everyday editing and renders, ProRes 422 HQ for masters and footage that will be graded or re-encoded many times, and ProRes 4444 only when you need an alpha channel or your source really is 4:4:4, such as RGB graphics and composites. 4444 does not make 4:2:2 camera footage look better; it makes the file bigger.

Below is the reasoning, for jobs that do not fit neatly, and the storage numbers. Every codec fact here comes from Apple's ProRes white paper (April 2022 edition, the current one as of November 2026). For the whole family, including Proxy, LT and 4444 XQ, start with what Apple ProRes is.

What actually separates the three

Three things fall out of that table.

422 and 422 HQ differ in headroom, not in what you see on first viewing. Apple describes ProRes 422 as offering nearly all the benefits of 422 HQ at 66 percent of the data rate. In the white paper's own test, the original, the 422 HQ encode and the 422 encode all look visually identical. The difference is what happens when you decode and re-encode the same footage again and again: the white paper's multigeneration chart shows 422 HQ holding a higher quality measure (PSNR) across nine generations than 422. That headroom is why HQ is the usual choice for a master, and why 422 is fine for material that will be rendered once or twice and then delivered.

422 HQ and 4444 have the same headroom. This is the point most comparisons miss. Apple's qualitative rating for 4444 (without alpha) is identical to 422 HQ, and the white paper says why: 4444's target rate is 50 percent higher, and those extra bits go to encoding the extra chroma samples of a 4:4:4 source at the same quality headroom 422 HQ gives a 4:2:2 source. So 4444 is not "a better 422 HQ". It is the same quality level for a different kind of source.

Only 4444 (and 4444 XQ) carries alpha. Apple calls them "the only ProRes codecs that support alpha channels." The alpha is stored mathematically lossless at up to 16 bits, and because it mostly describes edges, Apple says it typically adds only a small amount to the data rate. If the file has to keep transparency, the decision is already made.

Which ProRes for which job

Two judgment calls the table cannot make for you. If you are unsure whether a clip will be graded hard, HQ costs about half again as much storage as 422 and removes the question. And if a single shot in a 4:2:2 edit needs alpha (a title, a cut-out), export just that shot as 4444; the rest of the timeline stays 422 or HQ.

The cost: storage and playback

Apple's target rates turn into storage with one division and one multiplication: megabits per second divided by 8 gives megabytes per second, then multiply by the running time.

A 10-minute UHD (3840x2160) timeline at 24p, from the white paper's appendix:

• 422: 471 / 8 = 58.9 MB/s, x 600 seconds = about 35 GB
• 422 HQ: 707 / 8 = 88.4 MB/s, x 600 = about 53 GB
• 4444 (no alpha): 1,061 / 8 = 132.6 MB/s, x 600 = about 80 GB

At 1920x1080 and 24p the same table lists 53, 79 and 119 GB per hour for 422, 422 HQ and 4444. These are targets: ProRes is variable bit rate, simple frames come in under, and Apple says no frame goes more than about 10 percent over the target.

Playback cost rises too. In Apple's own test (December 2021, a 16-inch MacBook Pro with M1 Max, Final Cut Pro 10.6.1, 4096x2160 at 23.98 fps) the machine played 31 simultaneous streams of 422, 30 of 422 HQ and 22 of 4444. Your machine will differ; the shape of the drop is the useful part.

Exporting each one with ffmpeg

Your editing app lists these flavors by name in its export settings; the alpha export guide walks through Final Cut Pro, Premiere Pro, After Effects and Resolve. For batch conversions outside an editor, ffmpeg's prores_ks encoder picks the flavor with -profile:v: 0 Proxy, 1 LT, 2 422, 3 422 HQ, 4 4444, 5 4444 XQ.

ProRes 422, with 16-bit PCM audio:

ffmpeg -i clip.mp4 -c:v prores_ks -profile:v 2 -vendor apl0 -pix_fmt yuv422p10le -c:a pcm_s16le clip_422.mov

ProRes 422 HQ, the same with one number changed:

ffmpeg -i clip.mp4 -c:v prores_ks -profile:v 3 -vendor apl0 -pix_fmt yuv422p10le -c:a pcm_s16le clip_422hq.mov

ProRes 4444 keeping an alpha channel from a source that has one:

ffmpeg -i source_with_alpha.mov -c:v prores_ks -profile:v 4 -vendor apl0 -pix_fmt yuva444p10le -alpha_bits 16 graphic_4444.mov

Check what you made before it goes anywhere:

ffprobe -v error -select_streams v:0 -show_entries stream=codec_tag_string,profile,pix_fmt -of compact=p=0 clip_422hq.mov

We ran all of these on 3-second 1080p24 test clips. ffprobe reported apcn (profile Standard) for 422, apch (profile HQ) for 422 HQ, both yuv422p10le with PCM audio, and ap4h (profile 4444) for the graphic. On the 4444 file ffprobe showed yuva444p12le: the decoder reports 12-bit, and the a is the alpha plane.

One caveat from Apple's white paper: it names FFmpeg among unauthorized implementations that "may lead to decoding errors, performance degradation, incompatibility, and instability." When a delivery spec asks for an authorized encoder, export the deliverable from an app on Apple's licensed products list.

AI-generated clips: which flavor

Video models deliver H.264 MP4s. A higher ProRes flavor cannot add detail the source never had, so the choice is about how the clips will be worked, not about rescuing quality. To cut them into a ProRes timeline, 422 is usually enough; if they will be graded as hard as camera footage, match the timeline's 422 HQ so every clip has the same headroom from there on. Either way it is a transcode.

In Treza, an AI video pipeline can follow its generation with an FFmpeg step that runs the 422 or 422 HQ command above on every clip it makes, so the editor receives MOV files instead of MP4s. The step runs from chat or inside a pipeline, and each output is capped at 4 GB.

The one case where 4444 is the right answer for a generated clip is transparency. Treza's video background remover cuts the subject out of every frame and can return ProRes 4444 with a real alpha channel, with green spill taken off the edges of footage shot on green. Ask the AI video generator in chat for a character or product "with a transparent background" and it renders the subject on a flat green screen and cuts it to a transparent ProRes 4444 MOV as soon as it lands. Sound is not carried through the cut-out, so add audio in the edit.

Frequently Asked Questions

What is the difference between ProRes 422 and ProRes 422 HQ?

Both are 10-bit 4:2:2. 422 HQ has a higher data rate (about 220 Mb/s against 147 Mb/s at 1080p29.97) and more quality headroom, so it holds up better over many generations of re-encoding. On a first viewing Apple rates visible differences as very rare for 422 and virtually never for HQ.

ProRes 4444 vs 422 HQ: is 4444 better quality?

Not for 4:2:2 footage. Apple gives 4444 the same quality rating as 422 HQ; its extra data rate goes to full 4:4:4 chroma and optional alpha. Use 4444 for 4:4:4 sources such as graphics and renders, or when you need transparency.

Which ProRes should I use for editing?

ProRes 422 for most editing and render files, 422 LT when storage is tight, and 422 Proxy for offline editing you will relink later. Move to 422 HQ for footage that will be graded heavily.

Which ProRes should I export my master in?

422 HQ for a master cut from 4:2:2 footage, 4444 if the master must keep alpha or the project is 4:4:4 throughout. If a client or broadcaster gives you a delivery spec, it decides.

Is ProRes 422 good enough for YouTube?

You do not need ProRes for the upload itself. Export a ProRes master if you want one, then make an H.264 or HEVC file from it for the platform.

Does ProRes 4444 always have an alpha channel?

No. Alpha is optional in 4444. The file only carries transparency if the source had it and the export was set to keep it; check with ffprobe for a pixel format with an a, such as yuva444p12le.