How to increase video bitrate to improve visual quality
- Step 1Drop the video you're re-encoding — Add your source (
.mp4,.mov,.mkv,.webm,.avi,.m4v,.ts). It loads into FFmpeg.wasm in your browser — nothing uploads. - Step 2Set a generous Video kbps target — Type a higher value than the source's current bitrate ceiling so libx264 isn't forced to discard detail. The field allows up to 50000. See the resolution table for starting points.
- Step 3Raise Audio kbps if audio matters — For music or rich soundtracks, set Audio kbps to 256 or 320 (max 320). For speech, 128 is plenty. Audio is re-encoded to AAC at this value.
- Step 4Encode (single pass) — The tool runs
libx264 -preset medium -b:v Xk -maxrate (1.2X)k -bufsize (2X)k -c:a aac -b:a Yk -movflags +faststart. - Step 5Download the faststart MP4 — Larger file, fewer compression artefacts introduced by this pass. Compare side-by-side with the source to confirm the improvement is worth the size.
- Step 6Re-encode from the best available source — For real quality gains, always start from the highest-quality copy you have — re-encoding a re-encode compounds loss no matter how high you set the bitrate.
Quality-preserving Video kbps starting points
Targets aimed at preserving quality through a re-encode (higher than lean-delivery numbers). These cannot exceed the quality of the source; they just avoid adding new damage.
| Resolution | Good | High | Near-transparent |
|---|---|---|---|
| 480p | 1500 | 2500 | 4000 |
| 720p | 4000 | 6000 | 9000 |
| 1080p | 8000 | 12000 | 18000 |
| 1440p | 14000 | 20000 | 30000 |
| 4K | 30000 | 40000 | 50000 (cap) |
What raising bitrate can and cannot fix
Bitrate is a ceiling on how much detail the encoder may keep. It governs new compression, not damage already baked into the source.
| Symptom | Higher bitrate helps? | Why |
|---|---|---|
| New blocking from this re-encode | Yes | More bits mean less new quantisation loss |
| Banding on gradients (this pass) | Often | More bits preserve smooth transitions |
| Blocking already baked into source | No | Detail is gone before you started |
| Soft / out-of-focus footage | No | Bitrate can't add sharpness that wasn't shot |
| Low resolution / upscaled look | No | Resolution, not bitrate, is the limit |
| Heavy noise/grain you want kept | Yes | Grain needs lots of bits; raise the target |
Audio kbps guidance for quality work
Audio is re-encoded to AAC at the value you set (max 320). Match the content type.
| Content | Audio kbps | Notes |
|---|---|---|
| Speech / podcast | 128 | Transparent for voice |
| General mixed | 192 | Safe default |
| Music / soundtrack | 256–320 | Near-transparent AAC |
| Already-lossy 128k source | 128 | Higher won't recover lost audio detail |
Cookbook
Scenarios where a higher target genuinely helps — plus one where it doesn't — each with the numbers you type and the command the tool runs.
Stop a 1080p delivery encode from adding blocking
You must re-encode a clean 1080p source for delivery and don't want this pass to introduce artefacts.
Source: clean 1080p, ~12 Mbps Video kbps: 12000 Audio kbps: 256 ffmpeg -i clean.mov -c:v libx264 -preset medium \ -b:v 12000k -maxrate 14400k -bufsize 24000k \ -c:a aac -b:a 256k -movflags +faststart out.mp4 Result: near-transparent re-encode, minimal new loss
Preserve film grain through a re-encode
Grain is detail and eats bitrate. Starve it and grain turns to mush or blocks. Give it room.
Source: grainy 1080p film transfer Video kbps: 18000 Audio kbps: 192 High target lets libx264 keep grain structure instead of smearing it into blocks
Re-encode an editing intermediate at high bitrate
You'll re-edit/colour-grade later, so you want a generous intermediate (note: this is still H.264 MP4 — for a true edit codec use the ProRes encoder).
Video kbps: 30000 Audio kbps: 320 ffmpeg ... -b:v 30000k -maxrate 36000k -bufsize 60000k ... Better intermediate: prores-encoder for grading work
Raise audio to 320 for a concert clip
Video bitrate handles the picture; bump audio separately for music.
Video kbps: 9000 Audio kbps: 320 ffmpeg ... -b:v 9000k ... -c:a aac -b:a 320k ... Audio stays crisp; video has ample headroom
The case where it doesn't help
A clip already destroyed by hard compression won't improve no matter how high you set the number.
Source: 720p that was already crushed to 500 kbps (blocky) Video kbps: 8000 Result: an 8 Mbps file that faithfully reproduces the SAME blocky source -> bigger file, no new quality. Fix = find a better source copy
Edge cases and what actually happens
Higher bitrate, same blocky picture
No gainIf the source was already heavily compressed, the blocking is baked in. Raising Video kbps faithfully reproduces those blocks at a larger size — it cannot reverse quantisation that already happened. The only real fix is a higher-quality source copy.
File got much bigger but it doesn't look sharper
ExpectedBitrate caps how much detail the encoder *may* keep; it can't add detail that isn't in the frames. On an already-good source a higher target mostly just preserves what's there — diminishing returns set in past the 'near-transparent' column in the table.
Setting target above the source bitrate
ExpectedTargeting 18000 on a 6000 kbps source won't make it look like a 18000 kbps original — libx264 only has the source's existing detail to encode. The file may not even grow much beyond the source's information content.
You wanted to fix softness or upscaled look
Wrong leverBitrate doesn't add sharpness or resolution. Soft footage stays soft; upscaled footage stays upscaled. For resolution changes use the video resizer; bitrate only governs compression.
Capped at 50000 kbps
LimitThe Video kbps field maxes at 50000 (50 Mbps). For most 1080p/4K H.264 that's already near-transparent. If you genuinely need more efficiency at high quality, a different codec helps more than more H.264 bits — see the H.265 encoder.
Audio quality didn't improve past 128k source
No gainRe-encoding a 128 kbps audio track at 320 kbps can't recover detail the original lossy file already discarded — it just makes a larger AAC file. Higher audio bitrate only helps when the source audio still has that detail.
4K high-bitrate encode runs out of memory
Memory limitHigh-bitrate 4K encodes are heavy for FFmpeg.wasm. If the heap is exhausted, work on shorter segments or a 1080p version. The browser sandbox has finite memory.
You actually need an edit-grade codec
Wrong toolThis tool always outputs H.264 MP4, which is a delivery codec — not ideal as a grading/edit intermediate even at high bitrate. For editing use the ProRes encoder.
Source over your tier's size cap
RejectedFree 1 GB / 1 file, Pro 10 GB / 5, Pro-media 100 GB / 50, Developer 100 GB / unlimited. Files above the cap are rejected before encoding. No duration cap applies.
Frequently asked questions
Will increasing the bitrate fix my blocky video?
Only if the blocking comes from *this* re-encode. If the source was already compressed into blocks, a higher target just reproduces those blocks at a larger size — it can't undo damage already in the frames. The cure for a bad source is a better source copy.
How high should I set the bitrate to keep quality?
Set it at or above the source's existing bitrate so libx264 isn't forced to discard detail. The quality-preserving table gives per-resolution starting points (e.g. ~12000 kbps for a near-transparent 1080p H.264 encode).
Does a higher number always mean better quality?
Up to a point. Once you're past the level where artefacts disappear, extra bits mostly just grow the file. Quality is bounded by the source — bitrate is a ceiling, not a quality generator.
Can I recover detail lost in an earlier compression?
No. Lost detail is gone. The best you can do when re-encoding is avoid adding *new* loss by giving the encoder enough bits, which is exactly what raising Video kbps does.
What's the maximum bitrate I can set?
50000 kbps for video and 320 kbps for audio. For H.264 that's already near-transparent at most resolutions; beyond that, a more efficient codec helps more than more bits.
Should I use this for an editing intermediate?
It produces H.264 MP4, which is a delivery format. A high bitrate makes it a decent intermediate in a pinch, but for serious editing/grading use the ProRes encoder.
Does it use two-pass for accuracy?
No — single pass -b:v with auto maxrate/bufsize. For quality work the exact average matters less than the headroom; set a generous number and you're fine.
Will it improve audio if I raise Audio kbps?
Only if the source audio still has the detail. Re-encoding a 128 kbps source at 320 can't restore what the original lossy codec discarded — it just makes a bigger AAC file. For a high-quality source, 256–320 keeps music crisp.
Does this change my resolution?
No. It only affects bitrate. To change resolution use the video resizer; softness and upscaling are resolution issues, not bitrate ones.
Is the file uploaded anywhere?
No. Encoding runs in your browser via FFmpeg.wasm, so even a large high-bitrate intermediate never leaves your machine. Free allows up to a 1 GB source.
Why is the output MP4 even though I want quality?
The tool always writes faststart MP4 (H.264). It's a high-compatibility delivery container. If you need a different container or codec, use the video transcoder or a dedicated encoder.
Would H.265 give better quality than just raising H.264 bitrate?
Often yes — H.265 keeps more detail at the same bitrate. If file efficiency at high quality matters, try the H.265 encoder instead of pushing H.264 to its ceiling.
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.