HLS codec compatibility explained

Container and codec are different

MP4, MOV, and WebM are containers. H.264, VP9, AV1, AAC, Opus, and MP3 are codecs carried inside them. A filename extension alone cannot fully predict processing cost or device support.

Two .mov files can require different paths because their internal video and audio formats differ.

Repackage or transcode

Repackaging copies compatible compressed streams into a new delivery structure and is usually faster. Transcoding decodes and encodes the media, which takes more time and can introduce generational loss.

Standard mode attempts a compatible stream copy first and falls back when necessary. Master mode creates a 720p H.264/AAC video rendition; MP3 input becomes AAC audio HLS.

Repackage: compressed input -> HLS segments
Transcode:  compressed input -> decoded media -> H.264/AAC -> HLS segments

Compatibility is end to end

The playlist, segment container, video codec, audio codec, profile, level, resolution, and target device all affect playback. A valid M3U8 file can still reference media that one browser cannot decode.

Test the actual package on representative devices rather than relying only on a successful conversion message.

Choose a practical source

For predictable browser work, start with a lawful, healthy source at the resolution and duration you need. Avoid repeated lossy transcodes and retain the best available original.

If exact production profiles, encryption, subtitles, or a multi-rendition ladder are required, use a controlled professional encoding pipeline and validate against the target platform specification.

Technical references

Primary documentation used to review this guide:

• Apple: HLS Authoring Specification for Apple Devices