A reliable live stream preflight checklist helps you catch the problems viewers notice first: missing audio, the wrong scene, broken alerts, poor framing, or a stream that never reaches the platform. Use this guide before every broadcast, then repeat the relevant checks whenever you change gear, software, scenes, or platforms.
Overview
A preflight check is a short, repeatable test of your complete broadcast chain. It starts with the physical setup, moves through OBS Studio or your chosen streaming software, and ends with a platform-level check. The goal is not to redesign your stream before every broadcast. It is to confirm that the version you are about to publish works as expected.
Keep a copy of this stream test checklist near your desk, or turn it into a checklist in your creator workflow tool. A simple system works best: mark each item as passed, note any failure, and record the fix. If the same issue appears repeatedly, it belongs in a monthly setup review rather than in your last-minute routine.
For a first-time setup, use this checklist alongside the OBS Studio setup guide for beginners. For an established channel, focus on changes since your last broadcast. A scene or browser source that worked last week may still need testing after an update, a computer restart, or a change to your capture hardware.
Checklist by scenario
Before every stream
- Confirm the broadcast plan. Check the correct platform, account, category, title, description, tags, and scheduled start time. Make sure the title matches what you are actually doing on stream.
- Inspect the camera. Confirm the intended camera is selected, the lens is clean, the framing is stable, and your face is visible under the current lighting. Check that the camera is not being used by another application.
- Check the microphone. Speak at your normal volume and watch the input meter. Listen for clipping, excessive background noise, hum, keyboard noise, or a delayed monitoring signal. Your microphone should be clearly distinguishable from game or desktop audio.
- Verify the active scene. Open the scene you intend to use first. Confirm that the game capture, display capture, camera, overlays, chat panel, and other sources are visible in the right order.
- Test transitions. Move between starting, main, break, ending, and any special scenes you expect to use. Look for hidden sources, incorrect layouts, frozen media, or transitions that take longer than expected.
- Trigger a test alert. Use the alert service's test function where available. Confirm that the animation loads, the sound is audible, the text is readable, and the alert does not cover important gameplay or information.
- Review chat and moderation. Open chat as a viewer if possible, confirm that messages appear, and check that moderators or chat moderation tools are active. Keep a way to pause, restrict, or remove disruptive messages without leaving the broadcast.
- Confirm recording and clip settings. If you record locally, check the destination drive, available storage, and file format. If you plan to create clips later, make sure the moments you want to preserve can be found easily in the recording or platform dashboard.
- Check stream health. Confirm that your streaming software shows a stable connection and that the platform dashboard recognizes the incoming broadcast. Do not rely only on the local preview.
After changing gear, software, or scenes
Run a deeper test whenever you install a new microphone, camera, capture card, graphics driver, plugin, browser source, or streaming software update. Test each input separately before testing the whole scene. This makes it easier to identify whether the problem is the device, its permissions, the source configuration, or the final mix.
Browser sources deserve special attention. Reload each source, check its dimensions, and trigger animations or alerts manually. A browser source can appear in the editor while failing to load correctly in the live scene, so verify it in the same scene and resolution you will broadcast.
Before an important or sponsored broadcast
Allow extra time for a private rehearsal. Read the opening, demonstrate the primary segment, test every scene transition, and confirm that any sponsor message or product display is visible and accurate. Ask a trusted viewer to watch the test from another device and report problems with volume, readability, buffering, or layout.
Save a backup version of your key scenes before making last-minute edits. Also write down a fallback plan: a simple camera-and-microphone scene, a static holding screen, and a way to communicate with viewers if the main application or game capture fails.
What to double-check
Audio balance
Audio is easier to evaluate in a recording than through headphones while you are working. Record a short sample containing speech, game audio, an alert, and a scene transition. Listen back for sudden level changes, duplicated audio, echo, or sources that disappear when you switch scenes. If audio remains inconsistent, use the steps in How to Fix Common Stream Audio Problems.
Video and capture sources
Check that the capture source shows the intended application rather than a blank screen, the desktop, or a different window. Confirm that the game or application is running at a resolution your layout can display cleanly. Look at the edges of the frame for cropping, black bars, or overlays covering important information.
Encoding and connection
Use the streaming platform's current recommendations as the reference for resolution, frame rate, bitrate, encoder, and keyframe settings. These options can vary by platform, account, connection, and hardware, so avoid copying settings from an old guide without checking the current software and platform documentation. Run a short test and watch for dropped frames, rendering delays, encoder overload, or an unstable upload connection.
A local preview can look perfect while the delivered stream has a problem. When possible, monitor the broadcast from a separate device or ask a moderator to check the viewer-facing version. This is especially useful when you multistream or use different layouts for Twitch, YouTube Live, TikTok Live, or Kick.
Viewer experience
Read the opening message as a new viewer would. Is it clear what is happening, where to participate, and what to expect next? Check that on-screen text is large enough to read, alerts are not too frequent or distracting, and chat is visible to the people managing it. A technically stable stream can still feel unfinished if the first minute is silent or the wrong scene is displayed.
Common mistakes
- Testing only the preview. The editor view does not confirm that the platform receives the correct video and audio. Check the viewer-facing broadcast too.
- Checking levels without listening back. Meters show volume, not clarity. A signal can be loud enough and still contain echo, distortion, or distracting noise.
- Assuming every scene uses the same sources. Camera, microphone, and desktop audio may be configured differently across scenes. Test each scene you will actually use.
- Leaving alerts until the broadcast begins. Alerts depend on browser sources, permissions, network access, and audio routing. Trigger them before going live.
- Changing several things at once. If you replace the microphone, update OBS, and redesign the overlay together, troubleshooting becomes slower. Test one major change at a time where practical.
- Ignoring storage and backups. A full drive or failed recording can remove the easiest path to clips and highlights. Check storage before recording long sessions.
- Having no fallback scene. A simple scene gives you somewhere to send viewers while you restart a game, fix capture, or investigate a connection problem.
A failed check is useful information, not a reason to abandon the broadcast. Identify the affected component, switch to the fallback if necessary, and log the fix. For growth and repurposing, reliable recordings matter too: see How to Repurpose a Livestream Into Shorts, Clips, and YouTube Videos for a workflow that starts after the broadcast.
When to revisit
Use the short version of this checklist before every stream. Repeat the full version after changing hardware, installing software updates, editing scenes, switching platforms, changing internet equipment, or adding a new alert, plugin, or browser source. Run another full test before a seasonal schedule change, a long event, a collaboration, or a broadcast tied to a sponsor.
Review your failure notes at least monthly. Look for patterns such as recurring audio drift, capture failures, missing alerts, or repeated connection warnings. Fix the underlying workflow instead of relying on memory. Update the checklist when OBS, your platform dashboard, or a major tool changes its menu paths or behavior; verify current encoding recommendations at the same time.
To put this into practice, create three saved routines today: a five-minute pre-stream check, a deeper post-change test, and an emergency fallback procedure. Run the five-minute version before your next broadcast, record a short sample, and ask one moderator or trusted viewer to verify the delivered stream. Then link the completed checklist to your regular stream schedule so preparation becomes part of the broadcast—not a last-minute scramble.