What is M3U8?
M3U8 is the UTF-8 form of the M3U multimedia playlist format and is widely used for HTTP Live Streaming manifests. Its text entries can describe variants, segments, keys, and timed metadata.
How M3U8 works
An M3U8 document is a line-oriented UTF-8 playlist whose directives begin with a hash and whose other lines generally identify media resources. In HLS, a multivariant playlist advertises alternative renditions, while a media playlist enumerates playable segments for one rendition. Clients repeatedly reload live playlists and choose resources according to bandwidth, codecs, and playback state. Packagers produce these manifests after encoding and segmenting the media.
Key facts
- 1An HLS playlist begins with the EXTM3U marker. Tags such as EXTINF affect the URI that follows, so changing line order can alter meaning even though the file remains valid text.
- 2A multivariant playlist points to other playlists and describes selectable streams; a media playlist instead supplies the ordered segment sequence consumed during playback.
- 3Relative segment and key URIs are resolved against the playlist URL. Moving or signing a manifest without preserving that base relationship can produce authorization failures or broken requests.
When M3U8 matters
Manifest generators must emit valid ordering, durations, URLs, and tags for the intended HLS clients. Unsafe handling of untrusted playlists can expose parsers to malicious paths or unsupported schemes.
Common use cases for file formats & compression
These examples cover file formats & compression broadly, not specifically M3U8.
- Accepting heterogeneous uploads while producing a controlled set of delivery formats.
- Moving assets between cameras, editors, browsers, archives, and downstream APIs.
- Separating long-lived source files from compact derivatives optimized for a particular channel.
Working with file formats & compression
This guidance covers file formats & compression broadly, not just M3U8.
A parser reads the file structure, identifies contained streams and metadata, and exposes them to a decoder or application. Conversion usually decodes the source representation and writes compatible information into a different structure or encoding.
This category covers file and bitstream formats, their structures, and the compression methods they use. A filename extension can be misleading, so evaluate the detected format, decoding support, metadata, transparency, color, timing, patents, and archival needs before choosing an output.
What you gain
- A suitable format preserves the properties a workflow actually needs.
- Standardized structures allow files to move between compatible tools and systems.
- Format conversion can improve delivery size, editability, or long-term accessibility.
What it costs
- Modern formats can save bandwidth but may need fallbacks for older clients and production tools.
- Converting to a simpler format can discard transparency, animation, metadata, color precision, or editability.
- Archival suitability, browser support, and editing support often favor different choices.
Before production
- 1Inspect the detected container, codec, MIME type, and magic bytes instead of trusting a suffix.
- 2Verify decoder support and preserve metadata, color, transparency, or timing when required.
- 3Retain the source when the chosen delivery format is lossy or tied to current software.