Build better playlists.

Connect the Playlist Editor

A connection code is a short-lived invitation from one TV or browser device. It never reveals the database ID. After a successful connection, an encrypted Laravel session remembers that device in the current browser.

Choose how the playlist is loaded

External playlist requirements

• The player recognizes M3U, XSPF, XML/JSPF, PLS and ASX lists. The visual web editor is designed around Extended M3U options.
• The remote URL must be reachable from the TV. A private IP is usable only while the TV is on that network.
• This installation does not relay public media through the Laravel backend. The playlist, manifests, segments, subtitles and artwork are requested from their own origins.
• Browser clients need CORS permission. At minimum, return Access-Control-Allow-Origin for the website origin or * when credentials are not used.
• Use HTTPS for both the website and playlist to avoid mixed-content blocking.

Local-network playlists

Add the local URL as an External Playlist, for example http://192.168.1.20/playlists/home.m3u. Bind that server to the LAN interface, permit it through the firewall and keep the address stable with DHCP reservation or local DNS. Unlike the historical OEM behavior, this independent build does not rely on an automatic iptv.local service.

Install or launch CLUB IPTV

Use the CLUB IPTV website address or the installation package provided for your platform. An Android APK cannot be installed directly on Samsung Tizen or LG webOS; those platforms need their own package or can use the hosted browser version.

Android upgrade checklist

1. Build with the same application ID and signing certificate used by the installed custom app.
2. Increase the Android version code.
3. Back up the previous APK before distributing the update.
4. Test install-over-update and a clean installation on a spare device.

Understand the playlist structure

Save playlists as UTF-8 text. The first line is #EXTM3U. Every item then has an #EXTINF metadata line, optional directive lines and one source URL.

• Use duration 0 or -1 for live streams.
• Everything after the comma is the displayed title.
• Write attributes before the comma as name="value". Keep values in double quotes.
• The URL must be on the next non-directive line.
• Blank lines are optional but make large playlists easier to debug.

Choose the correct attribute

These are the options understood by the editor and player. Recognition fields describe the channel; playback fields control how it opens; presentation fields control how it appears.

Advanced lines

The editor preserves additional #EXTINF attributes and directive lines. Use options such as #EXTVLCOPT only when the target player actually supports them; browser playback may ignore native-player directives.

Control each tile

Place these directive lines after their #EXTINF line and before the source URL.

Entry directives override playlist-wide defaults. For example, #EXTM3U size="small" background="#10231f" sets defaults, while one item can still use #EXTSIZE: Big.

Configure catch-up correctly

The editor offers None, Default, Flussonic and Shift. Choose the protocol implemented by the stream provider and enter the real archive length.

• None: ordinary live stream with no archive.
• Default: provider-specific/default catch-up URL rules.
• Flussonic: archive URLs generated using Flussonic conventions.
• Shift: time-shift style playback supported by the provider.

These options do not create an archive. The origin server must already store and serve historical media.

Build a multi-level video library

A root library contains links to category playlists. Explicitly use type="playlist" when the URL does not end with .m3u or .xspf.

1. Root categories

2. A category can contain more playlists

3. Final playlist contains videos

type="video" tells the player the item is on-demand and should support seeking when the media format allows it. A nested playlist can mix subcategories and final videos.

Match channels with XMLTV

The recommended setup is to add XMLTV sources in the backend, select only the channels you need and run the scheduled daily refresh. Imported programmes remain available until they become older than seven days.

Recognition order

1. tvg-id against the XMLTV channel ID.
2. tvg-country to distinguish channels with the same display name.
3. tvg-name and playlist title as controlled fallbacks.

The app can also read an external guide declared in the M3U header:

Large guides can overwhelm older TVs. Backend-managed sources are easier to filter, refresh and debug. The backend importer accepts compressed XMLTV sources, but direct TV loading depends on the device parser and is safest with a reasonably small uncompressed guide.

For a guide loaded directly by a browser/device, configure CORS and range-related headers in the same way as an external playlist. The guide URL must be accessible to that device; it is not automatically proxied through this backend.

When content does not load

• Confirm the file is UTF-8 and begins with #EXTM3U.
• Check every #EXTINF entry has one source URL and properly quoted attributes.
• Open the playlist URL in a browser and test streams in VLC.
• A stream working in VLC does not guarantee that the TV supports its video codec, profile, audio layout or subtitles.
• Browser playback requires compatible HLS and cross-origin response headers from the media origin.
• If EPG is missing, compare tvg-id with the enabled channel in the selected EPG source.
• If Android shows old content, save the playlist and use the app Refresh action.