How to fix interlaced tv footage before uploading to youtube
- Step 1Confirm the footage is interlaced — Look for a
1080i/576i/480ilabel or pause on motion and check for comb teeth. Camcorder, broadcast-capture, and old TV-recording footage is commonly interlaced. If it's already1080p/720p, skip the tool. - Step 2Drop the clip onto the deinterlacer — MP4, MOV, MKV, WEBM, AVI, M4V, and TS are accepted. The file loads into the browser FFmpeg engine and is not uploaded to JAD.
- Step 3Use Mode 1 for a standard YouTube upload — Mode
1(yadif=1) keeps the frame rate (e.g. 29.97p out from 29.97i in). This is the right choice for talking-head, vlog, drama, or general TV footage going to YouTube. - Step 4Use Mode 0 for high-motion sports going to YouTube — Mode
0(bob) doubles the rate to 50/59.94p. YouTube supports these high frame rates, so for fast sports or action it can look smoother — at the cost of a larger file. - Step 5Run the deinterlace and let it finish — JAD runs yadif, re-encodes to H.264 CRF 20 preset medium, and copies the audio. HD footage on WASM takes a few minutes; the progress bar tracks it.
- Step 6Upload the progressive MP4 to YouTube — Upload the resulting MP4 directly. Because it's already progressive, YouTube's encoder has less to do and won't re-introduce combing. Resolution is unchanged from your source.
Mode choice by YouTube content type
Both modes output H.264 MP4 inside YouTube's recommended spec. The difference is frame rate.
| Content type | Mode | Result | Why |
|---|---|---|---|
| Vlog / talking head / drama | 1 (yadif=1) | Original rate, e.g. 1080p 29.97 | Matches standard YouTube uploads; smaller file |
| Sports / fast action | 0 (yadif=0 bob) | Doubled rate, e.g. 1080p 59.94 | Smoother motion; YouTube plays HFR natively |
| Already progressive | — | Don't deinterlace | yadif would only soften it |
Output vs. YouTube upload spec
The deinterlacer's fixed output sits well inside YouTube's recommended ingest format.
| Aspect | Tool output | YouTube recommends |
|---|---|---|
| Container | MP4 | MP4 (preferred) |
| Video codec | H.264 | H.264 (recommended) |
| Scan type | Progressive | Progressive |
| Audio | Copied from source | AAC-LC (most sources qualify) |
| Resolution | Unchanged from source | Up to 4K+ |
Tier limits for HD/TV footage
HD interlaced clips are larger than DVD rips; check your tier's file cap.
| Tier | Max file size | Batch files |
|---|---|---|
| Free | 1 GB | 1 |
| Pro | 10 GB | 5 |
| Pro-media | 100 GB | 50 |
| Developer | 100 GB | Unlimited |
Cookbook
YouTube-prep recipes that turn interlaced TV footage into upload-ready progressive MP4.
1080i broadcast clip to 1080p for YouTube
A 1080i 29.97 capture going to YouTube as a standard upload. Mode 1 keeps the rate; resolution is unchanged.
Input: segment.ts, 1920x1080, 29.97i Mode: 1 Filter: -vf yadif=1 Output: segment.mp4, 1920x1080, 29.97p, H.264 → upload as-is
Sports clip at double rate
A 1080i 50-field sports clip where smoother motion helps. Mode 0 produces 1080p 50.
Input: match.mxf-remux.mkv, 1080i (50 fields) Mode: 0 (bob) Output: match.mp4, 1080p 50, smoother motion, larger file
Old camcorder DV footage to YouTube
DV camcorder footage is interlaced SD. Deinterlace with Mode 1; YouTube will handle the upscale on playback.
Input: holiday.avi, 720x576 (or 720x480), interlaced DV Mode: 1 Output: holiday.mp4, progressive, original resolution (YouTube upscales for display; you don't resize here)
Audio kept in sync for a music performance
A live performance capture where audio sync is critical. Stream-copied audio stays locked to the rebuilt frames.
Input: gig.mov, interlaced, AAC stereo Mode: 1 Video: re-encoded H.264 progressive Audio: AAC copied, perfectly in sync Output: gig.mp4
Deinterlace, then resize if you want a smaller upload
The deinterlacer doesn't resize. If you want to downscale before upload, deinterlace first, then resize as a second step.
Step 1: deinterlacer Mode 1 → progressive 1080p MP4 Step 2: /video-tools/video-resizer → 720p if desired YouTube accepts both; resize only to cut upload size.
Edge cases and what actually happens
Footage is already progressive
AvoidIf your clip is already 1080p/720p, deinterlacing only softens it. Upload it directly to YouTube without running this tool.
Expecting YouTube to fix interlacing for you
UnreliableYouTube does re-encode, but its handling of interlaced sources often leaves residual combing or judder on motion. Deinterlacing before upload gives a consistently cleaner result.
The tool does not change resolution
By designDeinterlacing keeps the source resolution. If you want 1080p output from a 1080i source, that's already what you get (the 'i'→'p' is the scan-type change, not a resize). To actually change resolution use the resizer.
Output is always MP4
By designWhatever container you upload, the deinterlaced result is MP4 — which is YouTube's preferred ingest format anyway, so this is convenient here.
Mode 0 file is much larger to upload
ExpectedBob mode doubles the frame count and therefore the file size and upload time. Only use it when the smoother HFR motion is worth it (sports). Otherwise Mode 1 uploads faster.
HD clip over the tier cap
RejectedA long HD interlaced capture can exceed the 1 GB free cap. Pro raises it to 10 GB. Over the cap the file is rejected; split it with the video splitter or upgrade.
Slight softening after deinterlace
ExpectedField interpolation softens the image a little. YouTube's encoder copes with it fine. There's no sharpen option in this tool; sharpen in an editor before upload if it bothers you.
Processing is slow on long HD footage
Expectedyadif runs on FFmpeg.wasm (CPU-bound, no hardware acceleration here), so a long 1080i clip can take several minutes. Leave the tab open.
Frequently asked questions
Doesn't YouTube deinterlace automatically?
It re-encodes everything, but its deinterlacing of interlaced sources is inconsistent and often leaves residual combing or judder on motion. Uploading already-progressive video sidesteps that — YouTube's encoder has nothing to guess and won't re-introduce artefacts.
Which mode for a YouTube upload?
Mode 1 for most content — it keeps the original frame rate (1080i 29.97 → 1080p 29.97), matching standard uploads. Mode 0 (bob) doubles the rate to 50/59.94p for high-motion sports, which YouTube plays natively at the cost of a larger file.
Does this make my 1080i video into 1080p?
Yes, in the sense that matters: the output is progressive at 1080 (same resolution), so it is genuinely 1080p. The deinterlacer changes scan type, not resolution — it does not upscale or downscale.
Is the output format okay for YouTube?
Yes. The tool outputs H.264 in MP4 at CRF 20, which is inside YouTube's recommended ingest spec. You can upload it directly.
Will the audio stay in sync after upload?
Yes. Audio is stream-copied during deinterlacing so it stays locked to the rebuilt video, and YouTube preserves that sync.
Is my footage uploaded to JAD before YouTube sees it?
No. Deinterlacing happens entirely in your browser via FFmpeg.wasm. The only upload is the one you make to YouTube afterwards.
Can I downscale to save upload bandwidth?
Not in this tool — it keeps the source resolution. Deinterlace first, then run the result through the resizer to drop to 720p if you want a smaller upload.
Why is my deinterlaced clip a bit softer?
Interpolating the missing field's lines is inherently softer than native progressive capture. It's unavoidable with interlaced sources. YouTube handles it fine; there's no sharpen option here.
What input formats can I use?
MP4, MOV, MKV, WEBM, AVI, M4V, and TS. The output is always MP4, which is also YouTube's preferred upload container.
How large a file can I deinterlace?
Free allows 1 GB per file, Pro 10 GB, Pro-media and Developer 100 GB. There's no duration cap — only the size cap. Long HD captures may need Pro.
Should I trim before deinterlacing to save time?
Yes if you only need part of the footage. The lossless trimmer cuts at keyframe boundaries with no re-encode, so you can extract the segment first and deinterlace only that.
Does it use my GPU?
No. yadif + libx264 run on FFmpeg.wasm (CPU). Some other JAD video tools use the hardware WebCodecs path, but deinterlacing doesn't, so expect CPU-bound timing on long clips.
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.