Buffering usually comes from one of three places: the source, your streaming server, or the viewer's own connection. Find which one first.
Checks
- One channel, or many? If only one channel buffers, the cause is usually its source. If every channel on one server buffers, look at that server (step 4).
- Preview the channel. In Streams → Manage Streams, open its row menu (Options) and click Preview. If the preview stops and starts too, the problem is before the viewer: go on. If it plays smoothly, go to step 6.
- Check the source. Look at the channel's Restarts and its Restart history: each restart cuts the picture for every viewer. Add a backup from another provider: see A channel keeps restarting.
- Check the server. On Dashboard → Overview, CPU use, Memory use, Stream capacity and Network load show how full your servers are; Servers → Server Stats shows them over time.
- Network load compares the server's traffic with its Network capacity (Mbps), set on its page. Set it to the speed your host sells, so the figure is right.
- Converting takes about one processor core per HD channel. Send channels as they are (Original quality (no conversion)) where you can, or use a video card: see Video cards.
- Spread the load. Add a streaming server. Channels on Automatic start using it at once, and a full server is skipped: see Load balancing.
- The viewer's side. If the preview plays well and only some customers buffer, the cause is usually their internet or their device. A channel converted with Convert: SD needs at most 1,500 kbps. It changes the channel for every viewer, and costs processor on your server.
Updated 12 November 2026