Source feeds
Live channel streams are delivered for operator use via common playlist formats. Multi-region selection is available; availability can vary by source and region.
Guides
IPTV Restream Guide for Operators
A practical overview of how restream works, how connections are counted, and what you need before requesting a trial or paid activation.
On this page
Guide topics
Jump to the section you need, or read in order if you are evaluating Restream for the first time.
Concept
What IPTV restream means
In an operator context, restream is the process of pulling live television streams from an upstream provider into your own IPTV server or panel, then distributing those streams to your viewers through your infrastructure.
Your server makes the upstream requests. Your panel or media stack handles how those channels are presented and redistributed. Plans on this site are sized by concurrent upstream pulls — not by how many end users watch a channel once it is inside your network.
This model is intended for IPTV server operators and similar infrastructure teams. It is not a personal household IPTV subscription.
See the process flowUpstream vs redistribution
Upstream is the pull from Restream to your server. Redistribution is what happens after that on your side. Billing and plan limits focus on the upstream side.
Catalogue figure
13,500+ is a listed catalogue figure for live channels. It is not a guarantee that every listing is available at all times.
Architecture
Upstream streams in practice
Your panel or media server requests live channel feeds from the restream source. Those requests are what consume connections.
Your server
Your IPTV panel or streaming stack pulls the channels you need. Concurrent pulls count against your plan. Idle catalogue entries do not consume connections until requested.
Your viewers
Once a channel is pulled into your infrastructure, how you redistribute it to end users is handled by your own systems. Viewer count is separate from upstream connections.
Delivery
M3U / HLS basics
Streams are commonly provided as M3U playlists that reference HLS (or similar) media URLs. Operators import the playlist into a panel or media server so channels appear as selectable live sources.
Exact import steps differ by software. Panel-specific commands and screenshots are documented separately and should be verified against your panel version. Do not share playlist credentials or access links publicly.
Read the M3U / HLS guidePlaylist
An M3U file lists channel entries and stream URLs your server can request.
HLS segments
HLS delivers media in short segments so live playback can start and continue smoothly.
Capacity
How connection counting works
Each connection is one concurrent upstream channel pull from your server to the restream source.
Example: if your server pulls 20 different live channels at the same time, that typically uses about 20 upstream connections — even if hundreds of viewers watch those channels through your panel.
Actual usage depends on configuration and simultaneous upstream requests. Plans do not imply unlimited viewers, unlimited bandwidth, or content redistribution rights.
Deep dive on connections
Example load
20 live channels
Pulled concurrently
Upstream usage
≈ 20 connections
Counted against your plan
Your viewers
Internal redistribution
Viewer count is separate
Preparation
Server requirements & IP whitelisting
Paid access is tied to approved public IPv4 addresses. Stable server IPs are expected.
Server readiness
You should already operate an IPTV panel or media server capable of importing M3U/HLS sources and managing concurrent channel pulls. Hardware and software sizing is your responsibility.
Server setup overviewPublic IPv4 whitelisting
For paid activation, provide the public IPv4 addresses of your streaming servers and relevant load balancers. Residential or frequently changing addresses are not assumed. Activation is manual after payment verification.
IP whitelisting guideAccess
Trial and paid activation
Both paths are arranged through support. WhatsApp is the primary contact channel; Telegram is available as a secondary option.
Free trial
- 12-hour test window
- Up to 10 concurrent connections
- Timing begins on first playback
- A second trial may be available on request
- Country restrictions may apply
Paid activation
- Choose a monthly connection plan
- Confirm payment details with support
- Provide public IPv4 addresses for whitelisting
- Manual activation after payment verification
- Receive M3U / HLS access for your servers
Support
Channel reporting
If a listed channel fails, buffers excessively, or returns errors, report it to support with enough detail to investigate: channel name as shown in your playlist, approximate time, your server public IP, and what error or behaviour you observed.
Catalogue listings are not a guarantee of continuous availability. Reporting helps support check the source side when something is wrong.
WhatsApp supportWhat to include
Playlist entry name, time of issue, server IP, and a short description of the failure. Screenshots help when available.
Avoid friction
Common mistakes
These issues show up often when operators first connect upstream restream feeds.
Confusing viewers with connections
Plan size is about concurrent upstream channel pulls, not how many people watch after redistribution.
Unstable or wrong IP
Paid access expects stable public IPv4. Changing IPs or sending a private LAN address will block activation.
Pulling every channel at once
Preloading the entire catalogue can exhaust connections immediately. Pull only the channels you need concurrently.
Sharing credentials publicly
Playlist URLs and access details should stay private. Public exposure can lead to unauthorized pulls against your limit.
Misreading trial timing
The 12-hour window begins on first playback, not necessarily when credentials are first sent.
Treating it as household IPTV
This service targets operator servers. Personal single-device subscription expectations do not match how connections work.
Next steps
Troubleshooting intro
If streams fail after setup, check basics first: correct public IP whitelisting, playlist imported as intended, concurrent pulls within your plan, and that you are not hitting country or access restrictions. Then gather details and contact support.
For a structured checklist, use the dedicated troubleshooting page.
FAQ
Guide questions
Short answers that expand on the sections above.
Restream means your IPTV server or panel pulls live channel streams from an upstream source, then redistributes them through your own infrastructure to your end users. It is an operator workflow — not a personal household subscription.
Each connection is one concurrent upstream channel pull from your server. Viewer seats on your panel are separate if you redistribute internally. See the connections explained page for examples.
The trial lasts 12 hours with up to 10 concurrent connections. Timing begins on first playback. A second trial may be available on request; country restrictions may apply.
Paid activation requires whitelisting the public IPv4 addresses of your streaming servers and relevant load balancers. Access is tied to those approved addresses after payment verification. Details are on the IP whitelisting guide.
No. 13,500+ is a listed catalogue figure. Individual channel availability can vary by source and region. Report issues to support so they can be checked.
Read how restream works for the high-level flow, then review connections and M3U/HLS basics. When ready, request a trial on WhatsApp.