steamstreamer
  1. AccountWho may stream
  2. EncoderOBS or another app
  3. RTMP ingestToken and upload server
  4. Store pageApp ID, approval, event

Guides / Not working

Steam broadcast not working: fixes for the encoder side

When a Steam broadcast is not working, the cause almost always sits in one of four places: the account cannot create a token, the encoder cannot reach Steam, Steam rejects what the encoder sends, or the stream runs but carries the wrong App ID, the number that tells Steam which game's store page the stream belongs to. Steam writes most of these failures into your broadcast history, so read that first, then jump to the matching fix below.

Where do I see why my Steam broadcast failed?

On the broadcast history page, logged in as the streaming account. Steam records every attempt there for 30 days, including the error conditions it saw. It takes two minutes and saves you from changing settings at random.

  1. Log in as the streaming account in a browser. If a team member streams, they have to do this on their account; the partner account that owns the game sees nothing.
  2. Open the history page at steamcommunity.com/broadcast/history. Each stream appears as a broadcast session row with one or more upload session rows under it.
  3. Count the upload sessions. An upload session is one continuous connection from your encoder. One long upload session means the connection held. Many short ones under the same broadcast session mean the stream kept dropping and reconnecting within 5 minutes of each other.
  4. Open Details on an upload session. Valve's stats guide says it shows the video resolution, the start and stop time and "possible error conditions". This is where the keyframe and CBR error appears.
  5. Check the game capsule. If the row has no game artwork, the Broadcast App ID was not set for that stream. The stream can work perfectly and still never reach your store page.

The broadcast upload page is the second place to look: Valve's demo guide says it shows statistics and diagnostic error messages for the running stream. If nothing appears in the history at all, the encoder never got a working connection: start at the encoder cannot connect.

Which fix matches my symptom?

Find the line that matches what you see; the middle column is the screen that confirms it.

What you seeWhere to lookGo to
Create RTMP Token does nothing, or shows "Access is denied (15)"Upload pageCannot create a token
OBS says "hostname not found", "connection timed out" or "Could not access the specified channel or stream key"OBSEncoder cannot connect
OBS says it is live, nothing appears anywhere on SteamYour broadcast URL, historyStream fails to start
OBS reconnects every few seconds, many short upload sessionsHistoryReconnection loop
"packets are out of order or we do not have enough time to transcode"HistoryPackets out of order
Picture is blurry, choppy or stutters for viewersYour broadcast URLBlurry or stuttering
Picture works, no soundYour broadcast URLNo sound
Warning that the account is playing another App ID, such as 250820Upload pageWrong App ID warning
Wrong App ID only when OBS was started from SteamUpload pageOBS launched from Steam
Steam shows the client's own capture instead of your OBS feedYour broadcast URLClient broadcasting interferes
Stream works but is missing from the store pageUpload page, history capsuleNot showing on the store page

Where in the chain does each error happen?

Each error belongs to one of four stages, and the stage tells you whether to look at your account, your encoder, your network or Steam's checks.

Where each Steam broadcast error happens Four stages from top to bottom: the Steam account and upload page, the encoder on your computer, the network path to Steam's upload server, and Steam's ingest which checks the stream before the store page shows it. Next to each stage are the errors that happen there. 1. Steam account 2. Encoder (OBS) 3. Network to Steam 4. Steam ingest Upload page, token,App ID, visibility Server, stream key,keyframes, CBR, audio RTMP over TCP,upload bandwidth Checks the stream,then store page Token not created "Access is denied (15)" Wrong or missing App ID Library App ID overrides it Old token after regenerating Keyframe interval 0 or auto No audio on streaming track Bitrate above 7000 kbps "hostname not found" "connection timed out" Firewall blocks RTMP Upload too slow, drops Keyframe and CBR error "packets are out of order" Many short upload sessions No capsule in history
Errors in stages 1 and 2 stop the stream before it leaves your machine. Errors in stage 3 show up in the encoder. Errors in stage 4 show up in Steam's broadcast history, often while OBS still says everything is fine.

What causes each problem, and how do I fix it?

Where only other developers have reported something, we say so; Valve does not document every error.

You cannot create an RTMP token

Symptom

Clicking Create RTMP Token on the upload page does nothing useful. Developers have reported three versions: the error Settings update failed! - "Access is denied (15)", a loading wheel followed by the same page with no token and no message, and a note that the account is "not associated with an event".

Cause

Valve documents two hard requirements for the token. The account must be non-limited, meaning it has spent at least 5 USD on the Steam store; limited accounts "will not be able to create an RTMP token". And the account must either have the "Broadcast Live" permission in your Steamworks partner account or be a member of the Store Broadcast Beta group. The "Access is denied (15)" thread has no answer from Valve, so linking that code to a missing permission is our inference, not a documented meaning.

Fix

Confirm the account is not limited (what counts toward the 5 USD), that it owns the game, and that it has the permission or the group membership. The requirements guide walks through each check, and the stream key guide covers creating and regenerating the token. If all of those are true and the button still fails, try another browser and try again later. One developer hit the silent failure after streaming successfully before, which points to a temporary problem on Steam's end.

