How to encode av1 masters for youtube upload
- Step 1Export a high-quality cut from your editor — Start from the best source you have — ideally a high-bitrate H.264/H.265/ProRes export. Garbage in, garbage out: YouTube re-encodes from whatever you give it, so the master's quality is what matters.
- Step 2Drop the export into the AV1 encoder — Single file, read locally via an off-screen
<video>. Confirm your GPU encodes AV1 (RTX 40-series / Arc / Apple M3+) — otherwise the tool refuses with 'Hardware encoding for AV1 is not available on this device.' - Step 3Set a generous bitrate (don't trust auto for a master) — For a YouTube source you want headroom, not minimum size. Pin Bitrate to a high value: ~16000 kbps for 1080p, ~40000+ for 4K (max 50000). Auto's ~0.04 bits/pixel is tuned for delivery, which is too lean for a re-encode source.
- Step 4Match the framerate exactly — Type your project's real fps into Framerate (24/25/30/50/60). Auto is 30, which will wreck a 24 fps cinematic edit or a 60 fps gameplay cut. Wrong fps changes both motion cadence and total duration.
- Step 5Encode the AV1 video stream — Frames decode, re-encode to AV1 on the GPU (keyframe every fps×2), and FFmpeg.wasm muxes the stream. Nothing uploads to JAD during this step.
- Step 6Re-attach audio, then upload to YouTube — The encoder output is video-only — YouTube needs your audio. Mux the AV1 video with your audio (or just upload an audio-bearing master from the transcoder instead). Then upload to YouTube Studio; YouTube ingests AV1 directly.
Suggested AV1 master bitrates for YouTube ingest
Targets for a re-encode SOURCE (deliberately higher than delivery bitrates). YouTube re-encodes anyway, so headroom buys quality. Bitrate field maxes at 50000 kbps.
| Resolution / fps | Suggested AV1 bitrate | Why this high |
|---|---|---|
| 1080p 24/30 | ~12,000–16,000 kbps | Clean source for YouTube's transcoder; far above auto's ~2.5 Mbps delivery target |
| 1080p 60 | ~18,000–24,000 kbps | Double the temporal data; high-motion content needs the headroom |
| 1440p 30/60 | ~24,000–40,000 kbps | More pixels, more source detail to preserve through re-encode |
| 2160p (4K) 30 | ~40,000–50,000 kbps | Near the 50 Mbps cap; gives YouTube's 4K ladder a strong source |
Master vs delivery — when to use which encoder default
The same AV1 tool serves both jobs, but you set bitrate very differently.
| Use | Bitrate setting | Notes |
|---|---|---|
| YouTube master (this page) | Pinned high (12–50 Mbps) | Source for re-encode; quality over size |
| Web delivery file | Auto (0) or low pinned | ~0.04 bits/pixel; smallest at quality — see web-optimizer |
| Storage archive | Moderate pinned | Balance of size and longevity |
| Compatibility-first upload | Use H.265 instead | Wider device decode if you also self-host the file |
Cookbook
Master-grade AV1 encodes aimed at YouTube ingest. All assume audio is re-attached before upload (the AV1 encoder is video-only).
1080p24 cinematic edit → AV1 YouTube master
A 24 fps narrative cut. Set fps to 24 explicitly (auto's 30 would speed it up) and pin a high bitrate so YouTube's re-encode starts clean.
Source : 1920x1080, 24 fps, ProRes export Settings: Bitrate 16000 (16 Mbps), Framerate 24 Result : high-bitrate AV1 video stream (no audio) Next : mux with the project audio, upload to YouTube
4K30 master on an RTX 4090
Push near the 50 Mbps cap for a 4K source. Ada NVENC encodes 4K AV1 in hardware fast.
Source : 3840x2160, 30 fps GPU : RTX 4090 Settings: Bitrate 45000 (45 Mbps), Framerate 30 Result : 4K AV1 master, strong source for YouTube's 2160p ladder
60 fps gameplay → AV1 master
High-framerate gaming content. Set fps to 60 and give it extra bitrate for the motion.
Source : 2560x1440, 60 fps gameplay Settings: Bitrate 24000 (24 Mbps), Framerate 60 Mistake to avoid: leaving Framerate 0 → 30 fps → 2x duration
Don't ship the auto delivery target as a master
Auto bitrate (~0.04 b/px) is tuned for small delivery files. Uploading that as your master gives YouTube a starved source and the re-encode looks worse.
Auto 1080p ≈ 2.5 Mbps ← delivery target, too lean for a master Master : pin 12,000–16,000 kbps instead Rule : the file you upload should be over-provisioned
Need audio in the upload now — use the transcoder
If you don't want a separate mux step, the transcoder re-encodes video and keeps audio in one pass, producing an upload-ready file (though without AV1 hardware specifically).
Want : single upload-ready file with audio This tool: AV1 video-only (then mux audio yourself) Alt : /video-tools/video-transcoder (keeps audio in one pass)
Edge cases and what actually happens
Audio missing from the AV1 master
By designThe hardware AV1 encoder writes a video-only stream — YouTube needs audio, so you must re-mux the AV1 video with your soundtrack before uploading, or produce the master with the transcoder which keeps audio. Uploading the video-only AV1 file directly yields a silent video on YouTube.
Uploaded auto-bitrate file as a master
Starved sourceAuto bitrate targets small delivery files (~0.04 bits/pixel). As a YouTube source it's too lean, so YouTube's re-encode amplifies the compression artifacts. For a master, pin a high bitrate (12–50 Mbps depending on resolution).
Framerate auto on a 24 or 60 fps edit
Cadence brokenAuto resolves to 30 fps. A 24 fps film cut becomes faster and shorter; a 60 fps cut halves in cadence and doubles in duration. Always set Framerate to your project's true fps for a master.
No hardware AV1 encoder
Not availableHardware-only: without an RTX 40-series / Arc / Apple M3+ the tool throws 'Hardware encoding for AV1 is not available on this device.' For a YouTube upload you can equally use H.264/H.265 — YouTube re-encodes regardless. Use the transcoder or H.265 encoder.
Bitrate cap at 50 Mbps for 4K
CappedThe Bitrate field maxes at 50000 kbps (50 Mbps). For a 4K master that's a strong source for YouTube's ladder, but it's a ceiling — you can't push higher here. If you need a higher-bitrate intermediate, export ProRes from your editor with the ProRes encoder.
Container rejected by an uploader/checker
Re-muxThe output downloads as <name>-av1.mp4 but the AV1 stream is happiest in MKV/WebM. YouTube ingests AV1 fine, but a local strict-MP4 validator might object. Re-mux without re-encoding via the web optimizer.
Browser can't load the editor export
Could not loadSome editor exports use containers/codecs the <video> element won't decode. You'll see 'Could not load source video.' Re-export as H.264 MP4 or transcode it with the transcoder first.
10-bit / HDR project
8-bit outputThe encoder uses an 8-bit AV1 Main profile (av01.0.04M.08); HDR/10-bit is not preserved. For an HDR YouTube master, keep the source in its HDR codec rather than round-tripping through this hardware path.
Large 4K master
SupportedOn Pro + Media the output streams to a save-file handle, so a big 4K master writes to disk without filling RAM. Per-file ceiling is 100 GB streaming, single file per encode.
Requires Pro + Media tier
Tier gateHardware AV1 encode is gated to the Pro + Media tier. Free/Pro tiers can't run it. Creators uploading regularly will want that plan.
Frequently asked questions
Does YouTube accept AV1 uploads?
Yes — AV1 is a supported ingest format. YouTube re-encodes every upload into its own VP9/AV1 ladder, so your codec doesn't survive, but a clean AV1 master gives the transcoder good source data.
If YouTube re-encodes anyway, why bother with AV1?
Because the source quality is what survives, not the codec. A high-bitrate AV1 (or H.264/H.265) master re-encodes better than a compression-starved file. AV1 lets you pack more quality per byte into the master if your upload bandwidth is the bottleneck.
What bitrate should a YouTube master be?
Higher than a delivery file. Roughly 12–16 Mbps for 1080p, 18–24 for 1080p60, up to the 50 Mbps cap for 4K. Don't use the auto (~2.5 Mbps for 1080p) target for a master — that's a delivery setting.
Why does my upload have no sound?
Because the AV1 encoder is video-only and you uploaded the silent stream. Re-mux the AV1 video with your audio first, or build the master with the transcoder, which keeps audio.
My 24 fps film looks sped up — why?
You left Framerate on auto, which is 30 fps. Set it to 24 to match the edit. Wrong fps changes both motion cadence and clip duration.
Do I need a special GPU for the AV1 master?
For the AV1 path, yes — RTX 40-series, Intel Arc, or Apple M3/M4. Without AV1 encode silicon the tool refuses (no software fallback). Since YouTube re-encodes anyway, you can also upload an H.264/H.265 master from the transcoder or H.265 encoder.
Is my footage uploaded to JAD?
No. Encoding happens entirely in your browser on your GPU. Only the final master you choose to upload goes to YouTube. JAD never receives your video.
Can I make a 4K AV1 master?
Yes if your GPU encodes 4K AV1 (RTX 40-series, Arc, M3/M4). Pin a high bitrate up to the 50 Mbps cap and set fps to 30 (or your real fps). Output streams to disk on Pro + Media.
Is AV1 better than H.264 for a YouTube master?
For a given upload size, AV1 packs more quality, so a same-size AV1 master is a stronger source. But H.264/H.265 masters also work since YouTube re-encodes everything — the deciding factor is whether your hardware encodes AV1.
What about HDR uploads?
This tool encodes 8-bit AV1 (av01.0.04M.08), so it doesn't preserve HDR/10-bit. For HDR YouTube masters keep the source in its HDR codec instead of round-tripping here.
Can I encode several clips for a series at once?
Not in one batch — AV1 encode is single-file. Encode each clip in turn. The video engine serializes anyway.
What plan do I need?
Pro + Media for the hardware AV1 encode and streaming-to-disk. The per-file video ceiling on that tier is 100 GB streaming.
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.