Settings to copy
These values fit a channel with a 5 Mbps RTMP ingest, which is what each channel takes on both the PRO and Platinum plans. Set them once in your encoder profile and leave them alone between shows.
| Setting | Value | Why |
|---|---|---|
| Resolution | 1920x1080 | The top of what the channel carries |
| Frame rate | 30 (or 25 where mains power is 50 Hz) | Spends the bits on detail, not on extra frames |
| Video codec | H.264 | The codec HLS players everywhere decode |
| Rate control | CBR | A steady feed the line can carry |
| Video bitrate | 4,000 to 4,500 kbps | Leaves room under 5 Mbps for audio and overhead |
| Keyframe interval | 2 seconds | Clean segment starts for HLS |
| Audio | AAC stereo, 128 kbps | Inside the range Apple's HLS guidance gives for stereo AAC |
| Sustained upload | About 6 Mbps or more | Bitrate no higher than 75% of measured upload |
Add video and audio together before you compare with the channel. 4,500 kbps of picture plus 128 kbps of sound is about 4.6 Mbps, which sits under the 5 Mbps ingest with a small margin. Push the video to 5,000 kbps and the total no longer fits.
Why 1080p sits at the lean end here
Apple's HLS authoring specification gives an example ladder whose 1080p H.264 variants average 6,000 kbps or 7,800 kbps, and whose 720p variants average 3,000 kbps or 4,500 kbps. A 5 Mbps channel therefore carries 1080p, but with less data per frame than those reference encodes. That is workable for a pulpit, a lectern, a panel or a slide deck. It shows strain on fast pans, confetti, water and crowds.
So you choose where the bits go. You can keep 1080p and hold the frame rate at 30 or 25, which gives each frame more data. Or, for sport and dance, drop to 720p and run 60 or 50 frames a second, which keeps motion smooth at the cost of fine detail. Both are honest choices; the wrong one is 1080p at 60 frames squeezed into 4.5 Mbps.
Apple's guidance for live content asks for 60 or 59.94 fps in NTSC regions and 50 fps in PAL regions, and it says to deinterlace 30i sources to 60p. Read that as the target for a full bitrate ladder. At a single 5 Mbps feed, frame rate is the first thing you trade.
Upload headroom, measured honestly
The OBS project's own troubleshooting page suggests starting with a bitrate of 75% of your total upload speed, and it names dropped frames as a sign the connection cannot hold the bitrate you set. Work backwards from the bitrate you want:
| Video + audio total | Upload you should measure |
|---|---|
| About 4.6 Mbps (1080p) | About 6.2 Mbps sustained |
| About 3.1 Mbps (720p) | About 4.2 Mbps sustained |
| About 2.1 Mbps (540p) | About 2.8 Mbps sustained |
- Measure at the time of day you broadcast, from the encoder machine, over the cable you plan to use.
- Use a wired connection. The OBS documentation calls Wi-Fi potentially unstable for streaming.
- Count what else shares the line: cloud backups, phones on the guest network, a second camera uploading clips.
- Speed tests sample a few seconds; a two-hour service runs for two hours. Keep the margin.
Constant bitrate and the 2-second keyframe
Use CBR for the live feed. Variable bitrate saves space in a recording, but on a live line its peaks arrive exactly when the scene gets busy, which is also when your upload is least able to absorb them. The live encoder settings published by the large video platforms also list CBR and a keyframe every 2 seconds.
Set the keyframe interval to 2 seconds. Apple's specification recommends an IDR frame every two seconds and requires each HLS video segment to begin with one, with target segment durations of 6 seconds. A 2-second interval lines up with that cleanly, so viewers who join mid-show get a picture quickly. In OBS the field is in seconds; in a raw x264 or FFmpeg setting it counts frames, so at 30 fps the same interval is 60.
Setting it up in OBS Studio
- Open Settings, Output and set Output Mode to Advanced, so Rate Control and Keyframe Interval are visible.
- On the Streaming tab pick your H.264 encoder, set Rate Control to CBR, Bitrate to 4500 and Keyframe Interval to 2.
- On the Audio tab set the track you stream to 128.
- Open Settings, Video: Base and Output resolution 1920x1080, Common FPS Values 30 (or 25).
- Paste the address and stream key your control panel shows, as set out in the OBS Studio guide in our knowledge base.
- Start streaming and let it run for ten minutes before the audience arrives.
How to confirm it worked: the bitrate reading in OBS's status bar should hover near 4,600 kbps without sagging, and the dropped-frames count should stay at or very near zero. Then play the channel's HLS link on a phone over its cellular connection, off your building's Wi-Fi, for a full minute. Using vMix, Wirecast or FFmpeg instead? The same numbers apply; the knowledge base has a setup guide for each.
What to drop to on a weak connection
When the upload will not hold 1080p, lower resolution and bitrate together, in steps taken from Apple's example ladder. Do not keep 1080p and simply cut the bitrate: a starved 1080p picture looks worse than a well-fed 720p one.
| Sustained upload | Resolution | Video bitrate | Frame rate |
|---|---|---|---|
| About 6.2 Mbps or more | 1920x1080 | 4,000 to 4,500 kbps | 30 or 25 |
| About 4.2 to 6.2 Mbps | 1280x720 | 3,000 kbps | 30 or 25 |
| About 2.8 to 4.2 Mbps | 960x540 | 2,000 kbps | 30 or 25 |
OBS also offers a dynamic bitrate checkbox, marked Beta, under Settings, Advanced, Network. It lowers the bitrate rather than dropping frames when the line struggles. The OBS documentation is plain that this does not fix the cause and reduces quality, so keep it as a backstop on a line you already trust, never as the plan for a poor one.
When it goes wrong
- Dropped frames climbing: the network, not the computer. Lower the bitrate one step, move to a cable, stop other uploads.
- Frames skipped for encoding lag: the computer cannot keep up. Use a hardware encoder if you have one, choose a faster preset, or lower the output resolution.
- Blocky picture on movement, steady elsewhere: too little bitrate for the motion. Drop to 720p, or hold the frame rate at 30.
- Long black wait when a viewer joins: check the keyframe interval is 2 seconds, not left on automatic.
If the settings look right and the channel still misbehaves, open a ticket or a live chat with the time of the show and your encoder settings.
Where a 1080p channel runs
Our live video streaming plans take RTMP from a hardware encoder or from OBS, vMix, Wirecast or Larix and play it as HLS over HTTPS in a player you can embed, free of ads. PRO gives one channel with 5 Mbps ingest at up to 1080p and as many as 1,000 simultaneous viewers, and the traffic they make is not counted. Platinum gives two channels, each having its own 5 Mbps ingest, and every viewer gets the stream from the closest of the five CDN cities, from San Francisco and Miami across to Bucharest; the plan page lists all five. Paid plans come with round-the-clock phone and live chat help.
The free plan is for wiring up your encoder and player and checking the chain end to end before you move to a paid plan; your channel stays the same when you upgrade from the dashboard. Paid plans also add a Samsung and LG TV app that belongs to you; the TV and mobile app publishing guides cover getting it into the stores.