Configure a Twitch broadcast, test scene and audio behavior, use Inspector for network checks and verify the viewer experience before a planned stream.
Choose the content, intended orientation, devices and interaction needs. Confirm access to the correct Twitch account and its current broadcast settings. Record the encoder, output dimensions and frame-rate choice. Reduce the dimensions to an aspect ratio to check the intended layout; resolution alone does not choose a bitrate.
Use OBS’s Auto-Configuration Wizard as a starting point, then check the current Twitch guidance for the actual broadcast mode. Confirm encoder support, output scaling, audio routing and a stable network path. Save the configuration identity so later tests compare the same settings.
Create scenes for the actual running order, including a holding or break state. Add the intended game, window or camera sources and verify what is visible when a window closes or changes. Check source order, crop and transitions. Disable private notifications and test that a holding scene does not keep unintended audio live.
Record normal speech, louder speech, gameplay or presentation audio and a scene change. Listen on headphones and another playback device for missing channels, clipping, echo and voice balance. Estimate recording storage from its own combined bitrate or PCM format, then check actual free space and file playback.
Follow Twitch Inspector’s bandwidth-test instructions, including the bandwidthtest flag when entering a stream key manually. This test avoids appearing live to viewers; it is not a private audience stream. Inspect network stability and OBS’s rendering and encoding statistics under representative content. Keep the stream key out of shared notes and screenshots.
After the technical test, prepare a deliberate audience rehearsal or the planned broadcast with the correct visibility and test flag state. Check playback, audio, chat or moderation and the transition to a break. Record settings, observed problems and the recovery action. Download the rehearsal note and repeat the checks after material scene or encoder changes.
Check the ratio of the chosen output dimensions.
Convert the chosen output FPS to a reference interval.
Estimate storage from the recording’s own bitrate or PCM format.
Write and download the scene, test and recovery notes.
Loading your checklist…
OBS documents its configuration wizard, sources, audio setup and testing process. Validate the resulting settings with your own content and equipment.
Inspector documents the bandwidthtest stream-key flag for a technical test that does not appear online or notify viewers.
Keep these task-specific records with the tested version and review date.
| Record | Include | Verify |
|---|---|---|
| Configuration | Encoder, dimensions, FPS, audio and OBS version | Same settings as the tested run |
| Technical test | Network drops, render lag and encode lag | Investigate the observed category |
| Viewer check | Playback, audio, chat and holding scene | Record device, time and recovery action |
Use the busy content and scene transitions expected during the real broadcast.
A bandwidth test does not prove the full viewer, chat and moderation experience.