Skip to main content
All posts

Why Your M3U8 Won't Play or Convert: Common Errors and Fixes

Expired links, 403 errors, CORS, encryption, and broken segments are the usual reasons an M3U8 fails. Here is how to recognize and fix each one.

Troubleshooting

You found the M3U8 URL, pasted it into a converter or FFmpeg, and got an error instead of a video. Most failures come from a handful of causes. This guide explains how to recognize each one and what you can do about it.

Symptoms: 403 Forbidden or 404 Not Found, even though the video still plays on the original page.

Many sites add a signed token to the URL, for example index.m3u8?token=abc&expires=1731800000. The token is only valid for a few minutes or hours.

Fix: reload the original page, start playback again, and copy a fresh M3U8 URL. Convert it right away.

2. The server requires headers or cookies

Symptoms: 403 Forbidden from the start, while the page plays fine in your browser.

Some servers only answer requests that include a matching Referer, Origin, User-Agent, or login cookie.

Fix: with FFmpeg, pass the headers explicitly:

bash
ffmpeg -headers "Referer: https://example.com/" -i "https://example.com/index.m3u8" -c copy output.mp4

If the video requires a logged-in account, make sure you are allowed to download it before trying to work around the restriction.

3. Cross-origin (CORS) is blocked

Symptoms: browser-based tools report a network or CORS error, while FFmpeg works.

Browsers enforce CORS: a page can only read another site's files if that site allows it. Many video CDNs only allow their own website.

Fix: use a tool that does not run inside the browser page, such as FFmpeg or VLC, or a converter that processes the stream on its own server.

4. The stream is encrypted

Symptoms: the M3U8 file contains #EXT-X-KEY, and the output plays as noise or not at all.

HLS supports two very different kinds of protection:

  • AES-128 encryption with a key URL in the M3U8 file, for example #EXT-X-KEY:METHOD=AES-128,URI="key.bin". If the key URL is accessible, FFmpeg decrypts the segments automatically.
  • DRM such as Widevine or FairPlay (METHOD=SAMPLE-AES with a skd:// or license server URI). DRM is designed to prevent copying, and it cannot be converted with ordinary tools.

Fix: for AES-128, make sure the key URL is reachable with the same headers as the segments. For DRM, use the service's official download or offline feature instead.

5. You used the master manifest

Symptoms: the tool downloads nothing, or picks a quality you did not want.

A master manifest only lists other manifests, marked with #EXT-X-STREAM-INF.

Fix: open the master manifest, choose the variant with the resolution you want, and use that media manifest URL directly. With FFmpeg, you can also select a stream with -map 0:p:0 (the first program).

6. Missing or broken segments

Symptoms: the conversion stops partway, or the MP4 has gaps, frozen frames, or audio out of sync.

Individual segments can fail because of an unstable connection or a server error.

Fix: retry the conversion on a stable network. With FFmpeg, adding -reconnect 1 -reconnect_streamed 1 -reconnect_delay_max 5 before -i helps it recover from short interruptions.

7. The MP4 has no sound or will not open

Symptoms: video plays without audio, or some players refuse to open the file.

HLS often stores AAC audio in a format that is not valid inside MP4.

Fix: with FFmpeg, add -bsf:a aac_adtstoasc. If the source uses an audio codec MP4 does not support, re-encode only the audio with -c:v copy -c:a aac.

Quick checklist

  • Copy a fresh URL and convert immediately.
  • Use the media manifest for the quality you want.
  • Check for #EXT-X-KEY and know whether it is AES-128 or DRM.
  • Add the headers the site expects.
  • Retry on a stable connection.

Still stuck? Email us at support@m3u8tomp4.com with the error message you saw. For background on how HLS works, read What Is M3U8?, and for conversion options see 4 ways to convert M3U8 to MP4.