Media diagnostics · Primary-source explanation; no UK IPTV implementation or account test. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Read the label at its own layer
A browser diagnostic showing h3 is describing the HTTP version used for a request. RFC 9114 maps HTTP semantics over QUIC. It does not turn the response into one particular video codec. A familiar transport label cannot establish the media container, audio format, image resolution or decoder profile of the programme the viewer selected.
Follow two hypothetical requests
Consider two authorised media requests using the same HTTP version. One carries an AV1 representation and the other carries HEVC. A device can have different decoding capabilities for those two formats even though the transport indicator looks identical. Replacing the codec question with the statement that both use HTTP/3 loses the detail that could explain why one sample plays and the other does not.
Separate fallback from media support
The standard discusses QUIC connectivity and fallback to TCP-based HTTP when appropriate. A transport path changing is different from a player acquiring a new decoder. Record which request failed and whether the application subsequently obtained media through another route. Do not assume a successful homepage connection proves that every content request, entitlement step and local decoder stage also succeeded.
Build a useful comparison
Keep HTTP version, response status and media-format details in separate fields. If the question is a playback incompatibility, include the actual codec/profile and player environment where available. If it is connection establishment, preserve that narrower symptom. Neither an HTTP/3 label nor an HTTP/2 fallback establishes UK IPTV’s delivery architecture, a guaranteed latency benefit or support for a particular video format on every device.