
You want to run an OBS test before anyone watches: check that your upload holds the bitrate and that nothing goes live by accident. OBS Studio has two built-in tools for this, the bandwidth test in the Auto-Configuration Wizard and Twitch's Enable Bandwidth Test Mode. This guide reads both from the OBS source code at version 33.0.1, the current release (29 October 2026), and checks each platform's own documentation.
Quick answer: On Twitch, add ?bandwidthtest=true to the end of your stream key (or connect your Twitch account in Settings > Stream and tick Enable Bandwidth Test Mode), start streaming and check Twitch Inspector: viewers do not see it and no notifications go out. On YouTube, schedule a Private stream and watch the preview in Live Control Room without clicking Go live. Kick documents no test mode. The wizard's bandwidth test (Tools > Auto-Configuration Wizard) sends 10 seconds of random video per server at 10,000 kbps (6,000 for Twitch); if a frame drops or less than 75% gets through, it suggests 70% of what it measured. During any test, watch Dropped Frames (Network) in View > Stats.
OBS Test Options: Which Test Proves What
| Test | Viewers see it? | What it proves | What it misses |
|---|---|---|---|
Twitch test mode (?bandwidthtest=true) | No | Your real scenes, bitrate and route to Twitch, as long as you like | Other platforms |
| Wizard bandwidth test | Not on Twitch or on YouTube with a connected account. A pasted YouTube key is used as is, with no warning; most other services after a warning | Whether a short burst at the target gets through, and the fastest server | Drops every few minutes; your CPU with your own scenes |
| Scheduled Private YouTube stream | No: it is Private and not live until you click Go live | The whole chain to YouTube, with a preview | Other platforms |
| A real Kick stream | Yes | Kick's own ingest | Privacy |
| Local recording | No | Your encoder and scenes | The network |
| FFmpeg test pattern on a server | Depends on the key | The server's route and CPU | Your home connection |
How the OBS Bandwidth Test Works
Open Tools > Auto-Configuration Wizard, choose "Optimize for streaming, recording is secondary", and on the Stream Information page pick your service, enter the key and tick "Estimate bitrate with bandwidth test (may take a few minutes)". OBS then hides the Server and Bitrate fields for listed services and picks both itself.
What follows is read from AutoConfigStreamPage.cpp and AutoConfigTestPage.cpp at the 33.0.1 tag (master was identical on 4 November 2026):
- Target. "Default test target is 10 Mbps", so 10,000 kbps, then capped by OBS's own service list. Its Twitch entry allows 6,000 kbps, so Twitch tests at 6,000. YouTube rises to 18,000 kbps when your canvas is taller than 1080 pixels and 51,000 above 1440. Custom servers get no cap.
- Test video. OBS swaps your scenes for random noise at 128x128 pixels and 60 fps: x264, CBR, preset veryfast, a keyframe every 2 seconds, 32 kbps audio.
- Key. For Twitch and Amazon IVS, OBS adds
?bandwidthtestto the key; for Restream,?test=true. With a connected YouTube account, OBS creates a throwaway stream named "OBS Studio Test Stream" and tests on that key. - Servers. Twitch with Auto: the three closest. YouTube: primary and backup. Custom: only yours.
- Measuring. Per server, OBS connects, ignores the first 2.5 seconds "due to possible buffering skewing the result", then counts the bytes sent for 10 seconds.
- The rule. If any frame dropped, or the measured rate is under 75% of the target, the result is 70% of the measured rate. Otherwise it is the full target.
- Server choice. The highest result wins; when two are less than 400 kbps apart, the faster connection wins.
The 70% is OBS's rule, not our advice. With example readings:
| Service | Target | 75% line | Measured | Dropped | OBS result |
|---|---|---|---|---|---|
| Custom (Kick) | 10,000 | 7,500 | 6,000 | 0 | 6,000 x 0.7 = 4,200 |
| Custom | 10,000 | 7,500 | 9,800 | 0 | 10,000 |
| Twitch | 6,000 | 4,500 | 5,900 | 3 | 5,900 x 0.7 = 4,130 |
One dropped frame is enough to trigger the 70% rule, which is why a test can suggest much less than your line carried.
Next the wizard tests your encoder and picks the highest resolution whose minimum bitrate fits the result and your CPU. When it tests x264 (software) encoding, it also caps the bitrate per resolution. OBS's comment calls the formula "a totally arbitrary equation that gets the closest to the expected values". Worked out for a 16:9 canvas:
| Output | Minimum bitrate | x264 ceiling |
|---|---|---|
| 1080p, 60 fps | about 5,800 kbps | 8,750 kbps |
| 1080p, 30 fps | about 3,960 kbps | 5,950 kbps |
| 720p, 60 fps | about 2,910 kbps | 4,350 kbps |
| 720p, 30 fps | about 1,990 kbps | 3,000 kbps |
With Prefer hardware encoding, most hardware encoders need a 14% higher minimum. For Kick this matters: through Custom, OBS knows no Kick limit. When the test passes (no dropped frames, at least 7,500 kbps measured), the 10,000 kbps target stays; x264 at 1080p60 then caps it at 8,750, and a hardware encoder keeps all 10,000. Both are above Kick's 8,000 maximum. Set 8,000 or less yourself in Settings > Output, as the Kick bitrate guide shows.
Enable Bandwidth Test Mode: Where It Is and Why It Is Missing
The checkbox Enable Bandwidth Test Mode sits in Settings > Stream, and OBS only shows it when Service is Twitch and your account is connected with Connect Account. With a pasted stream key, any other service, or after Disconnect Account (which also unticks it), it is hidden (OBSBasicSettings_Stream.cpp).
Ticked, it makes OBS add ?bandwidthtest=true to the key it gets from Twitch (OAuth.cpp), and Start Streaming first asks "Start Bandwidth Test?":
You have OBS configured in bandwidth test mode. This mode allows for network testing without your channel going live. Once you are done testing, you will need to disable it in order for viewers to be able to see your stream.
Without a connected account, do it by hand. Twitch's developer docs give the URL as rtmp://<ingest-server>/app/<stream-key>[?bandwidthtest=true] and say the parameter "disables live viewing of the stream. It is used to verify bandwidth health on Twitch Inspector." In Settings > Stream, type the suffix after your key:
live_0000000_xxxxxxxxxxxx?bandwidthtest=true
OBS gives no prompt for a typed suffix, so remove it yourself afterwards. With Enhanced Broadcasting on, OBS carries query parameters "such as bandwidthtest" from your key to the multitrack connection, so the suffix still applies.
Then log in at inspector.twitch.tv. Its "run a stream test" panel gives the same steps and says the flag "allows you to broadcast without appearing online to viewers or sending notifications." Inspector shows live data during the test and lists your recent streams with the Twitch server they reached and any unstable events; open one to see its bitrate over time.
Test Without Going Live on YouTube and Kick
YouTube. YouTube's help describes two ways to stream from an encoder. On the Stream tab, starting OBS puts you live: "A watch page is now created for your stream, and you're now live on YouTube. Notifications will be sent". For a test, use Manage > Schedule stream, set visibility to Private (adults default to Public), put that stream's key in OBS and start streaming. YouTube's steps then say to "wait for the stream preview to show up, and then click Go live": check the preview, skip Go live, and stop streaming in OBS. Streams under 12 hours are archived automatically, so delete a test that did go live.
The wizard follows the same split. With a connected account it uses its "OBS Studio Test Stream" key; with a pasted YouTube key it shows no warning and tests on that key, so paste a Private scheduled stream's key. Bitrates per resolution are in the YouTube encoder settings guide.
Kick. Kick's help center describes no test mode; whatever reaches your Kick key is live. Kick is not in OBS's service list, so you use Custom, and for any service other than Twitch, YouTube and Amazon IVS the wizard warns:
The bandwidth test is about to stream randomized video data without audio to your channel. If you're able, it's recommended to temporarily turn off saving videos of streams and set the stream to private until after the test has completed. Continue?
So test your upload and settings on Twitch test mode or a Private YouTube stream first, knowing the route to Kick can differ. Check the KICK System Status page before blaming your setup, and if Kick lags, follow Kick's advice: lower the bitrate by 1,000 kbps and test again. Disconnects are covered in OBS keeps reconnecting to Kick.
How Long to Test and What to Read in OBS Stats
Open View > Stats. Three lines show where a problem sits:
| Stats line | What it counts | Usual cause |
|---|---|---|
| Dropped Frames (Network) | Frames that never left your PC | Upload too slow or unstable for the bitrate |
| Skipped frames due to encoding lag | Frames the encoder finished too late | CPU or encoder preset too heavy |
| Frames missed due to rendering lag | Frames OBS drew too late | Heavy scenes or overloaded graphics |
Each line reads "missed / total (percent)", marked as a warning above 1% and as an error above 5% (OBSBasicStats.cpp). Kick explains the first: dropped frames "mean your encoder is producing video faster than your internet can send it", and a climbing count means "your bitrate is too high for your connection or your network is unstable." For fixes, see OBS dropped frames: fix your upload.
No platform names a test length. The wizard's 10 seconds show if your line carries the rate at all. Problems that come and go, such as Wi-Fi interference or the peak-hour slowdowns Kick warns about, need a longer run: use Twitch test mode or a Private YouTube stream for as long as a normal session, at the hour you usually go live.
Speed Test or Stream Test?
OBS has no separate speed test; the wizard's bandwidth test is the closest it gets. A speed test site is a fair first check if you read it by the platforms' rules. Kick: "your upload speed should be at least twice your stream's bitrate". Amazon IVS: "Plan to allocate 50% more bandwidth than the minimum required", to absorb bitrate swings.
| Video bitrate | Kick's rule (2x) | IVS's rule (+50%) |
|---|---|---|
| 3,000 kbps | 6 Mbps | 4.5 Mbps |
| 6,000 kbps | 12 Mbps | 9 Mbps |
| 8,000 kbps | 16 Mbps | 12 Mbps |
Audio comes on top. A speed test is a short burst; a stream test holds a constant bitrate to the ingest you actually use, so it can fail on a line that passed. Settings per platform are in OBS best settings for streaming.
Test From a VPS With an FFmpeg Test Pattern
Before you move a stream from your PC to a server, test from the server. FFmpeg's lavfi input generates a pattern and a tone with no video file. This sends 1080p60 at 6,000 kbps CBR with 2 second keyframes (-g 120 at 60 fps) to Twitch in test mode:
ffmpeg -re -f lavfi -i "testsrc2=size=1920x1080:rate=60,noise=alls=20:allf=t+u" \
-re -f lavfi -i "sine=frequency=1000:sample_rate=48000" \
-c:v libx264 -preset veryfast -pix_fmt yuv420p \
-b:v 6000k -minrate 6000k -maxrate 6000k -bufsize 6000k -nal-hrd cbr -g 120 \
-c:a aac -b:a 160k \
-f flv "rtmp://INGEST/app/STREAM_KEY?bandwidthtest=true"
Replace INGEST with a Twitch ingest server and STREAM_KEY with your key. -re reads input at its native frame rate, like a live source. testsrc2 shows a color pattern, a scrolling gradient and a timestamp; for color bars, use smptehdbars=size=1920x1080:rate=60. The noise filter adds detail that changes every frame, so the encoder has something to fill the bitrate with. If FFmpeg's progress falls behind real time, the CPU cannot encode this live: try -preset superfast or 30 fps.
This tests the server's route and CPU, not your home line. To run OBS itself on Linux, see headless OBS on a Linux VPS, and for always-on streams, OBS auto-reconnect. At Space-Node, a streaming VPS comes with OBS Studio pre-installed and opens in your browser, and a Linux VPS in our EU data center runs the FFmpeg test above.
FAQ
What is Bandwidth Test Mode in OBS?
A Twitch-only checkbox in Settings > Stream. It makes OBS add ?bandwidthtest=true to your Twitch key, so you stream to Twitch without your channel going live and check the connection in Twitch Inspector. OBS asks "Start Bandwidth Test?" at every start until you untick it.
Why can't I see Enable Bandwidth Test Mode?
OBS only shows it when Service is Twitch and your Twitch account is connected. With a pasted key or another service it is hidden. Type ?bandwidthtest=true after your key instead.
Does the OBS bandwidth test go live on my channel?
Not on Twitch, where OBS adds a test suffix, and not on YouTube with a connected account, where it uses a throwaway key. With a pasted YouTube key it tests on that key without a warning, so use a Private scheduled stream's key. On other services, Kick through Custom included, it streams random video to your channel after a warning.
How do I test a stream in OBS without going live?
On Twitch, use Bandwidth Test Mode or the suffix and watch Twitch Inspector. On YouTube, schedule a Private stream and check the preview without clicking Go live. To test only your encoder and scenes, record locally and watch View > Stats.
Does OBS have a test pattern?
Not as a built-in source. OBS's code has test sources (random noise, a sine wave), but they are only built with the ENABLE_TEST_INPUT option, which is off by default. Use an Image source with a test card, a Media Source with a test clip, or FFmpeg's testsrc2 or smptehdbars.
How long should a stream test run?
No platform gives a number. The wizard's 10 seconds per server only show if your line can carry the rate. For drops that come and go, test as long as a normal session, at the hour you usually stream.
Sources
All opened on 4 November 2026:
- OBS Studio source code at tag 33.0.1: AutoConfigTestPage.cpp, AutoConfigStreamPage.cpp, AutoConfig.cpp, TestMode.hpp, OBSBasicSettings_Stream.cpp, OAuth.cpp, OBSBasic_Streaming.cpp, MultitrackVideoOutput.cpp, OBSBasicStats.cpp, OBSBasic.ui, en-US.ini, rtmp-common.c, services.json, test-input CMakeLists.txt
- OBS Studio 33.0.1 release
- Twitch: Video broadcast developer docs, Twitch Inspector
- YouTube Help: Create a YouTube live stream with an encoder
- Kick Help Center: Why is my stream lagging or buffering on KICK?
- Amazon IVS: Streaming configuration
- FFmpeg documentation: filters (testsrc2, smptehdbars, sine, noise), lavfi input device, ffmpeg -re, libx264 and rate control options, RTMP protocol