M3U8 Player Online: Play M3U, M3U8 and HLS Playlists in Your Browser

Most playlists arrive messy. A file exported from a set-top box or a provider panel will happily carry tens of thousands of entries in an order nobody chose, a good fraction of them long dead, many of them the same channel listed four separate times under four different spellings because four different people typed it in. This player loads that file and then lets you fix it, in the same tab, without uploading a thing. No playlist yet? The free popular IPTV playlist guide covers where M3U sources come from.

Drag a file onto the page. Paste a link. Either works, and because a large playlist gets parsed in a background worker instead of on the main thread, the page carries on responding while a file with forty thousand lines in it is read, sorted and handed to the interface. That is the part a plain m3u8 player tends to skip. From here the list is yours:

• Pin what you watch. Pinned entries jump to the top. The four channels you actually open stop being buried under eight thousand you do not.
• Group the rest. Your names, not the provider's.
• Delete what is dead. Entries that no longer resolve can go, so what you keep is what works.
• Search the whole file. Filter by name or by group. This stops being optional somewhere north of a few hundred entries.

When the list is right, export it as a clean M3U file. That file works anywhere: back in here, in VLC, in whatever you normally use. One caveat, stated plainly because it cuts both ways: your edits live in your own browser storage and are never sent anywhere, which is exactly what you want from a privacy standpoint and exactly what you do not want the day you clear your browser data and discover that an afternoon of tidying went with it. Export anything you care about.

An M3U file is a plain text index. It holds no video. It lists where video lives, and that is the whole of it. An M3U8 file is the same idea written in UTF-8, and it happens to be the manifest format HLS uses to describe a live stream as a long run of very short segments, which is why a player aimed at one is almost always a player aimed at the other. So an m3u player and an HLS player are really doing a single job: read the manifest, fetch segments in order, keep the browser fed fast enough that nothing stalls.

You do not pick an engine. The player reads the URL and decides: hls.js for HLS, dash.js for MPEG-DASH, mpegts.js for a raw transport stream. Safari can play HLS natively, so there it simply steps aside. Adaptive bitrate comes from those engines rather than from anything clever on this end, and it is the reason a stream that would stutter through a fixed rendition will instead quietly drop to a lower quality when your connection dips and climb back once there is room again. That is why you play m3u8 online instead of waiting on a download.

Four things here are worth stating outright. They are architectural, not policy. Two of them will occasionally annoy you:

• The connection is direct. Video goes from its source to your browser. It never passes through this website, and nothing is relayed or cached here.
• Nothing you watch is recorded. There are no accounts and no viewing history, because playback happens entirely in your browser and never touches a server here. Google Analytics counts page visits, which is a different thing and cannot see inside the player.
• The source has to allow it. A direct browser connection needs an Access-Control-Allow-Origin header from the far end. Plenty of servers do not send one. That is a consequence of the design rather than a bug, and it explains why a link that works in a desktop app can fail here.
• Plain http:// streams are blocked. Not by us. A secure page is not permitted to load insecure video, and roughly one public stream in six is still plain http.

Something not playing? The M3U8 stream checker names which of those four it was. The HLS stream analyzer shows what the manifest actually declares, which in my experience is frequently not what the person who sent you the link believed it declared. Anything else is likely answered on the M3U and HLS questions page. One exception worth knowing: if you are a developer testing an hls player online rather than someone trying to watch something, skip playlists entirely and take one of the HLS test streams, which are published by Apple, Akamai and Dolby precisely so that people have something stable to point a player at.