Start with Twitch’s conventional baseline for OBS: use CBR and a 2-second keyframe interval, then choose a resolution, frame rate and bitrate your connection and computer can sustain. The right settings are the ones that stay stable while you play or produce your actual stream, not the largest numbers in a preset.
Treat the figures below as starting points, not guarantees. Change one setting at a time, test with the same workload you expect to stream, and keep the configuration that delivers reliably without overloading your network or machine.
Start with Twitch’s baseline output guidance
For a conventional single-output stream, Twitch lists example profiles including 1080p at 60 frames per second (fps) with 6000 kbps, 720p at 60 fps with 4500 kbps, and 720p at 30 fps with 3000 kbps. These examples give you a sensible place to begin comparing options; they do not mean every connection, ingest route or computer can sustain them. Check Twitch’s current Broadcasting Guidelines before setting up, because platform guidance and features can change.
Twitch’s advice puts stable delivery ahead of pushing video quality until frames drop or the connection reaches its limit. That matters more in practice than whether a profile looks impressive on paper. A stream that holds together through a demanding match is a better starting point than one that looks sharper in a quiet scene but breaks down in action.
The figures are only useful in context. A 60 fps output carries more motion detail than 30 fps, but asks more of the encoder and connection. A higher output resolution carries more image detail, but also needs more bitrate to avoid visible compression. Your graphics card, processor, game settings, upload traffic from other devices and route to Twitch’s ingest server all affect what is sustainable.
If you are comparing profiles, keep the trade-offs visible:
| Example output | Twitch-listed bitrate | What to test on your system |
|---|---|---|
| 1080p60 | 6000 kbps | Whether the connection and encoder hold steady during fast scenes |
| 720p60 | 4500 kbps | Whether smoother motion is worth the bandwidth and encoding load |
| 720p30 | 3000 kbps | Whether lower motion smoothness is acceptable for your content |
The table reflects Twitch’s listed examples, not a recommendation that you force your system to match them. Use the profile closest to your target as a trial setting, then move down if performance or delivery is unstable. If you need background on what bitrate does, this guide to video encoding settings for a live stream explains the relationship between bitrate and image data in practical terms, although its platform examples concern YouTube rather than Twitch.
Set encoder mode and keyframe interval
In OBS, open Settings, then Output, and choose an output mode that exposes the streaming encoder settings. For a standard Twitch output, set rate control to CBR and set the keyframe interval to 2 seconds. CBR keeps the encoded bitrate predictable instead of letting it swing sharply between a quiet scene and a busy one. Twitch’s conventional guidance uses this predictable delivery pattern.
The encoder itself can be hardware-based or software-based. Hardware encoders use a specialised component in your graphics card to take work away from the CPU. Modern versions generally provide good quality with modest performance impact, but results differ by generation and machine. Try the hardware encoder available on your system, then compare it with x264 only if you can test both without compromising the stream.
x264 encodes on the CPU. Twitch suggests beginning with the veryfast preset; heavier presets demand more CPU work, and Twitch cautions that presets above Faster require CPUs with six or more cores. Those presets are not an automatic quality upgrade for every setup: a slower preset can produce a better encode at the same bitrate, but it can also leave too little processor capacity for a game, browser sources, alerts or other software. See the OBS overview guide for the current descriptions of OBS controls and workflow.
Make a short test with your normal game and scene collection before deciding that one encoder is better. Watch OBS’s performance statistics and the game itself. If the game stutters when you switch to x264, or OBS reports encoding lag, go back to hardware encoding or reduce the workload. If the hardware encoder is not available or behaves poorly, x264 may be worth testing, but choose a preset that leaves capacity for everything else you run.
Keep the keyframe interval at 2 seconds for the conventional configuration rather than adjusting it to chase a vague quality improvement. Twitch uses consistent keyframes as part of its expected delivery behaviour, and a consistent interval also helps quality options transition smoothly when they are available to viewers.
Choose resolution and frame rate for the workload
OBS separates Base (Canvas) Resolution from Output (Scaled) Resolution. The canvas is the working space for arranging sources; it is often the resolution of the game or monitor. The output is the frame size sent to Twitch. For example, you can arrange sources on a 1920 by 1080 canvas and send a 1280 by 720 output. That means the stream itself is 720p even if the game display is 1080p.
Choose output resolution and fps together. A higher resolution needs more bitrate to retain detail, while higher fps means more frames to encode and send each second. A fast-action game can benefit from 60 fps if the computer and connection can maintain it. For a slower strategy game, a talk stream, or a screen-based tutorial, 30 fps may be a reasonable test if it leaves more room for stability or image detail at a given bitrate.
Do not assume 1080p is always the right target. Viewers on smaller screens or variable connections may value a consistent stream more than additional detail. Likewise, do not assume 720p is always enough: a game with small text or fine visual detail may lose legibility after scaling and compression. Test a representative scene and inspect the result on a separate device if possible.
Try changes in a controlled order. First pick a frame rate suited to the motion in your content. Then choose an output resolution the machine can render and encode while the game is running. Finally set a bitrate that your Twitch route can sustain. If the system cannot maintain the output, try 30 fps, a lower output resolution, or both, then test again. The resolution guide offers useful background on scaling and image size, but Twitch’s actual delivery and your workload should decide your settings.
A lower output is not a failure. If dropping from 1080p60 to 720p60 or 720p30 stops frame loss and keeps the stream watchable, that is an improvement in delivered quality. Leave the canvas as needed for scene layout; adjust the output size to reduce what OBS must send and encode.
Set a sustainable bitrate for the connection
Bitrate is the amount of encoded video data sent each second. For live streaming, the number you enter in OBS must fit within the upload capacity available to the stream, while leaving room for other devices, voice chat, game traffic and normal variation in the connection. A speed test measures a moment and a route to a test server; it does not prove that the path to Twitch’s chosen ingest server will remain steady throughout a stream.
OBS’s troubleshooting guidance gives about 75% of total upload speed as a starting point when diagnosing connection drops. Treat this as a cautious heuristic, not a universal formula: it can still be too high if the route is unstable or other traffic competes for upload. Read OBS’s connection troubleshooting steps alongside the result of your own tests. If the connection cannot sustain the chosen bitrate, lower it and test again rather than trying to make the network carry more than it can reliably deliver.
Start with a Twitch-listed profile only if your available upload and initial test suggest it is plausible. Leave headroom rather than setting OBS at the full measured upload speed. If other people at home use the connection, test when they are likely to be online too. A profile that works on an empty network may fail when a cloud backup or video call begins.
If OBS reports dropped frames but the game and preview otherwise look smooth, first suspect an unstable or insufficient connection to the ingest server, rather than immediately changing the encoder. Lower the bitrate and try a different Twitch server. OBS notes that Windows users can use TwitchTest to compare server quality. A different server may improve the route, but it cannot compensate for inadequate upload capacity or congestion inside your local network.
Dynamic bitrate can help OBS react to congestion by changing the bitrate, but it does not repair the underlying connection problem and can reduce image quality while it adapts. Use it as a way to avoid a hard interruption if appropriate, not as a reason to keep an unnecessarily ambitious target. When a stable lower bitrate is available, predictable quality may be preferable to frequent swings.
Test with the same game and workload
A settings test only means something if it resembles the stream you intend to make. A quiet desktop does not reveal what happens when a game loads a new area, a browser source animates, an alert appears and voice chat is active. Before changing settings, record the current output resolution, fps, bitrate, encoder and any OBS warnings. That gives you a baseline for comparison and a way to undo a change that made things worse.
Run a private or otherwise non-public test, as Twitch and OBS recommend testing before relying on a setup. Use the same game, graphics settings, scenes, overlays and applications you plan to have open on stream. Include a demanding moment: a busy fight, a fast camera pan, a crowded scene or whatever typically makes your content harder to render. Let the test run long enough to observe more than the initial connection, and check performance during the busy portion rather than only after it ends.
Change one variable at a time. If you lower resolution and bitrate together, you may improve stability but will not know which change mattered. A practical sequence is to choose encoder mode, test it, settle the frame rate, test again, and then adjust output resolution or bitrate as needed. Keep a small note of each setting and what OBS reported, so you can return to a known stable configuration.
Assess the result from both sides. In OBS, note rendering and encoding warnings, dropped frames, and whether the stream preview remains steady. On a separate viewer device, check whether motion, text and audio are acceptable. Do not use only the OBS preview as evidence: it shows the local composition, not necessarily how a viewer’s connection or Twitch playback will present the stream.
This discipline is useful whether you stream a competitive game, a drawing session or a local event. The test does not prove the setup will never fail, because networks and workloads change, but it lets you make decisions from observed behaviour rather than from a preset or an online claim that one setting is best for everyone. For a broader look at long-running OBS reliability, see how to prevent OBS from stopping a 24/7 YouTube stream; the causes and service differ, but the habit of testing the actual workload transfers.
Read stream health and correct dropped frames
Dropped frames usually point to a connection problem between OBS and the selected ingest server. Rendering lag means OBS is struggling to render frames, often because the game or sources are using too much graphics capacity. Encoding lag means the encoder cannot process frames quickly enough. These symptoms need different responses, so read the OBS statistics rather than treating every hitch as a bitrate problem.
If dropped frames rise while rendering and encoding remain healthy, reduce bitrate first and test the route. Try another Twitch ingest server as well. If you are on Wi-Fi, a wired connection can be a useful comparison because it removes one source of local variability, though it will not fix an overloaded broadband connection or an unstable route beyond your home.
If rendering lag appears, lower the game’s graphics load or cap its frame rate so it does not consume all available GPU capacity. OBS needs resources to compose scenes as well as the game. If encoding lag appears, test a hardware encoder, a less demanding x264 preset, lower fps or a smaller output resolution. Make one change, repeat the same test, and compare the statistics.
OBS has guidance for hardware encoding, including the trade-off between CPU load and encoder generation. Do not assume that the newest-sounding encoder option is automatically the best for your particular card, driver and game. The useful result is the combination that stays within capacity during the demanding part of the stream.
Keep a stable fallback profile available. If a new game update, browser source or network condition changes performance, revert first to the last configuration that behaved well, then diagnose from there. If you need your computer to be off during an always-on YouTube loop rather than broadcasting from OBS, StreamNeo removes the need to keep a local machine running for that specific file-based workflow; it is not a solution.
Know when Twitch’s other workflows change the advice
The settings in this article describe a conventional single-output Twitch stream. Twitch also offers Enhanced Broadcasting, which can automatically configure a stream and provide multiple client-side encodes. Twitch says Enhanced Broadcasting is required for Dual Format Streaming and its 2K workflow. If you are eligible and intend to use those features, manual single-output advice may not describe the entire setup; follow Twitch’s Enhanced Broadcasting documentation for current setup steps and requirements.
Viewer quality choices also depend on transcoding availability. OBS explains that Twitch transcoding lets viewers select different quality levels, but access is tiered: Partners are guaranteed full access, Affiliates receive it as available with priority, and other streamers receive it as available. Do not base your own stability on an assumption that every viewer can select a lower-quality version. The OBS explanation of Twitch transcoding sets out why consistent keyframes matter for transitions between quality options.
The feature path and its compatibility can change, so verify Twitch’s current documentation for your OBS version and operating system rather than extrapolating from a conventional configuration. If you are not using Enhanced Broadcasting, continue with the single-output workflow: choose a sustainable profile, test it under real load, and respond to the actual health indicators OBS reports.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
What are good OBS settings for Twitch?
For a conventional single-output stream, begin with CBR and a 2-second keyframe interval, then test a Twitch-listed resolution, frame rate and bitrate that your system can sustain. Twitch’s listed profiles are starting points, not guarantees for every connection or computer.
What bitrate should I use for Twitch?
Choose a bitrate that leaves upload headroom and remains stable to the ingest server during your real workload. OBS’s roughly 75% of total upload speed is a troubleshooting starting point, not a promise; lower the bitrate if you see connection-related dropped frames.
Why am I dropping frames on Twitch?
If OBS reports dropped frames while rendering and encoding are otherwise healthy, the connection to the ingest server may be unstable or unable to keep up. Lower the bitrate and test a different Twitch server before changing resolution or encoder settings.
Should I stream at 1080p60 or 720p30?
Neither is best for every channel. 1080p60 gives more detail and smoother motion but demands more from the connection and computer; 720p30 reduces that workload, so test both only if your content and system justify it, then keep the stable result.