The encoder cannot connect to Steam

Symptom

OBS never goes live. Developers have quoted these OBS messages: hostname not found; The connection timed out. Make sure you've configured a valid streaming service and no firewall is blocking the connection.; and Could not access the specified channel or stream key, sometimes followed by connecting and dropping every few seconds.

Cause

The server address or the stream key is wrong, the token was invalidated, or something on the network blocks the connection. Steam picks the upload server by your IP when you create the token, so a server copied from a forum post or another machine may be the wrong one. If you invalidated and regenerated the token on the upload page, the old key in OBS stops working.

Fix

In OBS, open Settings, Stream, choose Custom..., and paste the Upload Server into Server and the current token into Stream Key, both copied fresh from the upload page while logged in as the streaming account. Leave any username and password fields empty. One developer reported that "hostname not found" went away after removing the rtmp:// prefix they had in the server field. If the exact copied value fails, check that the prefix appears only once. For timeouts, note that RTMP normally uses TCP port 1935; that is general RTMP behaviour, not something Valve documents for Steam. Allow outbound connections on it in your firewall, and on office or venue networks, test from another connection to rule out a blocked port.

The stream fails to start

Symptom

OBS shows a green live indicator and a rising timer, but your broadcast URL keeps loading and the store page shows nothing. One developer saw a history entry with the right duration and no errors.

Cause

Valve's setup guide names one setting for this: the keyframe interval. In OBS's advanced output settings it must be 2, and "without this setting your stream will fail to start". OBS's default of 0 means automatic, which with x264 can mean a keyframe only every 250 frames.

Fix

In OBS, Settings, Output, set Output Mode to Advanced, then on the Streaming tab set Keyframe Interval to 2 and Rate Control to CBR. If your encoder counts in frames, use 60 at 30 fps and 120 at 60 fps. Check the profile is High as well; vMix in particular defaults to Main and level 3.0, which Valve says you must change. The full list is in Steam broadcast settings.

OBS keeps reconnecting, history shows many upload sessions

Symptom

OBS shows "Reconnecting" over and over, or connects and drops every few seconds. The history page lists many short upload sessions under one broadcast session, and the upload session details show: Make sure your upload key-frame interval is set to 2 seconds and use constant bitrate (CBR). Limit your encoders group of picture (GOP) to at most two times your framerate.

Cause

Valve's guide says this exact error means the keyframe interval is not set correctly. Each drop closes the upload session and the reconnect opens a new one. The other common cause is an upload line that cannot hold the bitrate: RTMP runs over TCP, so a saturated line backs up until the connection closes. One developer fixed a loop by moving from 852x480 to 1280x720; Valve's spec only says 16:9, and 852x480 is not exactly 16:9, so the shape may have been the real problem.

Fix

Set the keyframe interval to 2 (not 0), rate control to CBR, and for frame-based tools a GOP of 2x the frame rate. Send an exact 16:9 output: 1280x720 or 1920x1080. Then lower the bitrate until it sits well under your measured upload speed; 4500 kbps at 720p60 needs about 7 Mbps of real upload. If OBS's Stats panel shows the stream output dropping frames, the line is the bottleneck. Run 10 minutes and check that the history shows one long upload session.

"Packets are out of order or we do not have enough time to transcode"

Symptom

A developer quoted this from the broadcast history, alongside "hundreds of 00:00:00 lines": Error: This can occur when packets are out of order or we do not have enough time to transcode incoming stream. Try lowering your bitrate in your uploading application. Or increase the Broadcast Delay setting above (recommend 10 seconds).

Cause

Valve's Steamworks pages do not document this error or a Broadcast Delay setting. The message itself names two causes: too much data arriving for Steam to process in time, or packets arriving out of order, which usually means an unstable connection.

Fix

Lower the video bitrate (try 4500 kbps, or 3000 kbps at 720p30). Then look for a delay setting on the upload page and raise it. The message recommends 10 seconds, another developer suggested 15 to 20 seconds at 6000 to 7000 kbps, and a 2018 post mentioned a default of 6 seconds. We have not been able to confirm the setting's current label, so treat these values as reported. Also apply the keyframe and CBR fix above, since a missing keyframe interval makes segments uneven.

The picture is blurry, choppy or stutters

Symptom

Developers report a stream that is "always really blurry" from OBS while the Steam client's own broadcast looks sharp, and a GPU-encoded stream "working like 5 FPS every 5 secs" on Steam only, at 5900 kbps, High, level 4.1, keyframe 2.

Cause

Valve's spec section opens with this case: stuttering, pausing or broken playback usually means the stream breaks one of the required values (H.264 High, level 4.1, 30 or 60 fps, 16:9, keyframe 2 s, CBR up to 7000 kbps). Blur usually means too little bitrate for the resolution, or a scaled non 16:9 canvas. Steam's stats guide adds one more factor: Steam only transcodes into smaller versions once an upload session has more than 10 concurrent viewers. Below that, every viewer gets your source stream at full bitrate, so a viewer on a slow line stutters while you see a clean picture.

Fix

