Quick Answer: Converting HDMI to IPTV takes three parts: an encoder that compresses the HDMI input to H.264 or H.265, a packetiser that wraps the elementary stream in MPEG-TS over UDP, and a network that delivers the multicast group to every viewer. A 1080p60 channel runs 6 to 10 Mbps in H.264; 2160p60 in H.265 runs 25 to 40 Mbps. Glass-to-glass latency lands at 1.5 to 4 seconds, and the switch settings decide whether it works at all. Size the network for the sum of every channel, not for one: ten 10 Mbps streams need 100 Mbps of trunk capacity plus headroom. Budget one encoder input per source and one decoder per screen.
HDMI is 18 Gbps of uncompressed video on four lanes and no network switch will route it. The encoder is the boundary between the two worlds: it terminates HDMI, compresses each frame and emits UDP packets addressed to a multicast group. Everything downstream, from bitrate to packet loss, follows from how that encoder is configured and how the switch handles the group.
The Chain: HDMI In, MPEG-TS Out
Capture and encode
The encoder locks to the incoming pixel clock and pushes frames into an H.264 or H.265 core. H.264 High profile at 1080p60 needs 6 to 10 Mbps to hold up on sport; H.265 Main10 reaches similar quality at roughly 40 to 50 percent of that bitrate, at the cost of more compute per stream and pickier decoders.
Packetise and publish
The elementary stream is wrapped in MPEG-TS, then RTP and UDP, and sent to a group such as 239.1.1.10 on port 1234. Multicast is the default because unicast needs one copy per viewer. Some units also publish RTMP or SRT to a CDN, which is convenient but adds a second of buffering.
A point-to-point extender is a different product: a passive HDMI to Ethernet adapter carries one stream to one receiver and never puts a routable packet on the LAN.
Bitrate: The Numbers That Matter
Pick the bitrate from the content, not from the label on the encoder. A static slide deck survives 3 Mbps at 1080p30; a football match at the same setting turns grass into smear. A 4K HDMI IPTV encoder that cannot sustain 40 Mbps per stream will drop frames the moment a second channel starts.
| Format | Codec profile | Typical bitrate | LAN note |
|---|
| 1080p30 | H.264 High | 3 to 5 Mbps | comfortable on Cat5e |
| 1080p60 | H.264 High | 6 to 10 Mbps | use for sport and motion |
| 1080p60 | H.265 Main | 4 to 6 Mbps | decoder support varies |
| 2160p30 | H.265 Main10 | 15 to 25 Mbps | Cat6 and gigabit ports |
| 2160p60 | H.265 Main10 | 25 to 40 Mbps | check switch backplane |
Multicast, IGMP and Switch Settings
IGMP snooping
Without IGMP snooping a switch floods every multicast frame to every port, so a 10 Mbps channel eats 10 Mbps on all 24 ports. Enable snooping, enable a querier, then read the group table to confirm the join. A missing querier is the usual reason a stream works for one viewer and dies when a second one connects.
VLAN and frame size
Give video its own VLAN so a broadcast storm in the office cannot starve it. Jumbo frames help only when every hop, decoder included, uses the same MTU; one mismatch produces silent loss on fragmented packets that looks exactly like a weak signal.
If only one screen needs the feed, HDMI over Ethernet is simpler and cheaper than standing up multicast, an IGMP querier and a decoder fleet.
Latency: Where the Seconds Go
Encoding with B-frames costs 300 to 800 ms of reorder delay. The transport buffer adds 200 to 500 ms, the decoder holds a jitter buffer of 300 ms to 1 s, and the player adds its own. Disabling B-frames and selecting a low-delay mode gets glass-to-glass near 1.5 s on a clean LAN; below that, use uncompressed HDMI over IP rather than fighting the codec.
Practical Scenarios
- Sports bar with eight screens: one encoder, one multicast group, eight decoders. Keep every decoder on the same firmware and bitrate ladder, or channel changes will take different times on each screen.
- Church overflow room: set the encoder to low delay with no B-frames and accept 2 Mbps more bitrate for the same quality; lip sync matters more than file size on a live feed.
- Campus announcement channel: use H.265 only if every decoder is known to handle it, otherwise H.264 High profile at 1080p30 saves a week of support calls.
- Recording plus streaming: record the encoder’s local MP4 or TS file rather than capturing the multicast stream, which loses packets during switch reconfiguration.
FAQ
Do I need a managed switch for IPTV?
You need IGMP snooping and a querier, and that means a managed or smart switch. A 24-port gigabit unit with snooping enabled carries twenty 10 Mbps channels without strain. Unmanaged switches work for one viewer because flooding is harmless with one port, then collapse at three.
Can I convert HDMI to IPTV without an encoder?
No. IPTV means an IP packet stream, and only an encoder produces one. Cheap HDMI-to-USB capture sticks can act as the capture stage on a small PC running ffmpeg, but the compression step still exists; there is no passive adapter that turns HDMI into a multicast stream.
Why does the stream freeze every few minutes?
Usually a decoder jitter buffer set too tight against a bursty switch, or IGMP group membership timing out because no querier answers. Check the decoder’s buffer setting first, then the group table during playback, then whether the uplink between switches is saturated by the same streams.
