A 4K IPTV encoder captures an ultra-high-definition signal (3840×2160) and compresses it, usually with H.265/HEVC, into a stream small enough for an IP network. Compared with HD encoding it needs faster inputs (HDMI 2.0 or 12G-SDI), more processing power, 10-bit support for HDR and careful bandwidth planning, because a single 4K channel can use as much bandwidth as several HD channels. This guide covers the specific requirements for encoding 4K for IPTV.
For general encoder basics, see IPTV encoder explained. If you're a viewer interested in 4K channels rather than equipment, see 4K IPTV.
Quick answer
For 4K IPTV, choose an encoder with an HDMI 2.0 or 12G-SDI input, hardware HEVC encoding, 10-bit/HDR support if you need HDR, and outputs your receivers accept. Plan around 12–25 Mbps per 4K HEVC channel and test on your actual TVs and set-top boxes.
What makes 4K encoding different?
| 1080p HD | 4K UHD | |
|---|---|---|
| Pixels per frame | ~2.1 million | ~8.3 million |
| Typical codec | H.264 | H.265 (HEVC) |
| Typical bitrate | 4–8 Mbps (H.264) | 12–25 Mbps (HEVC) |
| Input | HDMI 1.4 / 3G-SDI | HDMI 2.0+ / 12G-SDI |
| Colour | 8-bit SDR common | 10-bit for HDR |
| Processing | Moderate | High |
Four times the pixels means four times the raw data, so efficient compression matters much more.
Codecs for 4K
- H.265 (HEVC): the standard choice for 4K IPTV; roughly half the bitrate of H.264 for similar quality, and supports 10-bit and HDR.
- H.264: can do 4K, but at a much higher bitrate and with limited HDR use.
- AV1: efficient and royalty-free; support in encoders and receivers is growing.
HDR: what the encoder must support
| HDR format | Notes |
|---|---|
| HDR10 | Widely supported; static metadata |
| HLG | Designed for broadcast; backwards-compatible with SDR TVs |
| Dolby Vision / HDR10+ | Dynamic metadata; requires specific support end to end |
For HDR you need 10-bit encoding (HEVC Main10), correct colour metadata passed through, and receivers that support the same HDR format.
Bitrate settings for 4K
| Content | Suggested HEVC bitrate (2160p50/60) |
|---|---|
| Static content, signage, presentations | 8–12 Mbps |
| General TV, entertainment | 12–18 Mbps |
| Fast sport | 18–25 Mbps or more |
Use CBR on tightly managed multicast networks and test visually: watch fast motion, gradients and dark scenes for blocking and banding.
Network planning
- Per channel: 12–25 Mbps.
- Multicast: bandwidth is used on each link where the channel is being watched.
- Wi-Fi clients: 4K multicast over Wi-Fi is often unreliable; use wired connections for 4K receivers where possible.
- Headroom: keep at least 30% spare capacity on uplinks.
| Example | Channels | Bitrate | Total |
|---|---|---|---|
| Venue with 4K feeds | 4 | 20 Mbps | 80 Mbps |
| Hotel mixed line-up | 6 × 4K + 40 × HD | 18 / 5 Mbps | 308 Mbps |
Receiver compatibility checklist
- Does the TV or set-top box decode HEVC Main10?
- Does it support the protocol (UDP multicast, HLS)?
- Does it support the HDR format you're sending?
- Does it handle 50/60 fps 4K?
- Is its network port fast enough (100 Mbps can be tight with several streams)?
Latency at 4K
4K encoding takes more processing, and HEVC uses more complex prediction, which can add latency. Low-latency presets, shorter GOPs and avoiding B-frames reduce delay at the cost of some efficiency.
Choosing a 4K IPTV encoder
| Feature | Recommended |
|---|---|
| Input | HDMI 2.0 or later, or 12G-SDI |
| Encoding | Hardware HEVC, 10-bit |
| HDR | HDR10 and HLG pass-through |
| Outputs | UDP/RTP multicast, SRT, RTMP, HLS as needed |
| Management | Web UI, API, alarms |
| Cooling | Adequate for continuous operation |
Content rights and HDCP
Many 4K consumer sources use HDCP 2.2 copy protection, and compliant encoders won't capture them. Use sources you're licensed to distribute, such as your own cameras, signage players or properly licensed feeds.
Conclusion
A 4K IPTV encoder needs a fast input, hardware HEVC, 10-bit/HDR support and enough processing to run continuously. Plan 12–25 Mbps per channel, wire 4K receivers where possible, confirm every receiver can decode your format and test with demanding content before going live.