Guides

IPTV Encoders Explained: HDMI, 4K and How to Choose One

By the Sphere IPTV team · Updated

An IPTV encoder is a device or program that takes a video signal — usually HDMI or SDI from a camera, player or receiver — compresses it with a codec such as H.264 or H.265, and sends it over an IP network as a stream that players, set-top boxes or a streaming server can receive. Viewers do not need one: encoders are for people who produce or distribute a stream, such as hotels, venues, churches, schools or broadcasters.

At a glance

IPTV Encoders Explained: HDMI, 4K and How to Choose One: key facts
JobCompress live video and send it over an IP network
Typical inputHDMI (consumer/pro AV) or SDI (broadcast)
Common codecsH.264/AVC for compatibility, H.265/HEVC for efficiency
Common outputsUDP/RTP multicast, RTMP, SRT, HLS, RTSP
Who needs oneStream producers and distributors — not viewers
Illustration of an HDMI cable feeding an encoder box that sends a stream to a network

What an IPTV encoder does

Uncompressed 1080p video runs at roughly 3 Gbit/s, far more than a normal network or internet connection can carry. An encoder solves this in three steps: it captures the incoming signal, compresses it with a video codec (and audio with a codec such as AAC), and packages the result into a network protocol so other devices can receive it.

The output might feed a hotel's in-room TV system, a streaming platform via RTMP, or a server that redistributes the stream. The principle is the same for a small HDMI box, a rack unit or software.

Encoding vs transcoding

Encoding starts from a raw signal (HDMI, SDI or a camera sensor) and produces the first compressed version. Transcoding starts from a stream that is already compressed and converts it — to a different codec, resolution or bitrate — usually on a server.

A typical workflow uses both: one high-quality encode at the source, then a transcoder creates lower-bitrate versions (an “adaptive bitrate ladder”) so viewers on slow connections still get a picture. Every transcode loses a little quality, so encode once at the best quality your upload allows.

HDMI input, video formats and HDCP

An HDMI encoder for IPTV should list exactly which input formats it accepts. Check:

  • Resolution and frame rate — for example 1080p50/60 or 2160p60. A source sending a format the encoder doesn't support gives a black screen.
  • Loop-out — an HDMI output that passes the signal through, so you can monitor locally.
  • Audio — embedded HDMI audio, and whether there is a separate analogue input.
  • HDCP — copy protection used by many set-top boxes, Blu-ray players and streaming sticks. Encoders built for legitimate use generally won't encode an HDCP-protected signal, and circumventing it can breach copyright law. An encoder is a tool for content you have the right to distribute, not a way to re-broadcast someone else's channels.

Resolution, frame rate, bitrate and latency

Bitrate is the amount of data per second the encoder produces. Too low and fast motion turns blocky; too high and the network can't keep up. The ranges below are common starting points, not specifications — test with your own content, because sport needs more bitrate than a static presentation.

Starting bitrates for live encoding
OutputH.264 starting rangeH.265 starting range
720p at 30 fps2.5–4 Mbit/s1.5–3 Mbit/s
1080p at 30 fps4–6 Mbit/s2.5–4 Mbit/s
1080p at 50/60 fps6–10 Mbit/s4–7 Mbit/s
2160p (4K) at 50/60 fpsRarely practical15–35 Mbit/s

Latency is the delay between the live event and the viewer. Encoder settings such as GOP (keyframe interval), B-frames and buffer size affect it, but the delivery method matters more: local multicast and SRT can stay under a second or two, while standard HLS often adds tens of seconds because players buffer several segments.

H.264 vs H.265 compatibility

H.264 (AVC) plays almost everywhere: browsers, phones, smart TVs and old set-top boxes. H.265 (HEVC) needs roughly half the bitrate for similar quality, which is why 4K streams use it, but older devices and some browsers can't decode it. If you don't control the receiving devices, H.264 is the safer default; if you do, and they decode HEVC in hardware, H.265 saves bandwidth. Our 4K IPTV guide covers the viewer side of HEVC.

Protocols and network requirements

Common encoder output protocols
ProtocolTypical useWatch out for
UDP/RTP multicastTV distribution inside a building or campusSwitches need IGMP snooping or the stream floods every port
RTMPSending to YouTube, social platforms or a media serverIngest only; not used for playback to viewers
SRTReliable contribution over the public internetBoth ends must support it; set latency to suit the link
HLSDelivery to many viewers over HTTPHigher latency; usually produced by a server, not the encoder

Use wired Ethernet for the encoder, and keep upload bandwidth at least 1.5 times the total bitrate you send. Assign a fixed IP address so the stream address doesn't change after a reboot.

Hardware encoder vs software encoding

Software such as OBS Studio or FFmpeg can encode on a computer using the processor or graphics card. It is flexible and inexpensive, and suits productions that add graphics or switch between sources. A hardware encoder is a dedicated box: it starts on power-up, runs unattended for months and doesn't depend on a computer's updates. Fixed installations — a channel in a hotel or a permanent camera — usually favour hardware; occasional productions often start with software.

Choosing a 4K IPTV encoder

Read the specification carefully. Some products accept a 4K HDMI input but only output 1080p — useful when the source is 4K, but not a 4K stream. A true 4K IPTV encoder should state 2160p output, H.265 support, the frame rates it encodes at that resolution and the maximum bitrate. Confirm that the receiving devices decode HEVC at 4K and that the network can carry the bitrate for every simultaneous stream.

Common configuration mistakes

  • Bitrate set higher than the available upload, causing dropped frames.
  • Multicast enabled on a network without IGMP snooping, slowing the whole network.
  • Keyframe interval too long, so players take seconds to start or recover.
  • Input set to a fixed format that doesn't match the source's output.
  • Default admin password left unchanged on a device reachable from the internet.

Sphere IPTV doesn't sell encoders or broadcast hardware. If you want to watch IPTV rather than produce it, you need a player and a service — see what IPTV is and our device guides.

Frequently asked questions

Do I need an IPTV encoder to watch IPTV?

No. Viewers need a player app or set-top box and a service. Encoders are used by whoever creates and distributes the stream.

What is the difference between an HDMI encoder and an IPTV encoder?

Usually none: an HDMI encoder for IPTV is an IPTV encoder with HDMI inputs. Encoders for broadcast facilities often use SDI inputs instead.

Can an encoder stream to several destinations at once?

Many can output two or more streams at the same time, for example multicast on the local network plus RTMP to a platform. Check the model's specification for the number of simultaneous outputs.

Is H.265 always better than H.264?

It is more efficient, but not always better in practice. If some receiving devices can't decode H.265, H.264 is the right choice.

Sources

  1. H.264: Advanced video coding for generic audiovisual services — ITU-T (accessed )
  2. H.265: High efficiency video coding — ITU-T (accessed )
  3. RFC 8216: HTTP Live Streaming — IETF (accessed )
  4. RFC 4541: Considerations for IGMP and MLD Snooping Switches — IETF (accessed )
  5. Secure Reliable Transport (SRT) — SRT Alliance (accessed )
  6. HDCP specifications — Digital Content Protection, LLC (accessed )

Try Sphere IPTV on your device

Plans from $20 for 1 month to $75 for 12 months. Order on WhatsApp and get setup help.