Master 4K video conversion with this comprehensive guide covering UHD vs DCI resolutions, codec selection, bitrate settings, HDR handling, and hardware vs software encoding for optimal results.
4K video has moved from a professional luxury to an everyday reality. Modern smartphones, action cameras, drones, and mirrorless cameras all record in 4K resolution. The problem is that 4K files are massive, codec support varies wildly across devices, and getting the right balance between quality and file size requires understanding the technical landscape.
This guide covers everything you need to know about working with 4K content: resolution standards, codec choices, bitrate recommendations, hardware acceleration, and HDR considerations. Whether you are a content creator preparing YouTube uploads, a filmmaker delivering to clients, or someone who just wants their drone footage to play on the living room TV, this guide has you covered.
"4K" is not a single resolution. There are several standards, and confusing them can lead to incorrect conversion settings.
| Resolution Name | Pixels (W x H) | Aspect Ratio | Common Use |
|---|---|---|---|
| UHD (4K UHD) | 3840 x 2160 | 16:9 | Consumer TVs, streaming, YouTube |
| DCI 4K | 4096 x 2160 | ~17:9 (1.9:1) | Cinema projection, film production |
| 4K Anamorphic | 3840 x 1600 | 2.4:1 | Widescreen cinema |
| WQHD (not 4K) | 2560 x 1440 | 16:9 | Gaming monitors (often confused with 4K) |
| 8K UHD | 7680 x 4320 | 16:9 | Next-gen TVs (future standard) |
For most people, "4K" means UHD at 3840 x 2160. This is what YouTube, Netflix, and consumer TVs use. DCI 4K (4096 x 2160) is primarily used in professional cinema workflows.
Pro Tip: When converting 4K footage for YouTube, always use 3840 x 2160. YouTube recognizes this as 4K and enables the 4K quality option for viewers. DCI 4K (4096 x 2160) will be cropped or letterboxed, potentially losing resolution.
The codec you choose has a dramatic impact on file size, quality, compatibility, and encoding time. Here is how the major codecs compare for 4K content:
The most compatible codec, supported by virtually every device made in the last decade. However, H.264 was not designed for 4K and requires very high bitrates to maintain quality at UHD resolution.
ffmpeg -i input_4k.mp4 -c:v libx264 -crf 18 -preset slow \
-c:a aac -b:a 256k output_4k_h264.mp4
The successor to H.264, HEVC delivers roughly the same quality at 40-50% lower bitrates. This makes it ideal for 4K, where file sizes can balloon quickly with H.264.
ffmpeg -i input_4k.mp4 -c:v libx265 -crf 22 -preset slow \
-c:a aac -b:a 256k output_4k_hevc.mp4
The newest major codec, AV1 offers the best compression efficiency, with 30-50% savings over HEVC. The downside is significantly slower encoding time and limited hardware decoder support (though this is improving rapidly with newer devices).
ffmpeg -i input_4k.mp4 -c:v libaom-av1 -crf 28 -cpu-used 4 \
-row-mt 1 -c:a libopus -b:a 192k output_4k_av1.webm
Google's open-source codec, VP9 is the predecessor to AV1 and the default codec for YouTube at 4K. It offers compression between H.264 and HEVC.
ffmpeg -i input_4k.mp4 -c:v libvpx-vp9 -crf 30 -b:v 0 \
-row-mt 1 -c:a libopus -b:a 192k output_4k_vp9.webm
| Codec | Compression Efficiency | Encoding Speed | Hardware Support | Licensing |
|---|---|---|---|---|
| H.264 | Baseline | Fast | Universal | Royalties (MPEG LA) |
| H.265/HEVC | ~50% better than H.264 | Moderate | Most modern devices | Complex royalties |
| VP9 | ~35% better than H.264 | Moderate | Chrome, Android, smart TVs | Royalty-free |
| AV1 | ~50-60% better than H.264 | Very slow (software) | Newer devices (2022+) | Royalty-free |
For a detailed breakdown of codec differences, read our comprehensive guide on H.265 vs H.264 vs AV1.
Bitrate is the single most important factor controlling 4K video quality and file size. Too low and you get compression artifacts; too high and you waste storage and bandwidth.
| Codec | 4K 24fps | 4K 30fps | 4K 60fps | 4K HDR 60fps |
|---|---|---|---|---|
| H.264 | 35-45 Mbps | 45-55 Mbps | 55-80 Mbps | 60-85 Mbps |
| H.265/HEVC | 15-25 Mbps | 20-30 Mbps | 30-45 Mbps | 35-50 Mbps |
| VP9 | 20-30 Mbps | 25-35 Mbps | 35-50 Mbps | 40-55 Mbps |
| AV1 | 12-20 Mbps | 15-25 Mbps | 20-35 Mbps | 25-40 Mbps |
YouTube re-encodes everything you upload, so providing a high-quality source is essential. YouTube recommends:
For complete YouTube optimization, see our best video settings for YouTube guide.
Pro Tip: When in doubt, use CRF mode instead of fixed bitrate. CRF automatically adjusts the bitrate based on content complexity. For 4K, start with CRF 18 (H.264) or CRF 22 (H.265) and adjust from there. Static scenes will use less bitrate while complex action sequences get more, resulting in consistent visual quality throughout.
4K video encoding is computationally intensive. A 10-minute 4K clip can take anywhere from 5 minutes to several hours to encode depending on your method.
Software encoders like libx264, libx265, and libaom-av1 run entirely on your CPU. They produce the best quality per bitrate but are slow, especially for 4K.
# High-quality software encode (slow but best quality)
ffmpeg -i input_4k.mp4 -c:v libx265 -crf 22 -preset slow \
-pix_fmt yuv420p10le -c:a aac -b:a 256k output.mp4
Modern GPUs include dedicated video encoding hardware. NVIDIA has NVENC, AMD has VCE/VCN, Intel has Quick Sync, and Apple has VideoToolbox. These are dramatically faster but produce slightly larger files at the same quality level.
# NVIDIA NVENC (fast hardware encode)
ffmpeg -i input_4k.mp4 -c:v hevc_nvenc -preset p7 -cq 24 \
-c:a aac -b:a 256k output_nvenc.mp4
# Apple VideoToolbox (Mac)
ffmpeg -i input_4k.mp4 -c:v hevc_videotoolbox -q:v 55 \
-c:a aac -b:a 256k output_vtb.mp4
# Intel Quick Sync
ffmpeg -i input_4k.mp4 -c:v hevc_qsv -global_quality 24 \
-c:a aac -b:a 256k output_qsv.mp4
| Method | Approximate Time | Quality per Bitrate | Best For |
|---|---|---|---|
| libx265 (preset slow) | 45-90 minutes | Excellent | Final delivery, archiving |
| libx265 (preset medium) | 25-50 minutes | Very good | General purpose |
| libx265 (preset fast) | 15-30 minutes | Good | Quick conversions |
| NVENC HEVC (p7) | 3-6 minutes | Good | Batch processing, streaming |
| NVENC HEVC (p1) | 1-3 minutes | Moderate | Live streaming, previews |
| VideoToolbox HEVC | 4-8 minutes | Good | Mac workflows |
| Quick Sync HEVC | 3-7 minutes | Good | Intel-based systems |
Many modern 4K cameras and displays support High Dynamic Range (HDR), which provides a wider range of brightness and color. Converting HDR content requires special care to preserve the expanded color information.
| HDR Format | Color Space | Transfer Function | Metadata |
|---|---|---|---|
| HDR10 | BT.2020 | PQ (SMPTE ST 2084) | Static |
| HDR10+ | BT.2020 | PQ | Dynamic (scene-by-scene) |
| Dolby Vision | BT.2020 | PQ | Dynamic (frame-by-frame) |
| HLG | BT.2020 | HLG | None (backwards compatible) |
To maintain HDR metadata during a format conversion:
# Convert HDR10 content while preserving color information
ffmpeg -i input_hdr.mkv \
-c:v libx265 -crf 20 -preset slow \
-pix_fmt yuv420p10le \
-color_primaries bt2020 \
-color_trc smpte2084 \
-colorspace bt2020nc \
-x265-params "hdr-opt=1:repeat-headers=1:colorprim=bt2020:transfer=smpte2084:colormatrix=bt2020nc:max-cll=1000,400" \
-c:a copy output_hdr.mp4
If your target device does not support HDR, you need to tone-map the content to SDR. FFmpeg can do this with the zscale and tonemap filters:
ffmpeg -i input_hdr.mkv \
-vf "zscale=t=linear:npl=100,format=gbrpf32le,zscale=p=bt709,tonemap=tonemap=hable:desat=0,zscale=t=bt709:m=bt709:r=tv,format=yuv420p" \
-c:v libx264 -crf 18 -preset slow \
-c:a copy output_sdr.mp4
This converts the HDR10 content to standard BT.709 color space with Hable tone mapping, which produces natural-looking results on SDR displays.
Sometimes you need to downscale 4K content for compatibility, storage, or bandwidth reasons. Downscaling produces excellent results because you are discarding information rather than inventing it (as with upscaling).
# 4K to 1080p (Full HD)
ffmpeg -i input_4k.mp4 -vf "scale=1920:1080" \
-c:v libx264 -crf 20 -preset slow -c:a copy output_1080p.mp4
# 4K to 1440p (2K)
ffmpeg -i input_4k.mp4 -vf "scale=2560:1440" \
-c:v libx264 -crf 20 -preset slow -c:a copy output_1440p.mp4
# 4K to 720p (HD)
ffmpeg -i input_4k.mp4 -vf "scale=1280:720" \
-c:v libx264 -crf 22 -preset slow -c:a copy output_720p.mp4
Pro Tip: Use the lanczos scaling algorithm for the best downscaling quality. It is slower than the default bilinear filter but produces sharper results with fewer artifacts:
ffmpeg -i input_4k.mp4 -vf "scale=1920:1080:flags=lanczos" \
-c:v libx264 -crf 18 -c:a copy output_1080p.mp4
For an easier approach, use the Video Converter which handles resolution changes and codec selection through a visual interface, or the Video Compressor for one-click file size reduction.
# Step 1: Convert camera file to YouTube-optimized MP4
ffmpeg -i camera_4k.mov \
-c:v libx264 -crf 18 -preset slow \
-pix_fmt yuv420p \
-movflags +faststart \
-c:a aac -b:a 256k \
youtube_upload.mp4
Drone footage is often recorded in H.265 at high bitrates. Converting to AV1 can save 40-60% storage:
ffmpeg -i drone_4k.mp4 \
-c:v libaom-av1 -crf 28 -cpu-used 4 -row-mt 1 \
-c:a libopus -b:a 128k \
drone_archive.mkv
Social media platforms generally do not benefit from 4K input and will re-encode to lower resolutions for most viewers. Downscale to 1080p for faster uploads and identical visual results for the majority of viewers:
ffmpeg -i source_4k.mp4 \
-vf "scale=1080:1920:flags=lanczos" \
-c:v libx264 -crf 22 -preset slow \
-c:a aac -b:a 128k \
social_media.mp4
For platform-specific video requirements, check our social media video specs guide and our guide on converting video for Instagram Reels and TikTok.
Planning storage and bandwidth for 4K video requires understanding approximate file sizes.
| Codec | Quality Level | 4K 30fps | 4K 60fps |
|---|---|---|---|
| H.264 | High (CRF 18) | ~350 MB/min | ~550 MB/min |
| H.264 | Balanced (CRF 23) | ~200 MB/min | ~320 MB/min |
| H.265 | High (CRF 20) | ~180 MB/min | ~280 MB/min |
| H.265 | Balanced (CRF 24) | ~100 MB/min | ~160 MB/min |
| AV1 | High (CRF 25) | ~120 MB/min | ~190 MB/min |
| AV1 | Balanced (CRF 30) | ~70 MB/min | ~110 MB/min |
These are rough estimates. Actual sizes vary significantly based on content complexity: talking head footage compresses much smaller than fast-action sports.
When you have multiple 4K files to process, automation is essential.
#!/bin/bash
# Batch convert all 4K MOV files to H.265 MP4
mkdir -p converted
for file in *.mov; do
output="converted/${file%.mov}.mp4"
ffmpeg -i "$file" -c:v libx265 -crf 22 -preset medium \
-c:a aac -b:a 192k -movflags +faststart "$output"
echo "Converted: $file -> $output"
done
For a more comprehensive batch processing setup, see our batch processing guide or use our online batch conversion feature.
4K has four times the pixels of 1080p, so encoding takes roughly four times longer. Solutions:
-preset fast or -preset veryfast)-threads 0 for automatic)-row-mt 1)Reduce the bitrate or increase the CRF value. For H.265, a CRF increase of 6 roughly halves the file size. You can also downscale to 1080p, which is visually indistinguishable from 4K on screens smaller than 50 inches.
This is usually a color space mismatch. Ensure you preserve the color metadata:
ffmpeg -i input.mp4 -c:v libx265 -crf 22 \
-color_primaries bt709 -color_trc bt709 -colorspace bt709 \
-c:a copy output.mp4
4K playback requires significant hardware resources. If the target device struggles, consider using a more widely supported codec (H.264 over H.265 for older devices) or downscaling to 1080p.
Yes. YouTube allocates higher bitrate to 4K uploads, so even viewers watching at 1080p benefit from a 4K source because the downscaled version retains more detail. Upload in 4K whenever possible.
H.265 is strongly recommended for 4K. The 40-50% bitrate savings are significant at 4K resolutions, and compatibility is no longer a major concern as most devices from 2018 onward support HEVC decoding. See our codec comparison guide for details.
It depends on duration, codec, preset, and hardware. A 10-minute 4K clip takes approximately 30-60 minutes with software H.265 encoding at medium preset, or 3-6 minutes with hardware encoding (NVENC). Use the Video Converter for cloud-based processing that offloads the work from your machine.
Technically yes, but it does not add real detail. Upscaling interpolates pixels, resulting in a larger file with no additional sharpness. AI-based upscaling tools produce better results but still cannot match native 4K.
Working with 4K video requires understanding resolutions, codecs, bitrates, and encoding methods. The key takeaways are: use H.265 or AV1 for the best compression, leverage hardware encoding for speed, preserve HDR metadata when applicable, and choose bitrates based on your delivery target.
For quick conversions without the command-line learning curve, the Video Converter handles all of these settings through an intuitive interface. For compression-focused workflows, the Video Compressor provides one-click file size reduction while maintaining visual quality.
Whether you are archiving drone footage, preparing YouTube uploads, or delivering 4K content to clients, the techniques in this guide ensure you get the best possible results from your high-resolution material.
Marcus Rivera
Systems engineer writing about video transcoding, hardware acceleration, and large-scale media processing.