Pick 1280x720 at 60 fps around 4500 kbps for fast games, or 1920x1080 at 30 fps around 6000 kbps for detailed ones; 1080p60 is over level 4.1's limit. Match canvas and output resolution. If a GPU encoder stutters only on Steam, test x264 at veryfast on the same settings to see whether the encoder is the variable.

The stream has no sound

Symptom

Video plays on your broadcast URL, but there is no audio, or audio cuts in and out.

Cause

Steam expects AAC-LC audio at no more than 128 kbps. Beyond that, Valve does not document audio problems, so the rest is our experience with OBS. The streaming output is tied to one audio track. If your game or media source is routed to a different track, or the source is muted in the mixer, the stream goes out silent.

Fix

In OBS, Settings, Output, on the Streaming tab note the Audio Track number, then on the Audio tab set that track's bitrate to 128 or lower. In the audio mixer's advanced audio properties, make sure the game capture, desktop audio or media source is ticked for that same track and not muted. Then reload your broadcast URL and unmute the player, since browsers often start video muted.

Warning: the account is playing another App ID

Symptom

A developer quoted this warning from the upload page: Warning: The Streaming account is playing in the Steam Library the appid (250820) which is different than the appid that was initially setup on this configuration page. The library appid will be the one broadcast to users watching the stream. App ID 250820 is SteamVR.

Cause

This is documented. Valve's demo guide says playing a game from the Steam library tells the broadcast system which App ID the account is playing, and that the system gives that game priority over the App ID on the upload page. Valve's FAQ adds that for VR games you should stream with an external tool such as OBS so Steam points at your game, not SteamVR.exe.

Fix

On the machine logged in as the streaming account, close SteamVR and any game launched from that account's library. The developer who reported the warning fixed it by closing Steam and SteamVR while streaming from OBS. If you need to play the game on stream, play it from a different Steam account than the one that broadcasts.

OBS launched from Steam forces the wrong App ID

Symptom

A developer reported that when they start OBS from Steam, the upload page says they are streaming the wrong App ID, so the stream does not show on the game page.

Cause

Not documented by Valve, but it fits the documented rule above. OBS is available as an app on Steam, so launching it from the library counts as playing OBS's App ID, and the library App ID wins over your configured one. That explanation is our inference.

Fix

Start OBS from its own shortcut or obs64.exe, not from the Steam library, on the account that broadcasts.

The Steam client's own broadcasting interferes

Symptom

A developer reported that after the Steam client gained built-in broadcasting, Steam tried to pull the feed from the client instead of their OBS RTMP stream. Disabling broadcasting in the client stopped the browser feed showing.

Cause

The client's broadcasting and RTMP broadcasting run on the same account. Valve documents only that the client's built-in broadcasting reports the App ID of what you play (which is why it cannot stream a demo to the base game page). How the two interact beyond that is not documented.

Fix

Reports conflict, so test both ways. Other developers advise turning off broadcasting in the Steam client's settings (where that setting is), or not running the client at all on the streaming account, since an RTMP stream does not need it. If your feed then disappears, as one developer reported, set it back and instead close any game running on that account.

How do I confirm the broadcast is fixed?

Run a test with the upload page set to Friends Only, which Valve recommends for testing because only you and your friends can see it.

  1. Open "Your broadcast URL" from the quick links on the upload page and check picture, sound and frame rate.
  2. Leave it running 10 minutes. Bitrate problems often only show after the encoder buffer fills.
  3. Stop, then read the history. You want one upload session, no error conditions, the resolution you set, and your game's capsule on the row.
  4. Switch to Public when it is clean. Friends Only streams never appear on the store page.

If the stream is clean in history but not on the store page, the encoder is done and the remaining problem is approval, timing or App ID: see why a Steam broadcast is not showing on the store page. If viewers report spinners or messages while your history looks clean, see what "stuck on loading" means. If your settings are right but a long stream from a home PC keeps dying when the machine sleeps, updates or loses its connection, Loopcast runs a video stream from a datacenter and restarts it by itself within seconds of a drop. A full OBS setup from scratch is in how to stream to Steam with OBS.

Questions about a Steam broadcast that is not working

Why can't I broadcast on Steam at all?

Usually the account. Valve requires a non-limited account (at least 5 USD spent on the Steam store), ownership of the game, and either the "Broadcast Live" permission in Steamworks or membership of the Store Broadcast Beta group. Without these you cannot create an RTMP token.

Do I need a new stream key after changing the Broadcast App ID?

Valve's troubleshooting note says that if the App ID was missing, you enter it and regenerate the RTMP token, then put the new token into your software.

What does the keyframe interval error in broadcast history mean?

The message "Make sure your upload key-frame interval is set to 2 seconds and use constant bitrate (CBR)" means Steam received a stream whose keyframes were not every 2 seconds or whose bitrate was not constant. Set the keyframe interval to 2, rate control to CBR, and a GOP of at most 2x the frame rate.

Does the Steam client need to be running to broadcast with OBS?

Valve does not say it must be. Developers report streaming over RTMP with the client closed, and closing it on the streaming account avoids the library App ID overriding your configured one.

Sources