The difference between interlaced and progressive scan video is how the picture’s horizontal lines are delivered over time. Progressive video draws every line as one complete frame, while interlaced video splits the picture into two alternating-line fields captured or displayed at different moments.
For most modern editing, computer-display and YouTube workflows, progressive video is the simpler default. Interlaced footage is not automatically unusable, though: if you have older recordings or a delivery system that expects fields, preserve the field structure or deinterlace it deliberately rather than changing a label and hoping for the best.
Progressive versus interlaced: the short answer
The letter in a format label tells you the scan method. The number generally describes the vertical line count. In 1080p, the 1080 refers to the nominal vertical scan-line count and the p means progressive. In 1080i, the same nominal line count is interlaced.
That shared number does not mean the two formats present motion in the same way. A progressive frame is a complete image associated with one point in time. An interlaced frame is made from two fields containing alternating lines. Those fields are captured or displayed one after the other, so movement can occur between them.
A person walking across the image might therefore occupy a slightly different position in the first field from the second. If playback or editing combines the fields as if they were one simultaneous picture, the edges can look like a row of horizontal teeth. This is the familiar combing effect.
Interlacing was developed for television transmission where bandwidth was constrained. It remains relevant in analogue transfers, some older cameras and recordings, and delivery workflows that specifically require an interlaced signal. Modern digital systems typically use progressive scanning, but the correct choice still depends on the source and destination.
A useful first rule is simple:
- Use progressive settings for new recordings and modern computer-oriented work unless a real requirement says otherwise.
- Treat interlaced material as interlaced until you have checked its field order and decided how it will be delivered.
- Do not assume that deinterlacing is a harmless metadata change. It creates new progressive frames from fields and can affect motion detail.
The difference between a 24/7 channel built from one short video and a conventional upload also matters here. Repeating a source file continuously does not fix a scan-format mistake inside that file.
How progressive frames are scanned
A progressive frame contains all of its horizontal lines in sequence from top to bottom. The important point is not merely that the lines are drawn in order. It is that the frame represents a complete image rather than two alternating fields.
Suppose a camera records a progressive frame of a moving singer. The lines at the top and bottom belong to the same frame time, within the limits of the camera’s capture process. When an editor displays that frame as a still image, the face, microphone and background are not assembled from two separate moments.
This makes progressive footage easier to reason about in common editing tasks. A freeze frame is based on a complete image. Scaling and rotating do not require you to keep track of which lines belong to which field. Slow motion can work from complete frames, although its smoothness still depends on the source frame rate and the way the editor creates or repeats motion.
Progressive does not mean that motion is automatically smooth or that every progressive format has the same visual quality. A low frame rate can still make fast movement appear less fluid. Compression can still soften detail or create block-like artefacts. The p only tells you how the image is scanned, not how much data it contains or how well it was photographed.
The same distinction matters when preparing a long devotional loop, study stream or ambience video. Keep the project’s scan mode consistent with the source where possible. If your original file is progressive, importing it into an interlaced project can introduce unnecessary conversion. If your source is interlaced, changing the project setting to progressive does not by itself repair the fields.
When comparing delivery settings, separate three questions:
- How many vertical lines does the format describe?
- Is each image progressive or interlaced?
- What frame or field rate does the label represent?
These are related but different properties. Treating them as one number is how a format comparison becomes misleading.
How interlaced fields work
Interlaced video divides a nominal frame into two fields. One field contains one set of alternating horizontal lines and the other contains the lines between them. Adobe describes the upper field as odd-numbered lines and the lower field as even-numbered lines, although field-order conventions need to be checked for the particular source and system.
The fields are drawn in sequence. The ITU glossary describes one field as beginning one field period after the other. That time separation is the central fact behind interlaced motion behaviour.
Imagine a 1080i recording of a moving hand. The first field records one position of the hand, and the second field records a later position. When both fields are displayed correctly on an interlaced display, the timing is part of the format. When the fields are viewed together as one progressive still, the hand may have two slightly different outlines.
This is why the word “frame” can cause confusion. An interlaced frame is a container for two fields, not necessarily one complete image captured at one instant. The two fields may provide useful temporal information, but they must be interpreted according to their field order and intended display method.
Field order tells the system which field comes first. If the order is wrong, motion can appear to jump backwards and forwards at fine intervals. The footage may otherwise look correctly exposed and sharply focused, so a field-order mistake can be easy to miss until you inspect movement, pans or scrolling text.
Interlacing also affects thin horizontal detail. Lines that are only one or a few pixels high may flicker, disappear intermittently or behave differently from larger objects. Text overlays, news tickers, building railings and fine patterns deserve particular attention when you review older interlaced material.
The practical lesson is that interlaced video carries both spatial and temporal information in its fields. You should not throw away that structure without deciding what the final playback environment needs.
What 1080p and 1080i indicate
1080p and 1080i both describe formats associated with a nominal 1,080 vertical scan-line count, but the letter changes the scan structure. Sony’s explanation of progressive and interlaced scanning is a useful primary reference for the basic distinction: Sony’s support article explains the p and i labels.
The rate notation needs equal care. An interlaced rate can count fields rather than complete frames. Adobe gives 1080i60 as an example meaning 60 interlaced 1,920 by 1,080 fields per second, approximately 30 frames per second. Its 720p30 example means 30 progressive 1,280 by 720 frames per second.
That means 60i should not automatically be read as 60 complete pictures per second. A field is only part of an interlaced frame. Conversely, 60p refers to 60 progressive frames per second, so its motion timing and image completeness are different even if the number looks similar.
A simplified comparison looks like this:
| Label | What the number describes | What the letter describes | How to read the rate carefully |
|---|---|---|---|
| 720p30 | 720 nominal vertical lines | Progressive frames | 30 complete progressive frames per second |
| 1080i60 | 1,080 nominal vertical lines | Interlaced fields | 60 fields per second, approximately 30 interlaced frames per second |
| 1080p30 | 1,080 nominal vertical lines | Progressive frames | 30 complete progressive frames per second |
| 1080p60 | 1,080 nominal vertical lines | Progressive frames | 60 complete progressive frames per second |
These examples describe scan and rate conventions, not a guarantee of equal image quality. Lens quality, focus, lighting, compression, scaling and the actual camera mode also affect what you see.
Sony lists examples including 24p, 30p and 60p alongside 30i and 60i. Its format notes are manufacturer guidance, so check the documentation for the specific camera, codec and region rather than assuming every product uses a label in exactly the same way.
For a long YouTube stream, inspect the actual source properties in your editor or media player. Do not infer them only from a filename such as final_1080.mp4. A file can have a 1,080-line image while still requiring field-aware handling.
If you are also checking whether your connection can carry a large live output, keep scan mode separate from bitrate. The practical questions in this guide to 4K and 60fps streaming on Indian broadband concern sustained data delivery, while progressive or interlaced describes how the picture itself is organised.
Combing and other field-related artefacts
Combing appears when two fields from different moments are shown together without the correct interlaced display or a suitable deinterlacing process. A moving object develops alternating horizontal edges, making it resemble a comb. Fast pans, hand gestures and scrolling text make the effect easier to notice.
A related problem is incorrect field order. The image may not show obvious combing in every shot, but motion can look uneven because the later field is being displayed before the earlier one. This can happen when footage is interpreted with the wrong field-order setting or passed through a workflow that changes it.
Thin horizontal lines can flicker because the lines are split between fields and are not always represented with the same timing. This is one reason text overlays and fine architectural detail should be checked on the intended display, not only in a still frame from an editor.
Interlaced footage can also be awkward for freeze frames and slow motion. A freeze made from an untreated interlaced frame may contain two moments of movement. Slow motion may expose field-order errors or make the alternating fields more visible. Adobe discusses these editing concerns in its Premiere overview of interlaced video.
Scaling, rotating and applying effects can introduce further problems if the software treats the fields as ordinary progressive lines. Adobe’s After Effects documentation recommends field-aware handling when working with interlaced or field-rendered footage. Its guidance on importing and interpreting interlaced video is useful when a clip behaves differently from what its filename suggests.
Not every line-shaped artefact is caused by interlacing. Compression, sharpening, moiré, poor scaling and a camera sensor can create similar-looking patterns. Check a moving section, a still frame and the clip’s metadata before deciding that deinterlacing is the answer.
Preserve fields or deinterlace deliberately
The right choice depends on the source and destination, not on a universal rule that one scan method makes every video better.
Preserve the interlaced structure when the source is interlaced and the final delivery system specifically expects interlaced video. In that case, identify the field order, keep the project settings consistent and use field-aware export options. Avoid unnecessary resizing or effects that ignore field timing.
Deinterlace when you need a progressive file for a modern progressive workflow, computer playback or a destination that does not handle interlaced fields properly. A deinterlacer analyses the fields and produces progressive frames. Depending on the method and the footage, it may weave fields, discard information, blend them or estimate motion between them.
None of those methods is consequence-free. Weaving can leave combing when movement exists. Discarding a field can reduce temporal or vertical information. Blending can soften movement. Motion-compensated methods can produce their own errors around fast-moving objects, fine patterns or difficult edges.
That does not make deinterlacing a mistake. It means you should preview it and choose it intentionally. A good workflow preserves the original interlaced master, creates a progressive working or delivery version, and checks the result at normal speed as well as frame by frame.
Do not simply rename 1080i as 1080p, change an extension or tick a progressive checkbox without processing the fields. Metadata can tell software how to interpret a clip, but it cannot create a complete progressive image from two time-separated fields.
A practical decision table is:
| Your source | Your destination | Sensible first step |
|---|---|---|
| Progressive | Progressive | Keep it progressive and avoid an unnecessary interlaced conversion |
| Interlaced with a known field order | Interlaced requirement | Preserve the fields and field order through the workflow |
| Interlaced | Progressive playback or editing | Deinterlace in a controlled step, then inspect motion and fine detail |
| Unknown scan mode | Any destination | Inspect metadata and moving footage before choosing settings |
| Mixed progressive and interlaced clips | Progressive project | Interpret each clip correctly and deinterlace only the interlaced material that needs it |
If you are digitising a tape or importing an old broadcast recording, retain the untouched capture. Make a working copy for deinterlacing, cropping, noise reduction or scaling. That gives you a way back if a later export reveals field-order or motion problems.
A practical workflow for legacy footage
Start by finding out what the file actually contains. Look at the camera or capture documentation, the editor’s clip properties and a moving section with clear diagonal or horizontal edges. Do not rely only on the file name, because names often preserve a project convention rather than the true scan mode.
Next, identify the field order if the clip is interlaced. If your software offers an interpretation or field-order setting, apply it to the source clip before adding effects. Watch a pan, a person walking and any fine horizontal text. Wrong settings often reveal themselves more clearly in motion than in a paused frame.
Then decide what your final audience will watch. A file intended for a legacy broadcast chain may need its fields preserved. A file intended for a progressive editing timeline or a computer-based playback system may be better deinterlaced. The destination requirement is more useful than a general preference for one label.
Create a short test export before processing an entire archive or a long stream. Include movement, a still shot, thin lines, scrolling text and a fade. Compare the original interpretation, a deinterlaced version and, where appropriate, a field-preserved version. Look for combing, softness, judder and flicker.
Only after that test should you apply the choice to the full file. Keep the original capture and record what you changed. This is especially useful when a devotional programme, local news loop or family archive will be reused many times.
If you are preparing footage for a continuous channel, also test the complete repeat. An isolated clip may look fine while a transition, title card or loop boundary exposes a field mismatch. The same care applies to a lofi visual loop or a study stream, even when the background appears mostly still.
For a computer-run broadcast, an editor and a playback tool may each interpret fields differently. A setup based on OBS or a VPS for a 24/7 podcast stream should therefore be tested with the actual source file, project settings and output path rather than assumed from a tutorial using progressive footage.
Applying the choice to an always-on YouTube channel
For a new always-on YouTube channel, progressive source video is usually the conditional default because it fits modern editing and computer-display workflows with fewer field decisions. That applies to a new bhajan loop, a local information screen, a study timer or a small business presentation when you control the production from the beginning.
It is conditional because the source and delivery requirements still come first. If an older programme is interlaced, do not discard it just because progressive is easier. Confirm the field order, preserve the original and make a deliberate progressive version if that is what your final workflow needs.
Before publishing, watch the material at normal speed. Check faces, moving hands, camera pans, scrolling text and thin lines. A still frame can hide the exact timing problem that viewers will notice during a night-long stream.
Also separate scan-format checks from other live-stream checks. A progressive file can still have a poor bitrate, an unsuitable audio mix or an abrupt loop. A field-correct interlaced file can still be the wrong choice for a progressive destination. If you are preparing a test broadcast, this guide to testing a YouTube lofi radio stream before making it public provides a useful example of checking the complete viewing experience rather than only the source file.
If you use StreamNeo, uploading the checked file and supplying your YouTube stream key removes the need to leave your own computer running overnight, while the source still needs to be prepared with the correct scan handling before upload.
Keep a simple record for each master: source scan mode, field order if applicable, frame or field rate, whether it was deinterlaced, and the export used for the channel. That note can prevent a future editor from treating an interlaced archive as progressive or deinterlacing the same material twice.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is progressive video always better than interlaced video?
No. Progressive is usually simpler for modern editing and computer playback, but interlaced video may be the correct format for a legacy source or a destination that requires fields. The important question is whether the scan structure matches the source and delivery workflow.
What do 60i and 60p mean?
In an interlaced label such as 60i, the 60 commonly refers to fields per second, not 60 complete frames. In 60p, the 60 refers to complete progressive frames per second. Check the specific camera or codec documentation because rate naming can vary by system and region.
Should I deinterlace old footage?
Deinterlace it when you need progressive output and the destination does not handle interlaced fields correctly. Preserve the original, check the field order first and preview the result because deinterlacing can introduce softness, blending, combing or motion-estimation errors.
Can I change 1080i to 1080p by changing the setting?
No. A label change does not turn two time-separated fields into complete progressive frames. You need a deliberate field-aware conversion and should inspect the result before using it in a long video or continuous live channel.