Français Open the player

Find the right guide for your device

Choose your browser or device, then check access and source setup. Wemovexa IPTV guides explain the available workflow without assuming every stream will play everywhere.

All guides

Choose a starting point before changing settings

The same playback interface can behave differently across browsers, operating systems and media formats. Start with the device you actually intend to watch on. Next, establish whether you are using a browser page or an installed application, because their network paths can differ. Finally, have your existing access ready and confirm that an authorised line is assigned to it. These three checks make the walkthrough easier to follow and keep sign-in failures separate from catalogue or video problems. None of the guides supplies a playlist, channel source or subscription content.

Chrome and Firefox browser workflows

The Chrome guide covers the browser workflow and the checks surrounding the first playback attempt. Use the Firefox guide for the equivalent context in Firefox. A browser name is only part of the compatibility picture: the operating system and device still affect which media can be decoded. A managed computer may also apply restrictions through its browser profile. Opening the page successfully establishes that the interface loads, but it does not establish that every separate video resource will be reachable or playable.

Safari and Apple devices

Choose the Safari guide for browser-specific steps. The Mac guide adds the desktop context, while the iPhone and iPad guide focuses on phones and tablets. The player prefers native HLS when the browser reports support for it. That preference does not guarantee support for every codec or audio track a provider might send. These guides describe browser use on Apple devices; they are not instructions for a native iOS or macOS application supplied by the player.

Windows: identify which application is making the request

The Windows PC guide is the starting point for computer viewing. The web page and Windows desktop application share an interface, but their routes to a provider can be different. The desktop application has a local relay and can fall back to the service relay in some circumstances. That mechanism is not a blanket compatibility claim for all provider panels. Once you have identified your workflow, the VLC comparison can help assess requirements involving files, source management and the kind of interface you want.

Android phones, tablets and TV boxes

The Android guide distinguishes browser use from the Android APK. On a TV box, also check whether the remote sends the keys needed to move and select controls. The player includes arrow-key navigation and validation, but the device still determines which button events arrive. A browser may need the HTTPS relay for HTTP streams, while the APK uses a different direct path. Moving between those environments changes more than the presence of a home-screen icon, so include that detail in any playback problem report.

Smart TV browsers need a model-specific test

Start with the smart TV browser guide if you want to use the television’s own browser. The label smart TV covers many systems and generations of hardware. Check the page, remote navigation and one authorised stream on the actual television before assuming the setup is suitable. A successful phone test does not establish television compatibility. If media support or controls are insufficient, the player comparisons help turn that observation into specific requirements for another workflow rather than repeated attempts with an unsupported browser.

Resolve shared concepts once

If your starting point is a file or export link, read the M3U explanation before looking for a general import screen. If you are unsure which password belongs in the sign-in form, the Xtream guide separates provider credentials from player access. Missing programme titles belong in the EPG and XMLTV guide. A catalogue followed by a black video screen may instead call for the built-in proxy explanation, which separates network restrictions from provider refusals and media compatibility.

Make a playback test informative

  1. Record the device, browser and browser version before you begin.
  2. Confirm access, line assignment and the provider’s connection rules.
  3. Try one channel and then a second, closing playback sessions you no longer need.
  4. Note when the failure occurs and copy only the visible error, without exposing credential-bearing URLs.

Keep the source unchanged when comparing browsers and change one condition at a time. Another browser profile may have no favourites or history because those records are stored locally, even when the underlying access is the same. The FAQ explains those differences. When the workflow is clear, open the player with your personal access and verify the result on the device that matters to you.

Ready to try it?

The player opens in your browser: sign in with your credentials and your IPTV line loads.

Open the player