An IPTV encoder is a hardware device or software application that takes a video source (for example an HDMI or SDI signal from a camera, media player or receiver), compresses it with a codec such as H.264 or H.265 and sends it out as a stream over an IP network. It is the first step in any IPTV system: without encoding, a video signal is far too large to send over a network. This guide explains what an IPTV encoder does, how it works, the specifications that matter and where it sits in a complete IPTV workflow.
This is a technical guide for people building or managing IPTV systems, such as hotels, offices, schools, venues and churches. If you just want to watch TV over the internet, you don't need an encoder; see what is IPTV.
Quick answer
An IPTV encoder converts video into a compressed network stream. You connect a source to its input, choose a codec, resolution and bitrate, and it outputs a stream (often MPEG-TS over UDP multicast, or RTMP, SRT or HLS) that set-top boxes, smart TVs, players or a streaming server can receive.
What does an IPTV encoder do?
An encoder performs four jobs:
- Capture: receives the raw video and audio from an input such as HDMI, SDI or composite.
- Compress: reduces the data rate with a video codec (H.264/AVC, H.265/HEVC) and an audio codec (usually AAC).
- Package: wraps audio and video into a container such as MPEG transport stream (MPEG-TS).
- Transmit: sends the stream over IP using a protocol such as UDP, RTP, RTSP, RTMP, SRT or HLS.
Uncompressed 1080p60 video is roughly 3 Gbps. A good encoder brings that down to around 4–8 Mbps with H.264 while keeping the picture watchable on a large TV.
Encoding vs transcoding
| Encoding | Transcoding | |
|---|---|---|
| Input | Uncompressed signal (HDMI, SDI) | An existing compressed stream or file |
| Output | Compressed stream | A stream in another codec, bitrate or resolution |
| Typical use | Turning a live source into IPTV | Creating lower-bitrate versions for phones, or converting H.264 to H.265 |
| Equipment | Hardware encoder or capture card plus software | Server software or dedicated transcoders |
Many professional systems use both: an encoder creates a high-quality stream, and a transcoder makes extra versions for different devices and connection speeds (adaptive bitrate).
How does an IPTV encoder work?
The signal chain
Source → encoder → network → (optional streaming server or middleware) → decoder (set-top box, smart TV, app) → screen
Key settings
| Setting | What it controls | Typical values |
|---|---|---|
| Codec | Compression efficiency and compatibility | H.264, H.265 |
| Resolution | Picture size | 720p, 1080p, 2160p (4K) |
| Frame rate | Smoothness | 25/30 or 50/60 fps |
| Bitrate | Data per second; quality vs bandwidth | 2–8 Mbps HD, 12–25 Mbps 4K HEVC |
| Rate control | Constant (CBR) or variable (VBR) bitrate | CBR for multicast networks |
| GOP / keyframe interval | How often full frames are sent | 1–2 seconds |
| Audio | Codec and bitrate | AAC, 128–256 kbps |
Bitrate and quality
The bitrate is the most important quality setting. Fast motion (sport) needs more bitrate than talking heads (news). Too little bitrate causes blockiness; too much wastes bandwidth and can overload Wi-Fi clients.
Latency
Latency is the delay between the source and the screen. Hardware encoders can encode with very low delay, but the protocol often adds more: UDP multicast on a local network can be well under a second end to end, while HLS typically adds several seconds because it delivers video in segments.
Hardware vs software encoders
| Hardware encoder | Software encoder | |
|---|---|---|
| Form | Dedicated box or rack unit | Application on a computer (e.g. OBS Studio, FFmpeg) |
| Reliability | Built for 24/7 operation | Depends on the computer and operating system |
| Latency | Usually low and consistent | Varies with settings and hardware |
| Flexibility | Fixed feature set | Highly configurable |
| Cost | Higher per channel | Low software cost, but needs a capable computer |
| Best for | Permanent channels, hotels, venues | Events, testing, small productions |
See IPTV encoders compared for a buyer's comparison.
Streaming protocols
| Protocol | Typical use | Latency |
|---|---|---|
| UDP / RTP multicast (MPEG-TS) | Local IPTV networks (hotels, campuses) | Very low |
| RTSP | Cameras and some players | Low |
| RTMP | Sending to streaming servers and platforms | Low to moderate |
| SRT | Reliable contribution over the internet | Low, configurable |
| HLS / DASH | Delivery to apps and browsers at scale | Several seconds |
Where encoders sit in an IPTV system
A typical in-building IPTV system includes:
- Sources: satellite or terrestrial receivers (with the right licences), cameras, media players, digital signage.
- Encoders: one channel per input, or multi-channel units.
- Network: managed switches with IGMP snooping for multicast.
- Middleware: channel lists, guides and menus (for example in hotels).
- Receivers: set-top boxes, smart TVs or apps.
See IPTV professional systems.
What should you consider when choosing one?
- Inputs: HDMI, SDI or both; number of channels.
- Codecs: H.264 for compatibility; H.265 for 4K and bandwidth savings.
- Outputs and protocols: must match your receivers and servers.
- Management: web interface, SNMP or API for monitoring.
- Reliability: power supply, cooling and 24/7 rating.
- Content protection and rights: you need the right to distribute what you encode. HDCP-protected HDMI sources (many consumer set-top boxes and Blu-ray players) are designed not to be captured, and compliant encoders won't capture them.
Common mistakes
- Setting VBR on a multicast network with tight bandwidth.
- Using H.265 when some TVs can't decode it.
- Forgetting IGMP snooping, which floods the network with multicast traffic.
- Using a very long keyframe interval, which slows channel changes.
Conclusion
An IPTV encoder converts video sources into compressed IP streams and is the starting point of every IPTV system. Choose the codec for your receivers, set the bitrate for your content and network, pick the protocol for your delivery method and decide between hardware for permanent channels and software for flexible use. And make sure you have the rights to distribute what you encode.