How to generate a prores 422 hq master deliverable
- Step 1Open the ProRes encoder — Load the ProRes encoder. It is a Pro-media tool (
minTier: pro_media) — appropriate since 422 HQ masters are large. Confirm your plan covers it before encoding a long deliverable. - Step 2Drop your finished cut — Drag in the locked, graded export you are delivering — MP4, MOV, MKV, WebM, AVI, M4V, or TS. One file per run. It stays in the browser; nothing uploads.
- Step 3Select the 422hq profile — Change Profile from the default
422to422hq. This is the single setting that makes it a broadcast master —422hqmaps to-profile:v 3. Do not leave it on422if the spec calls for HQ. - Step 4Choose the delivery save location — Because the tool streams, the browser asks where to save (a
…-prores.movname is suggested). Name it to match the delivery spec. Browsers without the File System Access API download the MOV at the end. - Step 5Encode the master — FFmpeg.wasm runs
prores_ksat the HQ profile locally. HQ allocates more bitrate than 422, so the file is larger and the encode takes longer — expected for a master deliverable. - Step 6QC and deliver — Verify the file reports as ProRes 422 HQ in your NLE or a QC tool before sending. If the deliverable also needs metadata stripped or a faststart pass for online review, see the metadata scrubber and web optimizer.
ProRes 422 HQ master — exact encode parameters
What this tool emits when you select 422hq. Verified against the encoder implementation; the only thing you choose is the profile.
| Parameter | Value for 422 HQ | Notes |
|---|---|---|
| Encoder | prores_ks | FFmpeg ProRes encoder via WebAssembly |
-profile:v | 3 | ProRes 422 HQ profile (the 422hq picker value) |
-pix_fmt | yuv422p10le | 10-bit 4:2:2 — same sampling as 422, HQ adds bitrate not chroma |
-vendor | apl0 | Apple vendor tag for genuine-ProRes recognition |
-c:a | pcm_s16le | Uncompressed 16-bit PCM audio for the master |
| Container | .mov (video/quicktime) | Standard deliverable wrapper |
422 HQ vs the other profiles
422 HQ is the middle profile. Note it shares the pixel format with 422 — the difference is bitrate, not chroma sampling.
| Profile value | `-profile:v` | Pixel format | Typical role |
|---|---|---|---|
422 | 2 | yuv422p10le | Everyday editorial |
422hq (this page) | 3 | yuv422p10le | Broadcast/client master, 4K, finishing |
4444 | 4 | yuva444p10le | Alpha/VFX delivery |
Tier limits for HQ masters
ProRes encoding requires Pro-media. HQ masters are large, so the file-size cap is what matters most.
| 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 master-delivery encodes. The commands are the FFmpeg.wasm equivalents the 422hq picker drives — you only select the profile.
Graded 4K cut to a 422 HQ broadcast master
A finished, graded 4K export needs to go out as the broadcast master. Select 422hq and you hit the spec exactly.
Input: film-final-graded.mov (H.265, 4K, 10-bit)
Profile: 422hq
In-browser equivalent:
prores_ks -profile:v 3 -pix_fmt yuv422p10le \
-vendor apl0 -c:a pcm_s16le
Output: film-final-graded-prores.mov (ProRes 422 HQ)
→ QC reads it as ProRes 422 HQ; ready to deliver.Don't ship 422 when the spec says HQ
The most common delivery reject is the wrong profile. Confirm the picker is on 422hq before encoding — plain 422 is profile 2, HQ is profile 3.
Spec: ProRes 422 HQ WRONG: Profile 422 → -profile:v 2 (rejected by QC) RIGHT: Profile 422hq → -profile:v 3 (accepted) There is no auto-detect — you must select 422hq.
Strip metadata before sending the master
Some clients require a clean master with no camera/edit metadata. Scrub first, then encode the HQ deliverable.
Step 1 — metadata-scrubber: cut.mov → cut-clean.mov (camera/GPS/edit tags removed) Step 2 — prores-encoder, Profile 422hq: cut-clean.mov → cut-clean-prores.mov (ProRes 422 HQ)
1080p network deliverable
Even for HD, broadcasters often require 422 HQ rather than standard 422 for the master bitrate headroom.
Input: episode-07.mp4 (H.264, 1080p) Profile: 422hq Output: episode-07-prores.mov (ProRes 422 HQ, 1080p) Audio: pcm_s16le, container .mov
Web-review copy after the master
Deliver the heavy HQ master, then make a light faststart copy for online review without re-grading.
Master: Profile 422hq → episode-07-prores.mov (deliver)
Review: web-optimizer on a separate H.264 export
→ faststart MP4 for streaming review
Keep the ProRes HQ as the archival/deliverable master.Edge cases and what actually happens
422 HQ and 422 use the same pixel format
By designBoth write 10-bit yuv422p10le; the difference between profile 2 and profile 3 is the target bitrate, not the chroma sampling. So HQ does not give you 4:4:4 colour — for full chroma plus alpha you need the 4444 profile. Choose HQ for bitrate headroom on a 4:2:2 master.
Wrong profile delivered (422 instead of HQ)
Reject riskIf the picker is left on the default 422 the file is profile 2, which a strict QC house will reject when the spec demands 422 HQ. There is no automatic spec detection — you must select 422hq. Verify the reported profile in your NLE before sending.
HQ master is very large
Expected422 HQ allocates a higher bitrate than 422, so masters are bigger again than standard ProRes — and far bigger than the source. That is the nature of a broadcast master. Pro-media's 100 GB cap covers feature-length 4K HQ; trim with the lossless trimmer if you only need a section.
Not available on Free or basic Pro
403 tier-gatedEncoding ProRes requires the Pro-media tier (minTier: pro_media). Master delivery work realistically lives on Pro-media or Developer anyway, which also grant the 100 GB file limit HQ masters need.
Source already low quality (heavily compressed)
No quality recoveryEncoding to 422 HQ wraps the source in a high-bitrate master container but cannot restore detail already lost to compression — garbage in, large garbage out. Always master from the highest-quality graded export available, not a re-compressed copy.
File over the tier size limit
413 too largeA source above your tier's video cap (Pro-media/Developer 100 GB) is rejected before encoding. For an extremely long programme, deliver in reels: split with the video splitter, encode each reel to 422 HQ, and deliver as parts.
Client wants a different audio spec
Fixed to PCMThe master carries uncompressed pcm_s16le audio — standard for broadcast. The audio format is not configurable here. If the deliverable spec calls for a separate audio layout or stem, extract and prepare audio with the audio track extractor before or after encoding.
Need alpha in the master
Use 4444422 HQ has no alpha channel — its pixel format is yuv422p10le. If the deliverable must carry transparency, pick 4444 instead (yuva444p10le). See the 4444 + alpha guide.
Image-only or audio-only file dropped in
Invalid inputThe encoder needs a video container with a video stream. A still or an audio file fails. Provide the graded video export you intend to master.
Frequently asked questions
How do I make sure I'm delivering 422 HQ and not plain 422?
Set the Profile picker to 422hq before encoding — that maps to -profile:v 3, the HQ profile. The default is 422 (profile 2), so you must change it deliberately. After encoding, confirm your NLE or QC tool reports the file as ProRes 422 HQ.
Is this a genuine broadcast-grade ProRes 422 HQ file?
Yes. It is prores_ks at -profile:v 3 with 10-bit yuv422p10le, the Apple vendor tag apl0, uncompressed pcm_s16le audio, in a QuickTime .mov. That is the standard 422 HQ master shape that finishing houses and networks accept.
What's the difference between 422 and 422 HQ here?
Both use the same 10-bit 4:2:2 pixel format (yuv422p10le); HQ (profile 3) targets a higher bitrate than standard 422 (profile 2). HQ is the master/finishing choice for colour-critical and 4K work; plain 422 is for everyday editing.
Does the master upload to a server?
No. The encode runs in FFmpeg.wasm in your browser. The deliverable never leaves your machine, which is important for embargoed releases and NDA client work.
Can I get a higher-precision master than 422 HQ?
For full 4:4:4 chroma and an alpha channel, use the 4444 profile (yuva444p10le, profile 4). 422 HQ stays at 4:2:2 — it raises bitrate, not chroma sampling. Pick 4444 only if the spec genuinely needs it.
Why is the HQ file so large?
422 HQ uses a higher bitrate than 422, and ProRes is intra-frame, so masters are large by design — often many gigabytes for a feature-length 4K cut. That is expected; trim or split if you need to manage size.
What audio does the master carry?
Uncompressed pcm_s16le (16-bit PCM) inside the MOV — the broadcast-standard choice. It is not configurable in this tool; handle separate audio layouts with the audio track extractor if your spec requires it.
Can I strip metadata from the deliverable?
Not within this tool. Run the export through the metadata scrubber first to remove camera, GPS, and edit metadata, then encode the clean file to 422 HQ here.
Do I need a Mac to make a 422 HQ master?
No. The encode runs in the browser via WebAssembly, so you can deliver an Apple ProRes 422 HQ master from Windows, Linux, or a Chromebook. See the no-Mac ProRes guide.
Will encoding to HQ improve a low-quality source?
No. A higher-bitrate ProRes wrapper cannot restore detail the source already lost to compression. Always master from the best available graded export, not a re-compressed copy.
How long can the master be?
There is no duration cap — output streams to disk. The limit is file size (Pro-media 100 GB) and batch count. For very long programmes, split into reels and deliver as parts.
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 limit that HQ masters typically need.
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.