Video formats

Interlacing, frame rates and deinterlacing for streaming

Broadcast television still carries decades of interlaced heritage. Streaming screens are progressive. Bridging the two well is one of the quiet details that separates a premium service from an average one.

Key takeaways

  • Interlaced video sends alternating half-pictures (fields); every modern display shows full frames.
  • Deinterlacing is required somewhere — on the server or in the player. Doing it centrally gives consistent results.
  • Good deinterlacing costs CPU, so apply it only to channels that actually need it.
  • Monitor the real output frame rate and processing speed, not just whether a process is running.

Interlaced vs progressive

A progressive frame contains every line of the picture captured at the same moment. An interlaced signal instead transmits fields: one field carries the odd lines, the next carries the even lines, captured a fraction of a second later. Two fields make one frame's worth of lines, but they represent two different instants in time.

Interlacing was a clever way to get smooth motion within the bandwidth of analogue television, and it survived into digital broadcasting: many HD channels are still produced and distributed as 1080i. On a CRT, fields were displayed one after another and the eye blended them. On a flat panel or phone, the two fields must be turned into full frames — and if that is done naively, fast motion shows the familiar "combing" artefacts along moving edges.

Frame rates in practice

Notation varies, but the convention used here is: the number is the rate of full frames for progressive video, and the rate of frames (pairs of fields) for interlaced video. Regions inherited different base rates from their electrical grids.

FormatRegionPictures per secondTypical content
1080i25 (often written 50i)Europe and 50 Hz regions50 fieldsMost HD broadcast channels
1080i29.97 (59.94i)North America, 60 Hz regions59.94 fieldsHD broadcast channels
720p50 / 1080p5050 Hz regions50 framesSport, high-motion channels
1080p2550 Hz regions25 framesFilm, drama, documentaries
23.976p / 24pWorldwide~24 framesCinema-originated content

The fractional rates — 29.97 and 59.94 — are a legacy of colour television in 60 Hz regions and are still standard there today.

Film content and telecine

Films are shot at around 24 frames per second. To show them on interlaced television, frames are distributed across fields. In 50 Hz regions this is usually done by speeding film up slightly to 25 fps and splitting each frame into two fields. In 60 Hz regions, the 3:2 pulldown pattern alternates between three and two fields per film frame.

Content prepared this way is not truly interlaced in motion — both fields of a frame often come from the same film frame. Applying heavy deinterlacing to such content wastes processing and can soften the picture; detecting and reversing the pattern (inverse telecine) is the higher-quality option, though it adds complexity.

Why streaming needs progressive video

Smart TVs, phones, tablets and browsers all display progressive frames. If a channel is delivered interlaced, each player has to deinterlace on its own — and quality varies enormously between devices. Some do it well; others simply show combing, or drop one field and halve vertical resolution.

Encoders also benefit: progressive frames compress more predictably for streaming, and many efficient encoding settings assume progressive input. Deinterlacing once, centrally, before encoding means every subscriber sees the same clean result regardless of their device.

Deinterlacing methods and their cost

  • Weave simply combines two fields into one frame. Perfect for static images and telecined film, but produces combing on motion.
  • Bob turns each field into its own frame by interpolating the missing lines. Motion stays smooth — 50 fields become 50 frames — at some loss of vertical detail.
  • Motion-adaptive deinterlacers, a family that includes widely used open-source filters, weave where the picture is still and interpolate where it moves, often using neighbouring fields to decide. They give the best balance of sharpness and smoothness for live broadcast.

The trade-off is processing power. Motion-adaptive deinterlacing of a 1080i channel costs significantly more CPU than passing the stream through, and it requires decoding and re-encoding the video. That is why it should be a per-channel decision: apply it to interlaced channels that need it, and keep progressive channels on passthrough.

50p or 25p output?

When deinterlacing 50i, outputting one frame per field (50p) preserves the fluid motion of the original — important for sport and live events. Outputting 25p halves the frame rate and the encoding load, which is acceptable for film and studio content but makes fast motion look less smooth. The right choice depends on the channel, not on a global setting.

Monitoring real frame rate and speed

A transcoding process can be "running" while delivering 18 frames per second instead of 25, or processing at 0.9× real time and slowly falling behind. Neither is visible from a simple up/down status. Useful monitoring reports the actual output frame rate and the processing speed relative to real time for every channel. A speed persistently below 1.0× means the server cannot keep up — usually a sign that a channel needs passthrough instead of processing, or that the load must be rebalanced across servers.

How SaurusRex handles it: deinterlacing and custom track mapping are configured per channel, so interlaced feeds can be processed while progressive channels stay on passthrough. Stream info shows each channel's codec, resolution, real frame rate and processing speed, and health checks catch frame-rate drops and speed loss with automatic restarts. Explore the platform.

Let's talk

See SaurusRex running on your own network.

Tell us about your channels, sites and subscribers. We'll walk you through a live demo and propose an architecture that fits.