IPTV glossary: formats, networks and viewing terms

Use these definitions to identify a source, understand an error and distinguish playback capabilities from related industry terms.

Separate terminology from feature claims

These definitions cover formats, network behaviour and viewing workflows. Including a term does not mean Wemovexa IPTV implements every associated feature. Start with the M3U, Xtream and EPG explanations for practical context.

IPTV

Television delivered over an Internet Protocol network. The term describes distribution technology rather than permission to watch particular programmes. The source must be your own authorised subscription.

Web IPTV player

A viewing interface that runs in a browser. Its ability to play a source depends on browser media support, source availability and the network rules applied to individual requests.

Playlist

A document describing media references. Successfully reading it does not establish that every referenced stream remains available. The list itself usually contains addresses and metadata rather than video.

M3U

A playlist format that can associate names and attributes with media addresses. Wemovexa IPTV does not provide general M3U file uploads or arbitrary playlist imports in its web interface.

M3U8

A UTF-8 playlist, frequently used as an HLS manifest. An M3U8 resource can describe one stream and its fragments rather than an entire channel collection ready to import.

HLS

A streaming approach using manifests and successive media resources. Reaching the first manifest is only one step; the player must also retrieve the referenced resources to keep playback running.

Manifest

A document describing resources needed for an HLS presentation. It may reference variants or media segments. The relay rewrites supported references so later requests follow the intended browser-compatible path.

Media segment

One fragment of a stream, fetched as playback proceeds. A manifest may load while a later segment is rejected, causing playback to fail initially or stop after starting.

MPEG-TS

An audio and video transport container often associated with TS files. The player has an environment-dependent MPEG-TS path, but container handling does not guarantee support for every codec inside it.

Codec

A method for encoding and decoding audio or video. A reachable media resource can still be unplayable when its contents require decoding capabilities unavailable in the browser or operating system.

Container

The structure holding video, audio and sometimes other tracks. Container recognition and codec support are separate checks; a familiar filename extension alone does not establish that playback will work.

Xtream Codes

A family of panel interfaces commonly using a server address, username and password. An assigned line supplies the information needed for catalogue requests and the construction of playback addresses.

Panel

The remote service answering IPTV source requests. Catalogue access and media access can receive different responses, so an account that returns channel metadata may still have playback requests refused.

Assigned line

An Xtream source associated with an access record through administration. The application receives its configuration; this is different from freely importing an arbitrary file stored on the viewing device.

EPG

Electronic programme guide data. This player focuses on now and next information. Missing schedule metadata does not necessarily affect video, which is obtained through a separate media request.

XMLTV

A structured format for channels, programme entries and times. The service has a server-side processing path for it, but the web interface has no personal XMLTV upload or URL field.

Guide identifier

A value used to match a channel with its programme data, often called tvg-id. Different identifiers can prevent a match even when the visible channel names appear nearly identical.

Now and next

A view of the current programme and the next scheduled item when known. It does not imply a full multi-day guide, programme recording or access to previously aired video.

CORS

Rules governing browser access to responses from another origin. A server can respond at the network level yet omit the headers required for a JavaScript player on a different site.

Mixed content

An HTTPS page requesting an HTTP resource. Browser security can block that request. The HTTPS relay handles relevant targets while leaving the browser’s security mechanisms in place.

HTTPS

HTTP protected by TLS between two endpoints. A secure browser-to-relay connection does not imply that the relay-to-provider connection is encrypted when the provider endpoint still uses HTTP.

Proxy

An intermediary that fetches a resource and returns its response. The built-in proxy adapts certain requests for the browser; it neither grants content permissions nor supplies missing video decoders.

Outgoing IP

The network address from which a request reaches the provider. For relayed resources it belongs to the outgoing server connection, which the provider may treat differently from your device’s connection.

Range

An HTTP request header asking for part of a resource by byte range. Forwarding it preserves opportunities to seek within media when the upstream source supports that operation.

206 response

An HTTP status indicating partial content, often following a successful Range request. The relay preserves the upstream status instead of inventing byte-range support for a source that lacks it.

Seeking

Moving to another point in media playback. It depends on the player, source file and server. Seek controls for movies do not automatically provide an archive or rewind support for live channels.

VOD

Video on demand, started at a time you choose rather than according to a live channel schedule. Movie and series interfaces do not guarantee particular titles are included with an access.

Catch-up

Access to a programme after its original transmission when both the source and player support it. This industry term does not identify a claimed feature of the current web player.

DRM

A system for managing and protecting media rights. Rewriting HLS references through a proxy does not unlock protected content or establish that the player supports the required rights-management system.

Playback buffer

Media data held ready before it is displayed. Playback can pause when data arrives too slowly to replenish it. Using a proxy does not guarantee additional available bandwidth.

Local storage

Browser storage used for assigned line details, favourites and history. It belongs to the browser profile in use; closing a tab does not necessarily remove the stored information.

Recovery code

A secret used with the access identifier to restore entry to the player. It is distinct from the provider’s password and should be kept out of public messages and screenshots.

Relay token

A value associated with access to proxy paths that can be retained in rewritten HLS references. It does not encrypt the target URL and should remain private like other access details.

Native HLS

HLS playback supplied by the browser’s own media implementation. The player prefers it for live playback when reported as available; usable codecs still depend on the surrounding device and software.

History

A local list of recently launched content, limited to 30 entries in the player. Launching an item again from history is not a promise of automatic restoration to an exact timestamp.

Use the terms to choose the next check

Codec, guide-data and account-permission problems need different investigations. The proxy explanation follows the network path, the guides cover devices and the comparisons help assess required features. Always use your own authorised source.