How to downscale 4k video to 1080p with no visible quality loss
- Step 1Drop the 4K master onto the resizer — Drag in the 3840×2160 file —
.mp4,.mov,.mkv, or any accepted format. Everything runs locally in FFmpeg.wasm; the master is never uploaded. Check your tier's file-size cap first: Free 1 GB, Pro 10 GB, Pro + Media 100 GB. - Step 2Set Width to 1920 — Type
1920into the Width (px) box. Since a 4K UHD frame is a true 16:9, this is all you need — the height resolves to 1080 automatically. - Step 3Confirm Lock aspect ratio is ON — The default-on Lock aspect ratio toggle makes the tool run
scale=1920:-2:flags=lanczos. The-2rounds the derived height to an even number (1080, already even), so a 16:9 4K source lands exactly on 1920×1080. - Step 4Leave Height alone — With Lock on, the Height box is ignored — you don't need to enter 1080. The aspect ratio is computed from the source. Only touch Height if your 4K source was cropped to a non-16:9 ratio and you want a forced box (Lock off).
- Step 5Run the downscale — Click process. FFmpeg.wasm applies the Lanczos scale, then re-encodes with
libx264 -preset medium -crf 20, copying the audio. A typical 4K clip processes at well below real-time on a modern machine; very long masters scale with duration. - Step 6Compare against the master and download — Output is always
.mp4. Eyeball the 1080p result next to the master at 1:1 — for normal content you won't see a difference. If you need an even smaller file for a hard cap, pass the 1080p result to the bitrate setter or a size-targeted compressor.
Why Lanczos beats the alternatives for 4K → 1080p
Downscale quality by resampling algorithm. JAD's resizer is hard-wired to Lanczos (flags=lanczos) — the comparison is to what other quick tools commonly use.
| Algorithm | Sharpness on downscale | Aliasing risk | Used by JAD? |
|---|---|---|---|
| Lanczos | Highest — preserves edge/texture detail | Low (windowed sinc) | Yes — flags=lanczos |
| Bicubic | Good, slightly softer than Lanczos | Low–moderate | No |
| Bilinear | Soft, smears fine detail | Higher on textures | No |
| Nearest neighbour | Blocky, never use for downscale | Severe | No |
File-size and detail change: 4K master vs 1080p downscale
Indicative outcomes for a downscale at the resizer's fixed CRF 20 / preset medium. Exact sizes depend on motion and content complexity — CRF is a quality target, not a size target.
| Property | 4K master (typical) | 1080p downscale (this tool) |
|---|---|---|
| Resolution | 3840×2160 | 1920×1080 |
| Pixels per frame | 8.3 million | 2.1 million (¼) |
| Perceived sharpness at 1080p playback | Reference | Indistinguishable for most content |
| Codec | Often HEVC / 10-bit | H.264 8-bit (libx264) |
| Audio | Original | Identical — stream-copied |
| File size | Largest | Much smaller (typically a large fraction off) |
Cookbook
Real 4K-to-1080p downscale runs. The arguments shown are exactly what FFmpeg.wasm executes.
Standard 4K UHD master → visually-lossless 1080p
The bread-and-butter case. A 3840×2160 16:9 master scaled to 1920 wide produces exactly 1080 tall, re-encoded once at CRF 20. The result is a clean viewing/sharing copy.
Input: master_4k.mov 3840x2160 16:9 HEVC Control: Width = 1920, Lock aspect ratio = ON FFmpeg runs: -vf scale=1920:-2:flags=lanczos -c:v libx264 -preset medium -crf 20 -c:a copy Output: master_4k.mp4 1920x1080 H.264 + original audio
Cinematic 2.39:1 4K → 1080p (height is NOT 1080)
A 3840×1606 cinematic 4K crop is not 16:9. Width 1920 + Lock ON keeps the 2.39:1 shape, producing 1920×803. That's correct — the bars were never in the file.
Input: film_grade.mp4 3840x1606 2.39:1 Control: Width = 1920, Lock ON Output: 1920x803 (still 2.39:1, downscaled cleanly) This is 1080p-class width with the original cinematic ratio.
4K screen recording with crisp UI text
Lanczos matters most where there is fine high-frequency detail like UI text and thin lines. A 4K screen capture downscaled with Lanczos keeps menu labels legible where bilinear would blur them.
Input: demo_4k_capture.mp4 3840x2160 Control: Width = 1920, Lock ON Lanczos preserves 1px UI strokes and small fonts. If text still needs to be larger, crop to the region of interest first with /video-tools/video-cropper, then resize.
4K HDR master — check for washed-out colour
The resizer does not tone-map. A 10-bit HEVC HDR 4K master re-encoded to 8-bit libx264 can look flat. Downscale resolution here, but handle the HDR→SDR conversion with a tool that controls colour.
Input: hdr_master.mov 3840x2160 HDR10 (PQ) Control: Width = 1920, Lock ON Output: 1920x1080 8-bit H.264 — may look dim/washed For HDR delivery, use /video-tools/video-transcoder to keep 10-bit, or grade before resizing.
Downscale, then hit a hard file-size cap
CRF 20 is a quality target, so even a 1080p downscale of a long 4K clip can be sizeable. Chain the resize with a size-targeted tool when you need a guaranteed cap.
Step 1 (this tool): 3840x2160 -> 1920x1080 at CRF 20 Step 2: feed the 1080p MP4 to /video-tools/email-compressor (25 MB Gmail cap), or /video-tools/discord-compressor (25 / 50 MB cap), or /video-tools/video-bitrate-set (exact kbps)
Edge cases and what actually happens
4K UHD 16:9 → exactly 1920×1080
ExpectedA standard 3840×2160 source scaled to width 1920 with Lock on lands on 1080 height every time — scale=1920:-2 derives 1080, which is already even, so there is zero rounding drift. This is the canonical no-quality-loss downscale.
Downscale looks SHARPER than a native 1080p shot
By designBecause Lanczos averages four source pixels into one, fine detail is preserved better than in footage natively captured at 1080p. This 'supersampling' effect is why downscaling from 4K is the highest-quality way to produce 1080p — it's a feature, not an artefact.
Single CRF 20 re-encode introduces mild generation loss
Expected (visually transparent)There is exactly one libx264 pass at CRF 20. For 4K→1080p this is below the threshold most viewers can detect. If you will re-encode the result again later, be aware each pass compounds — keep the 4K master as your true archive copy.
HDR source not tone-mapped
Watch colourThe resizer re-encodes to 8-bit libx264 without HDR→SDR tone mapping. A 10-bit HDR 4K master can come out dim or washed-out. For HDR-aware downscaling use the video transcoder to keep 10-bit/HEVC, or grade the footage first.
High-grain or high-motion 4K produces a large 1080p file
ExpectedCRF is a quality target, not a size target, so heavily-grained film or fast action keeps a high bitrate even at 1080p. The downscale shrinks the file, but if you need a guaranteed size use the bitrate setter or a size-targeted compressor afterwards.
4K master exceeds the Free 1 GB cap
1 GB capLong 4K masters easily exceed 1 GB. Upgrade to Pro (10 GB) or Pro + Media (100 GB), or trim the clip down first. The video pipeline streams, so there is no duration limit — only the file-size cap matters.
Non-16:9 4K crop won't be 1080 tall
By designA cinematic or vertical 4K crop keeps its ratio with Lock on, so the height won't be 1080. To force a 1920×1080 box turn Lock off (which distorts a non-16:9 source) or crop to 16:9 first with the video cropper.
8K source downscaled to 1080p
SupportedThe Width input ceiling is 7680, but you can set width 1920 to take a 7680×4320 8K source straight to 1080p in one Lanczos pass. The downscale ratio is steeper (16:1 pixel reduction) so the supersampling sharpening effect is even stronger.
Frequently asked questions
Can you really downscale 4K to 1080p with no visible quality loss?
For most content, yes. The resizer uses Lanczos resampling and a single libx264 CRF 20 pass — at 1080p playback distances the result is indistinguishable from the master. You're discarding pixels a 1080p screen can't show anyway, so the perceptual cost is essentially nil. Grainy film, HDR sources, and heavy compression downstream are the exceptions to watch.
Why does a downscale from 4K look sharper than native 1080p?
Downscaling averages multiple source pixels into each output pixel (a form of supersampling). That extra information makes edges and textures crisper than footage shot natively at 1080p. It's the main reason editors deliver 1080p from 4K masters rather than shooting 1080p directly.
What downscale algorithm does the tool use?
Lanczos, hard-wired via flags=lanczos in the scale filter. It's the sharpest practical resampler in FFmpeg — better than the bilinear scaling many quick web converters default to, which softens detail when shrinking.
Does it re-encode, and how much quality is lost?
Yes — exactly one pass with libx264 at CRF 20, preset medium. For a 4K→1080p downscale this is visually transparent for typical content. The audio is stream-copied, so only the video is touched, once.
How much smaller will the 1080p file be?
Substantially — 1080p has a quarter of the pixels of 4K, and the CRF 20 H.264 output is much smaller than a typical 4K HEVC master. Exact size depends on motion and grain because CRF targets quality, not a fixed size. For a guaranteed cap, follow with the bitrate setter.
Will my HDR 4K video look right after downscaling?
Not necessarily. The resizer doesn't tone-map, so a 10-bit HDR source re-encoded to 8-bit H.264 can look dim or washed-out. For HDR-aware work use the video transcoder to keep 10-bit/HEVC, or grade before resizing.
Is my 4K footage uploaded?
No. The downscale runs entirely in your browser through FFmpeg.wasm. Even a confidential or unreleased 4K master stays on your machine — only an anonymous processed-file counter is recorded for dashboard stats.
What's the largest 4K file I can downscale?
Free tier: 1 GB. Pro: 10 GB. Pro + Media: 100 GB. Developer: 100 GB with unlimited batch. Long 4K masters often exceed 1 GB, so check your tier or trim first. There's no duration cap — only the file-size limit applies.
Can I downscale 8K to 1080p too?
Yes. The Width box accepts up to 7680, but for 1080p you set width 1920 and an 8K (7680×4320) source goes straight to 1920×1080 in one Lanczos pass. The steeper downscale ratio makes the supersampling sharpening effect even stronger.
Should I keep the 4K master after downscaling?
Yes — keep the 4K as your archive. The 1080p output is a viewing/sharing copy. If you later need a different resolution or want to avoid stacking generation loss, always go back to the master rather than re-encoding the 1080p.
Can I pick the output codec or container?
No — the resizer always outputs MP4/H.264 at CRF 20. To choose the codec (HEVC, AV1, ProRes, VP9) or a different container, use the video transcoder instead.
My cinematic 4K came out 1920×803, not 1080. Is that wrong?
No — that's correct for a 2.39:1 source. With Lock on, the tool keeps your source's aspect ratio and only fixes the width, so a cinematic crop stays cinematic. The bars were never part of the file; the 1920-wide output is the right 1080p-class result.
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.