Codec and container: why a file extension is not enough
A container packages tracks; a codec describes how a track is encoded. Recognising an MP4 or MKV filename does not tell you every video and audio format inside it.
When one file opens on a computer but fails on a television, compare the track details rather than renaming the extension. A supported video codec can still be paired with an unsupported audio track. The useful result is a list of actual formats that can be compared with the chosen device and player documentation.
A practical check
- Read the media information in your player
- Note video codec and audio codec separately
- Keep the original file unchanged
Related: audio codec · browser source support
What video decoding does during playback
Decoding turns an encoded video stream into frames a screen can display. Opening a playlist and successfully decoding its picture are separate stages.
A player may retrieve channel names before it encounters a video format it cannot handle. That is why a working menu does not settle a playback complaint. Record whether audio starts, whether the frame freezes and whether the same source behaves differently in another genuinely supported setup.
A practical check
- Separate menu loading from video playback
- Record whether audio works
- Look up the exact device and player capabilities
Related: media capability testing
Why compressed video can lose fine detail
Compression reduces the data needed to represent a picture. With lossy encoding, some original information is discarded rather than stored exactly.
Fast movement, fine textures and difficult lighting can make compression artefacts easier to notice. Increasing a television's sharpness control does not recover source detail that was removed. Use the same scene when comparing alternatives so that motion and camera cuts do not change the test halfway through.
A practical check
- Choose a repeatable scene
- Compare the actual source options
- Avoid treating display sharpness as restored source detail
Related: upscaling
Why codec profile and level matter
A codec name is only part of a format description. Profiles and levels describe additional encoding features and constraints that can affect playback support.
A statement that a device supports a codec should not be expanded into a promise that every possible stream using that codec will work. Keep the exact model, software version and media details together. For a viewer, the aim is a supported playback route rather than changing advanced decoder options at random.
A practical check
- Record the full media description
- Use the exact model documentation
- Avoid assuming every profile is supported
Hardware decoding and smooth playback
Some devices can decode particular media configurations using dedicated hardware. That capability is different from merely recognising the format.
Smoothness, power use and format support are separate questions. A software fallback may behave differently from a hardware path on the same device. Do not infer an actual decoder path from a logo or a large resolution label; use the manufacturer's specification and any reliable playback information the player exposes.
A practical check
- Check documented codec support
- Observe playback information if available
- Compare smoothness without changing several settings
Bitrate and resolution answer different questions
Resolution describes picture dimensions. Bitrate describes the amount of encoded data sent or stored over time.
Two streams with the same dimensions can have different picture quality and data use. A larger bitrate is not a universal quality ranking across different sources, codecs and encoding settings. Compare like with like: the same scene, the same display route and the actual available stream alternatives.
A practical check
- Read dimensions and bitrate separately
- Compare the same scene
- Record the codec and source context
Questions answered
Does changing .mkv to .mp4 convert a video?
No. Renaming an extension changes the name, not the encoded tracks or their container structure.
Can two MP4 files behave differently on the same player?
Yes. Their codecs, profiles, audio tracks or other characteristics can differ despite sharing a file extension.
Does a loading channel list prove the video format is supported?
No. The list can load before the device has decoded a programme's video.
Does a newer codec automatically mean better playback?
No. Source quality, encoding settings and the receiving device's capabilities all matter.
Can a sharpness setting recover detail removed by compression?
No. It can change how edges look, but it cannot reconstruct the original source information.
Why do fast scenes sometimes look worse than static scenes?
The encoding has to represent changing picture detail within its data budget; source and encoder choices can affect the result.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.
- https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Containers
- https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Video_codecs
- https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Formats/Audio_codecs
- https://developer.mozilla.org/en-US/docs/Web/API/WebCodecs_API/Video_processing_concepts
- https://developer.mozilla.org/en-US/docs/Web/API/Media_Capabilities_API