HLS & DASH Stream Tester

Paste an .m3u8 or .mpd address to play the stream, see what's inside and find out why it doesn't play in a browser.

How to test a stream

  1. Paste the address

    Copy the .m3u8 (HLS) or .mpd (DASH) address from your streaming server, CDN or encoder, and click Test stream.

  2. Read the result

    The stream plays in Fluid Player. Below it: quality levels, codecs, live or on-demand, and a check of every request, with what to fix in plain words.

  3. Embed it on your site

    Once it plays, copy the code under the tester to show the stream on your own page with Fluid Player.

Fix CORS on your server

A web player downloads the playlists, segments and keys with JavaScript, so the browser only hands them over if the server says your site may read them. That’s the Access-Control-Allow-Origin header. VLC and other apps don’t check it, which is why a stream can work there and fail in a browser.

nginx
location ~* \.(m3u8|mpd|ts|m4s|mp4|m4a|aac|vtt|key)$ {
    add_header Access-Control-Allow-Origin "*" always;
    add_header Access-Control-Allow-Methods "GET, HEAD, OPTIONS" always;
    add_header Access-Control-Allow-Headers "Range" always;
    add_header Access-Control-Expose-Headers "Content-Length, Content-Range" always;
    if ($request_method = OPTIONS) {
        return 204;
    }
}

An add_header inside a location block replaces the ones set above it: repeat your other headers (HSTS…) in this block if you have any.

Apache
# .htaccess or virtual host (needs mod_headers)
<FilesMatch "\.(m3u8|mpd|ts|m4s|mp4|m4a|aac|vtt|key)$">
    Header always set Access-Control-Allow-Origin "*"
    Header always set Access-Control-Allow-Headers "Range"
    Header always set Access-Control-Expose-Headers "Content-Length, Content-Range"
</FilesMatch>

Turn on the module with a2enmod headers if the header doesn’t show up.

Amazon S3
[
  {
    "AllowedOrigins": ["*"],
    "AllowedMethods": ["GET", "HEAD"],
    "AllowedHeaders": ["Range"],
    "ExposeHeaders": ["Content-Length", "Content-Range"],
    "MaxAgeSeconds": 3600
  }
]

In the S3 console: your bucket → Permissions → Cross-origin resource sharing (CORS) → Edit, then paste this.

  • Amazon CloudFront: in the cache behavior of your stream, attach the managed response headers policy CORS-With-Preflight (or SimpleCORS). With an S3 origin, also attach the origin request policy CORS-S3Origin.
  • Cloudflare: add a Response Header Transform Rule that sets Access-Control-Allow-Origin for your stream’s path. Purge the cache afterwards: cached files keep their old headers.
  • Any CDN: the header has to be on every file, not only the playlist. Test again here after a cache purge: the Requests list shows each file type.

Replace * with your site’s address (https://www.example.com) to allow only your site. * is fine for public streams. The Range and Content-Range lines are needed by players that download parts of a file.

Stream not playing?

  • Every file of the stream sends Access-Control-Allow-Origin: playlists, segments and keys.
  • Everything is on https://, including the addresses inside the playlist.
  • There’s an H.264 (avc1) quality level: HEVC and AV1 don’t play in every browser.
  • The playlist declares CODECS and RESOLUTION for each level.
  • For a live stream, the encoder is broadcasting right now.
  • The stream isn’t DRM-protected (Widevine, PlayReady, FairPlay): DRM needs a license server.

Questions

Is my stream address sent to you?

No. The tester runs in your browser: it downloads the playlist and segments straight from the stream’s server, as a player on your site would. Nothing goes through our servers and nothing is stored. A share link keeps the address after a #, a part of the link that browsers never send to a server.

Why does my stream play in VLC but not in the browser?

Most often, CORS. A web player downloads the stream with JavaScript, and the browser blocks the answer unless the server sends an Access-Control-Allow-Origin header. VLC doesn’t check it. Other causes: an http:// address on an https:// page, or a codec the browser can’t play (HEVC in Chrome on some systems, for example). The tester shows which one it is.

Why does it play in Safari or Chrome but not in Firefox?

Safari, and Chrome since version 142 (late 2025), play HLS by themselves, like an MP4 file, so they don’t need CORS headers. Firefox and older versions of Chrome play HLS through a JavaScript library (hls.js), which does, and every browser needs one for DASH. So a stream without CORS headers can play in Safari and Chrome and fail elsewhere. Add the headers, and it plays everywhere. This tester always uses hls.js, the strictest path, so a stream that passes here plays in every browser.

Can I test an http:// stream?

Not as such: browsers block http:// files on https:// pages (mixed content), so such a stream can’t play on any secure website either. The tester tries the https:// version of the address instead. If that one fails too, serve the stream over https://: most CDNs and streaming servers do it for free.

Does it work with signed or token URLs?

Yes, if the token is in the address (?token=…, signed URLs). Streams protected by cookies or a login don’t play: the tester, like most web players, sends no cookies to other sites. A token that expires quickly may have expired by the time you test it.

Can I test DRM-protected streams?

Not the playback: DRM (Widevine, PlayReady, FairPlay) needs a license server and keys from the stream owner. The tester detects DRM and still shows the quality levels, codecs and requests. AES-128 encryption isn’t DRM: those streams play.

Does it test live streams?

Yes, HLS and DASH. It shows whether the stream is live, how far behind the live edge you are, and warns about common live problems, such as a playlist with too few segments or a DASH manifest without a time source.

How do I put the stream on my website?

Copy the code under the tester: Fluid Player plays HLS and DASH on its own. See HLS (opens in a new tab) and DASH (opens in a new tab) in the Fluid Player documentation for the options.

More free tools

  • SRT to VTT Converter

    Convert SRT subtitles to WebVTT for HTML5 video. Fixes broken accents, checks for errors and previews the result in Fluid Player.

  • VTT to SRT Converter

    Convert WebVTT subtitles to SRT for YouTube, video editors and media players. Keeps positions, checks for errors and previews the result.

  • Player Builder

    Set up Fluid Player visually, with video ads, subtitles and your colors, and copy ready-to-use code.