What do the Steam broadcast player messages mean?
Steam's documentation does not list the viewer messages. The wording in the "Message" column comes from Steam's public web player code (the script behind the broadcast watch page, which we read in October 2026), from the Steam client, or from developer reports, as marked. The "likely meaning" column is our interpretation unless it cites Valve's docs.
| Message or symptom | Likely meaning | Who can fix it | Fix |
|---|---|---|---|
| "Loading..." that never ends (web player) | The player cannot get the next piece of video and keeps asking again | Usually the broadcaster; sometimes the viewer | Broadcaster: check the upload session is running and the keyframe interval is 2. Viewer: refresh, try a browser |
| "Waiting for [name]'s broadcast to start" (web player) | The broadcast exists but no video has started | Broadcaster | Start or restart the encoder; check it actually connected |
| "Waiting for [name] to reconnect to Steam" (web player) | The upload dropped and Steam is holding the broadcast open | Broadcaster | Let the encoder reconnect; then fix whatever drops it |
| "Waiting for a response from [name]" (web player) | Steam is waiting on the broadcaster's side to answer | Broadcaster | Check the encoder or client is running and online |
| "[name]'s broadcast is not available at this time" (web player) | Shown after about 60 seconds of waiting for a response, and for unknown states | Broadcaster | Restart the stream; check visibility is Public |
| "[name] is currently unable to maintain a stable broadcast connection to Steam." (web player) | The upload is too unstable to play | Broadcaster | Lower the bitrate, use a wired connection |
| "Steam is currently experiencing high broadcast load in [name]'s area..." (web player) | Steam could not reserve a server for the broadcast | Steam | Wait a few minutes, as the message says |
| "[name]'s broadcast has ended" (web player) | The broadcast session closed | Broadcaster | Start a new stream |
| "This broadcaster is offline" (Steam client, reported) | Reported mostly for friend broadcasts watched from chat | Broadcaster or viewer | See friend broadcasts |
| "Please stand by" (reported) | Not in the web player code; most likely an image inside the video itself | Broadcaster | Check what the encoder is capturing |
| Same few seconds loop (reported) | Not documented; see looping | Broadcaster, then Steam | Check the upload session, restart the encoder |
| Gray box or blank video while marked Live (reported) | Video arrives but shows nothing, or never arrives | Broadcaster | Check the encoder preview and the history |
| Infinite loading on phones only (reported) | Mobile playback fails while desktop works | Broadcaster | Stay inside the spec, lower the bitrate |
What does "stuck on loading" mean for the broadcaster?
It usually means Steam has a broadcast for you but not a steady supply of video. To see why, you need Valve's two session types, documented in its viewership stats guide:
- A broadcast session starts when you first go live and lasts at least 5 minutes after you stop. It is what viewers connect to.
- An upload session is one continuous connection from your encoder. If the network drops, it closes; your encoder opens a new one, and Steam attaches it to the same broadcast session if it is still open.
So a viewer can open a broadcast that exists while no upload session is feeding it. In the player code we read, Steam's server answers the player with states such as "waiting for start" and "waiting for reconnect", and the player shows the matching "Waiting for..." text while it retries. That is the most common "loading forever" case, and it is a broadcaster problem.
Your broadcast history shows exactly this picture: one broadcast session row, with an upload session row for each connection. Several upload sessions in one broadcast mean viewers hit a loading gap each time. The upload session details list error conditions; the most common is Valve's keyframe and CBR message. The fixes for drops are in Steam broadcast not working.
Why does the broadcast load for me but not for viewers?
Because viewers may be downloading more than their connection can carry. Valve's stats guide says Steam only transcodes your stream into smaller versions (likely 720p, 480p and 360p) once an upload session has more than 10 concurrent viewers. With 10 or fewer, every viewer gets your original stream. A 7000 kbps source works on your fiber line and spins on a viewer's phone or hotel Wi-Fi. Small store page streams spend most of their time under that threshold, so this hits them hardest.
A 2018 report shows the pattern: an infinite loading screen on iOS and Android while PC viewers were fine, for a stream the developer listed as 1600x900 at 60 fps, CBR 7000 kbps, with "Transcoded Streams: 0" in the history. Our arithmetic says 1600x900 at 60 fps is also above H.264 level 4.1's macroblock limit (about 342,000 per second against 245,760), the same issue as 1080p60. Whether that caused the mobile failure is our inference, not something Valve confirmed. The developer reported that Android viewers recovered the next day.
The fix on your side: stay inside Valve's spec and leave headroom. 1280x720 at 60 fps around 4500 kbps, or 1920x1080 at 30 fps around 6000 kbps, keyframe interval 2, CBR. The reasoning and test encodes are in Steam broadcast settings.
Why does my Steam broadcast loop the same few seconds?
Valve has not documented this, and the threads reporting it have no answer. A developer described the store page player looping "the same ~15 seconds over and over" while the stream looked fine in the broadcasting dashboard, sometimes with two player windows at once and a broken preview thumbnail, across devices and browsers. A viewer in another thread described the player trying to connect for about 5 seconds, resetting, and starting over.
Our reading of the player code: when a video download fails, the player shows "Loading..." and asks Steam for the broadcast again. If the newest video Steam has is the same short stretch each time, the viewer sees that stretch repeat. That fits an upload that stalls or keeps reconnecting. It is an inference. What to do:
- Check your history for many short upload sessions during the loop. If there are, fix the drops first.
- Check the encoder's keyframe interval is exactly 2 seconds and rate control is CBR. Uneven segments are the documented cause of interrupted streams.
- Stop the encoder, wait more than 5 minutes so the broadcast session closes, then start again. This gives viewers a fresh broadcast instead of the old one.
- Compare the store page with your broadcast URL. If your broadcast URL plays live and only the store page loops, the problem is on Steam's side; reports so far suggest it clears on its own.
Why is the broadcast a gray box or a blank screen while it says Live?
Either the video arrives but contains nothing, or it does not arrive at all. Two reports cover both cases. One developer saw "Live" with "just a blank screen" for viewers; replies suggested checking that the encoder's scene actually captured the game, since some games block game capture and need window or display capture instead. Another saw a gray box only in the US evening while rebroadcasting a file from OBS, after drawing 409 viewers in the daytime; it was never explained.
Check your encoder's preview first. If the preview is black, the stream is black: switch the capture method or the source. If the preview is fine, open your broadcast URL and the history. A history with clean, long upload sessions and a gray store page player means the problem is between Steam and the viewer. There is little you can change beyond lowering the bitrate for slow viewers.
What does "Please stand by" mean on a Steam broadcast?
We could not find this text in Steam's web player code or in Valve's documentation, so we cannot tell you what Steam means by it. Our best guess is that it is part of the picture itself: a holding image that broadcasting software or the capture source sends when it has nothing else to show. If you see it on your own stream, look at what your encoder is sending. If you see it on someone else's, it is up to them.
What can a viewer do when a Steam broadcast will not load?
Viewers can only fix problems on their own side, and these are the steps that have helped people in reports:
- Refresh after a few seconds. Valve's own troubleshooting note says to refresh the product page, and that the first viewers take the longest to connect.
- Switch between the Steam client and a web browser. One user reported broadcasts stuck on loading in the Steam client that played "almost instantly" after pasting the page URL into a browser.
- Turn on GPU accelerated rendering in the Steam client's settings if it is off. Forum replies say broadcasts may not show without it. This is reported, not documented.
- Try a different browser. The player shows a specific message if a browser lacks the features it needs: "Your web browser does not support the minimum set of features required to watch this broadcast." Valve's list of supported browsers is in how to watch a Steam broadcast.
- Try another network or a desktop. On a slow connection, a small stream sends full bitrate until it has more than 10 viewers. Mobile-only loading has been reported while desktop worked.
- Run Steam Support's checklist. For broadcasting that keeps failing, Steam Support lists these steps: restart Steam and the computer, restart the modem and router, use a wired Ethernet connection instead of Wi-Fi, test on a different network, and check that a firewall or anti-virus program is not blocking Steam.
If none of these work, it is almost certainly the stream. Telling the developer the exact message you see saves them a lot of guessing.
Why does a friend's broadcast say "This broadcaster is offline"?
This message comes from the Steam client when you watch a friend, not from a store page stream. Users report a loading screen of about a minute that ends in "This broadcaster is offline" while both people are online, and one VR player saw it only with VR games. Developers report two workarounds. The broadcaster changes their client broadcast setting from requiring a watch request to letting friends watch without asking. Or the viewer watches from the community broadcasts page in a browser rather than from chat. In a related report, a VR broadcaster saw "Waiting for a response from" their own name and suspected an accept prompt hidden behind the headset, although their setting allowed anyone to watch. As far as we can tell, store page streams sent over RTMP do not use these watch settings at all.
What else should the broadcaster check?
If viewers can open the player at all, the stream is on the page; if they cannot find it, that is a different problem covered in Steam broadcast not showing on the store page. For loading problems, run this short list while streaming:
- The upload page shows the stream running, with no diagnostic errors.
- The history shows one long upload session, not a series of short ones.
- Your encoder reports no dropped frames on the stream output.
- Your bitrate is well under your measured upload speed and at or under 7000 kbps.
- Someone outside your network can play your broadcast URL for 10 minutes.
Viewer counts in the history are also useful later: the upload session graph shows when viewers dropped off, which often lines up with a reconnect. More on reading that page is in managing a Steam broadcast.
Questions about a Steam broadcast stuck on loading
Why is my Steam broadcast stuck on loading?
Usually because the broadcast exists but no video is arriving: the encoder stopped, the upload dropped and is reconnecting, or the stream is too heavy for the viewer's connection. Check the broadcaster's history for short upload sessions and errors, and refresh as a viewer.
How long does Steam keep a broadcast open after the stream drops?
Valve's stats guide says a broadcast session lasts at least 5 minutes after you stop streaming. A new upload within that time joins the same broadcast session.
Does Steam lower the quality for viewers with slow internet?
Only once an upload session has more than 10 concurrent viewers. Then Steam transcodes into smaller versions such as 720p, 480p and 360p. Below that, all viewers get your original stream.
Why does the broadcast work in a browser but not in the Steam client?
Valve does not document this. Users report it, and report that turning on GPU accelerated rendering in the client or simply watching in a browser works around it.
Does a Steam broadcast have a delay?
Yes, some. Developers report a Broadcast Delay setting on the upload page, with a 6 second default mentioned in 2018, and a Steam error that recommends 10 seconds for streams that are hard to transcode. Valve's Steamworks pages do not document it.
Sources
- Steamworks: Broadcast viewership statistics (broadcast and upload sessions, 5 minute window, transcoding above 10 viewers)
- Steamworks: Setting up a stream (RTMP specs, refresh advice, first viewers take longest)
- Steam Support: Steam Broadcasting (troubleshooting broadcasting issues)
- Steam's public broadcast watch page script (broadcast_watch.js), read on 24 October 2026, for the exact player messages.
- Reports in the Store Broadcast Beta group (looping, endless loading, gray box, blank screen, mobile-only loading) and the Steam Broadcasting group and Steam Discussions (client loading, broadcaster offline).