The settings at a glance
This is Valve's published spec for streams sent to Steam from external software, plus our recommended value for each line. Steam's own column is the rule; the recommendation is what we would type in on a typical home connection.
| Setting | Steam requires | We recommend |
|---|---|---|
| Video codec | H.264 | H.264 (x264, NVENC, AMF or Quick Sync all produce it) |
| Profile | High | High |
| Level | 4.1 | 4.1, which limits 1080p to 30 fps (see below) |
| Frame rate | 30 or 60 fps | 60 at 720p, or 30 at 1080p |
| Aspect ratio | 16:9 | 1280x720 or 1920x1080 |
| Keyframe interval | 2 seconds | 2 seconds, never 0 or auto |
| Rate control | CBR | CBR |
| Video bitrate | 7000 kbps maximum | 4500 kbps at 720p60, 6000 kbps at 1080p30 |
| Audio codec | AAC-LC | AAC-LC, stereo |
| Audio bitrate | 128 kbps maximum | 128 kbps |
Valve says these specs are required for now, and that stuttering, pausing or broken playback usually traces back to one of them. If your stream misbehaves, compare it line by line with this table before anything else. The troubleshooting guide starts from the same list.
What is the RTMP URL for Steam?
There is no single fixed address to copy from a forum post. Steam gives each streaming account its own pair of values on the broadcast upload page:
- Upload server: the RTMP URL. Steam picks an ingest server close to you based on your IP address when you click Create RTMP Token. In OBS this goes into the Server field.
- RTMP token: the stream key. It goes into the Stream Key field. Anyone who has it can stream as you, so treat it like a password. You can invalidate it and make a new one on the same page.
Two details catch people out. First, set the Broadcast App ID on that page before you create the token. Valve's troubleshooting note says that if the App ID was missing, you must enter it, regenerate the token and paste the new token into your software. Second, if you move the streaming machine to another location (a different office, a rented server in another country), create a fresh token from that network so Steam picks a nearby upload server.
The account must also be allowed to create a token at all. A limited account, one that has not spent at least 5 USD on the Steam store, cannot. The requirements guide covers that and the other account rules, and the stream key guide shows where the token goes in each tool.
Why does Steam need a 2 second keyframe interval?
A keyframe is a complete picture. Every frame between two keyframes only stores what changed since the last one, so a player can only start showing a stream at a keyframe. Live video platforms generally cut incoming streams into short chunks at keyframes, which is why they want them at a fixed, short spacing. Valve does not document Steam's internals, but it does document the result: a stream without a 2 second keyframe interval fails to start or keeps getting interrupted.
Valve's setup guide calls this step important and says that without it the stream will not start. When a stream does start but keeps dropping, the broadcast history page shows the matching error: 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.
That last sentence gives you the number to type in tools that count in frames instead of seconds:
| Frame rate | Keyframe interval in seconds | GOP size in frames |
|---|---|---|
| 30 fps | 2 | 60 |
| 60 fps | 2 | 120 |
In OBS and Streamlabs the field is in seconds, so you type 2. In ffmpeg and some hardware encoders it is in frames, so you type 60 or 120.
What resolution and frame rate should a Steam broadcast use?
Steam asks for a 16:9 picture at 30 or 60 fps, encoded at H.264 level 4.1. That level is the part most guides skip, and it decides which resolution and frame rate pairs are legal. Level 4.1 allows at most 245,760 macroblocks per second. A 1080p frame is 8,160 macroblocks, so level 4.1 tops out at about 30 frames per second at 1080p. A 720p frame is 3,600 macroblocks, so 60 fps fits with room to spare.
We checked this with the x264 encoder (ffmpeg 7.0.2) by encoding 20 seconds of test pattern at each combination with -profile:v high -level:v 4.1, 6000 kbps CBR and a 2 second GOP, then reading the result back with ffprobe:
| Resolution and fps | Macroblocks per second | Result at level 4.1 |
|---|---|---|
| 1280x720 at 30 | 108,000 | Within the level |
| 1280x720 at 60 | 216,000 | Within the level |
| 1920x1080 at 30 | 244,800 | Within the level |
| 1920x1080 at 60 | 489,600 | Over the level. x264 warns MB rate (489600) > level limit (245760) and writes level 4.1 in the header anyway |
So 1080p60 "works" in the sense that the encoder produces a file labelled 4.1, but the stream breaks the level it claims. Steam's spec does not say what it does with such a stream. You avoid the question entirely by picking one of these:
- 1280x720 at 60 fps for fast games where motion matters: action, racing, fighting, rhythm.
- 1920x1080 at 30 fps for games where detail and text matter more than motion: strategy, card games, management sims, visual novels.
Whatever you pick, keep the canvas and the output at the same 16:9 size. A 1920x1200 or ultrawide capture scaled into the stream adds black bars or stretches the image.
What bitrate should I use for Steam broadcasting?
The ceiling is 7000 kbps of video plus 128 kbps of audio, sent as constant bitrate. You do not have to run at the ceiling, and on most connections you should not.
The reason is in Valve's stats documentation: Steam only starts transcoding, making smaller 720p, 480p and 360p versions of your stream, once an upload session has more than 10 concurrent viewers. Below that, every viewer receives your original stream. A small store page broadcast spends most of its life under 10 viewers, so a 7000 kbps stream goes as-is to the visitor on hotel Wi-Fi, who sees a spinner. That is one of the reasons people report a broadcast "stuck on loading" (more on that in the loading guide).
| Output | Video bitrate | Total with audio | Upload speed to have |
|---|---|---|---|
| 1280x720 at 30 | 3000 kbps | about 3.1 Mbps | 5 Mbps or more |
| 1280x720 at 60 | 4500 kbps | about 4.6 Mbps | 7 Mbps or more |
| 1920x1080 at 30 | 6000 kbps | about 6.1 Mbps | 9 Mbps or more |
| Steam maximum | 7000 kbps | about 7.1 Mbps | 11 Mbps or more |
The upload column leaves about 50 percent headroom over the stream itself. RTMP runs over TCP, so when the line is saturated the encoder backs up, drops frames, and Steam may close the upload session. If the same connection also carries a game client, a voice call or a cloud backup, leave more.
OBS Studio settings for Steam
OBS is the tool Valve uses in its own setup guide. These are the fields to change; leave everything else at its default. For a full walkthrough with scenes and a test run, see how to stream to Steam with OBS.
| Where in OBS | Field | Value |
|---|---|---|
| Settings, Stream | Service | Custom... |
| Settings, Stream | Server | Upload server from the Steam broadcast page |
| Settings, Stream | Stream Key | RTMP token from the Steam broadcast page |
| Settings, Output | Output Mode | Advanced |
| Output, Streaming tab | Video Encoder | x264, or your GPU's H.264 encoder (NVENC, AMF, Quick Sync) |
| Output, Streaming tab | Rate Control | CBR |
| Output, Streaming tab | Bitrate | 4500 (720p60) or 6000 (1080p30) |
| Output, Streaming tab | Keyframe Interval | 2 s |
| Output, Streaming tab | Profile | high |
| Output, Streaming tab | CPU Usage Preset (x264 only) | veryfast, or faster if the CPU is spare |
| Settings, Output, Audio tab | Audio Bitrate (track used for streaming) | 128 |
| Settings, Video | Output (Scaled) Resolution | 1280x720 or 1920x1080 |
| Settings, Video | Common FPS Values | 60 for 720p, 30 for 1080p |
OBS does not show an H.264 level field for x264 in the standard settings. It lets the encoder pick the level from the resolution and frame rate, which is why staying on one of the two recommended pairs matters. If you need to force it, x264 accepts level=4.1 in the x264 Options field.
Which encoder? If the game and OBS run on the same PC, a GPU encoder (NVENC on NVIDIA, AMF on AMD, Quick Sync on Intel) keeps the CPU free for the game. For a pre-recorded video or a dedicated streaming PC, x264 at veryfast gives slightly better quality at the same bitrate. Both produce H.264 that Steam accepts, as long as the keyframe interval is 2 and rate control is CBR.
Streamlabs Desktop settings for Steam
Streamlabs Desktop is built on OBS, so the values are the same and only a few labels differ. Under Settings, Stream, choose a custom streaming server, then paste the Steam upload server as the URL and the RTMP token as the stream key. Under Settings, Output, switch the mode to Advanced and set rate control to CBR, the bitrate as in the table above, keyframe interval to 2 and the profile to high. Set the output resolution and frame rate under Settings, Video.
If you also stream to other platforms through Streamlabs' own multistream feature, the encode is shared, so every destination gets the same settings. Steam's limits (CBR, 2 second keyframes, 7000 kbps) are within what the other large platforms accept, so the Steam-safe values work for all of them. Which of the two apps suits a Steam stream better is compared in OBS vs Streamlabs for Steam.
vMix settings for Steam
vMix needs one change that Valve calls out by name: by default vMix streams with profile Main and level 3.0, and Steam requires High and 4.1. Open the streaming quality settings (the cog next to the quality preset in the stream window). Set the H.264 profile to High and the level to 4.1, and confirm the keyframe interval is 2 seconds and the bitrate mode is constant. Use the custom RTMP destination with Steam's upload server as the URL and the token as the stream name or key.
Settings for other encoders and hosted services
Steam accepts any software that streams over RTMP, so the same spec applies to hardware encoders, cloud production tools and services that stream a video file for you. When you set up any of them, check four things in their settings or ask their support:
- Can you enter a custom RTMP URL and stream key?
- Can you set the keyframe interval to 2 seconds (or the GOP to 2x the frame rate)?
- Does it use constant bitrate, and can you keep it at or under 7000 kbps?
- Does it send H.264 High profile and AAC-LC audio at or under 128 kbps?
If a tool cannot do the first two, it will not work reliably with Steam. Valve's guide mentions Restream and LiveU Studio as multistreaming options that support Steam. If you stream a finished video, Loopcast encodes every upload to this spec itself (1080p30, H.264 High 4.1, 2 second keyframes, 6000 kbps CBR, AAC 128 kbps), so there is nothing to set; its Steam video specs page lists the values.
For command-line encoders, these are the flags behind our test encodes. They show how the spec maps onto x264 options; they are not a complete streaming setup:
# 720p60, 4500 kbps CBR, 2 s keyframes, AAC 128 kbps
-c:v libx264 -profile:v high -level:v 4.1 -pix_fmt yuv420p
-b:v 4500k -minrate 4500k -maxrate 4500k -bufsize 4500k
-g 120 -keyint_min 120 -sc_threshold 0
-c:a aac -b:a 128k -ar 48000 -ac 2 -f flv
-g 120 is the 2 second GOP at 60 fps (use 60 at 30 fps). -sc_threshold 0 stops x264 from adding extra keyframes on scene cuts, which keeps the spacing exact. Equal -b:v, -minrate and -maxrate is how x264 approximates CBR. Read back with ffprobe, our 720p60 test file showed profile High, level 41, 60 fps and keyframes at 0.03, 2.03, 4.03 and 6.03 seconds.
How do I check that Steam is happy with my settings?
Steam gives you two places to look while you test with the broadcast set to Friends Only:
- The broadcast upload page shows statistics for the running stream and any diagnostic error messages, according to Valve's demo streaming guide. Keep it open in a browser tab while you start the encoder.
- The broadcast history page lists every upload session with its video resolution, start and stop time and any error conditions. Several short upload sessions in a row mean the stream is being interrupted and reconnected. The keyframe and CBR error quoted above appears here.
Run the test for at least 10 minutes. Some problems, such as a connection that cannot hold the bitrate, only show up after the encoder buffer fills. When the history shows one long, clean upload session at the resolution you expect, the encoder side is done. What remains is getting the stream onto the store page, covered step by step in the setup guide.
Questions about Steam broadcast settings
Can I stream to Steam in 1440p or 4K?
No. Steam's spec is H.264 level 4.1 with a maximum of 7000 kbps, which in practice means 1080p at 30 fps at most. Scale higher resolutions down to 1920x1080 or 1280x720 in your encoder.
Does Steam accept HEVC (H.265) or AV1?
No. Valve's spec lists H.264 as the video codec for streams from external software. Pick an H.264 encoder even if your GPU offers HEVC or AV1.
Is VBR allowed if the average stays under 7000 kbps?
Steam asks for constant bitrate. The broadcast history error for broken streams explicitly says to use CBR, so set rate control to CBR rather than VBR or CQP.
What keyframe interval should I use at 60 fps?
Still 2 seconds. In tools that count frames, that is a GOP of 120 at 60 fps and 60 at 30 fps.
Can I use a vertical or 4:3 video?
Steam requires a 16:9 frame. Place a vertical or 4:3 video on a 16:9 canvas with a background, rather than sending it at its own shape.
Sources
- Steamworks: Setting up a stream (RTMP specs, OBS steps, keyframe error, vMix note)
- Steamworks: Broadcast viewership statistics (upload sessions, transcoding above 10 viewers)
- Steamworks: Livestreaming a game demo (upload page diagnostics)
- Our test encodes: ffmpeg 7.0.2 with libx264, 20 seconds of testsrc2 per combination, checked with ffprobe on 24 October 2026.