This live streaming setup checklist helps you verify your camera, audio, lighting, scenes, internet connection, moderation tools, and backup plan before every broadcast. Use it as a repeatable OBS streaming checklist, then adjust platform-specific settings whenever your streaming service or software changes.
Overview
A professional-looking stream depends less on expensive equipment than on a reliable content creation workflow. A modest camera with good framing, a clear microphone, stable lighting, and a tested scene layout will usually serve viewers better than a complicated setup that has not been rehearsed.
Run this checklist in order: prepare the room, connect and test equipment, configure scenes, check the stream settings, review moderation, and complete a short private or unlisted test if your platform supports one. Keep a written record of settings that work well for your computer, connection, and usual stream format. That record makes recurring problems easier to diagnose.
Platform dashboards and encoder software can use different labels, so treat the following as workflow guidance rather than permanent specifications. Confirm the current ingest server, supported resolution, frame rate, encoder options, bitrate guidance, and account requirements in the documentation for the platform you are using.
Quick pre-stream checklist
- Camera is connected, selected in the encoder, and framed correctly.
- Microphone is selected, positioned close enough, and free from clipping or unwanted noise.
- Face and background are visible without harsh glare or distracting shadows.
- Scenes, sources, alerts, overlays, and transitions have been tested.
- Streaming and recording settings match the computer, connection, and platform.
- Upload capacity has been checked at the time of day you normally stream.
- Chat moderation, blocked words, moderators, and slow-mode options are ready.
- Media, music, images, and clips are cleared for use in a live broadcast.
- Recording storage is available if you plan to save a local copy.
- A backup connection, backup recording, or alternate communication plan is available.
Checklist by scenario
1. Camera, framing, and lighting
- Clean the lens and confirm the correct camera is selected.
- Place the camera at approximately eye level. Leave enough headroom without making the frame feel empty.
- Check the full frame for private information, mirrors, bright windows, clutter, and notifications on secondary displays.
- Use a consistent background. If you use a virtual background, test its edges while moving naturally.
- Position the main light in front of you or slightly to one side. Avoid placing a strong light directly behind you unless the camera exposure has been tested.
- Confirm that the image is neither too dark nor washed out. Lock exposure or white balance when automatic changes are distracting.
For a gameplay, interview, or presentation stream, decide in advance whether the camera should be full-screen, part of a layout, or hidden in selected scenes. Consistency makes scene switching less error-prone.
2. Microphone and streaming audio settings
- Select the intended microphone rather than relying on a default device that may change when headphones or a webcam are connected.
- Speak at your normal volume and watch the meter. Leave headroom so an excited reaction does not distort the recording.
- Listen through headphones for hum, keyboard noise, fan noise, echo, and audio delay.
- Place the microphone close to your mouth, but outside the direct path of strong breaths and plosive sounds.
- Set the balance between microphone, game, browser, guest, and alert audio before going live. Your voice should remain intelligible when several sources play together.
- Mute unused sources and check that notification sounds do not expose private messages.
A short test recording is more useful than watching the meters alone. Speak, play the loudest expected content, and review the result with headphones.
3. Scenes, overlays, and sources
Open every scene you expect to use and verify that its sources appear in the correct order. Check the starting scene, live scene, break scene, ending scene, gameplay or screen-share scene, and any layout used for guests.
- Confirm that screen capture shows only the intended window or display.
- Hide sensitive browser tabs, desktop files, email previews, and account information.
- Test alerts, chat boxes, timers, donation or membership elements, and animated overlays.
- Make sure browser-based sources have loaded and that fonts, images, and local files are still available.
- Check transitions and hotkeys. Do not assign critical shortcuts that conflict with the game or application you are demonstrating.
- Keep a clean fallback scene with camera and microphone only.
If you need to create clips or short-form edits from the broadcast later, leave important action inside a safe central area and avoid placing essential text at the extreme edges. The repurposing workflow for turning long videos into Shorts offers a useful way to plan for that next step.
4. Encoder, resolution, and connection
- Choose the platform’s current ingest server or recommended automatic option.
- Select a resolution and frame rate your computer can encode consistently. Higher settings are not automatically better if they cause dropped frames or overheating.
- Use a hardware encoder when it is stable and compatible with your system; otherwise test the available software encoder at a conservative quality setting.
- Set the video bitrate within the platform’s current guidance and leave practical upload headroom rather than using all available capacity.
- Confirm keyframe, audio, and encoder options against the platform’s current requirements.
- Run a connection test at the same location and, when possible, near the time of the broadcast. Pause cloud backups, large downloads, and other uploads.
Upload speed is only one part of reliability. Wireless interference, network congestion, encoder overload, and an unstable route to the ingest server can also interrupt a stream. A wired connection is worth testing when it is available, but verify the complete path rather than assuming any single change will solve the problem.
5. Chat, copyright-safe media, and backup plans
- Turn on the moderation controls appropriate for your audience, such as slow mode, follower or subscriber restrictions, blocked terms, and verification options where available.
- Assign a trusted moderator for streams with active chat or guests.
- Prepare a pinned message with the topic, links, rules, or instructions viewers need.
- Use music, video clips, images, and sound effects that you are permitted to broadcast. Do not assume that media available online is cleared for live use.
- Confirm that local recording is enabled only if you have enough disk space and know where the file will be saved.
- Keep a phone hotspot, second connection, or alternate announcement channel available if the stream is important.
- Know how to switch to a low-bandwidth scene or end the broadcast cleanly if the connection fails.
For broader production continuity, review the video creator file organization and backup workflow. It can help you protect recordings, graphics, project files, and reusable overlays.
What to double-check
Complete these checks immediately before clicking Start Streaming:
- Do a one-minute rehearsal. Say the opening, switch scenes, play the loudest media, and return to the main layout.
- Review the recording. Confirm that speech is clear, sources are visible, and audio levels remain balanced during the rehearsal.
- Check dropped frames and encoder load. If either rises during the test, lower the most demanding setting before going live.
- Confirm storage. Check the recording drive, file path, and available space.
- Check the public view. Use the platform’s preview or a separate device to verify title, category, thumbnail, visibility, and latency choices.
- Open the moderation view. Make sure you can see chat and reach the controls needed to remove messages, pause chat, or communicate with moderators.
| Symptom | Likely area to inspect | First response |
|---|---|---|
| Dropped frames during the stream | Network upload, Wi-Fi, ingest route, or bitrate | Pause other uploads, test a wired or alternate connection, and use the platform’s current recommended settings. |
| Encoder overload or stuttering video | CPU/GPU load, resolution, frame rate, or demanding sources | Close unnecessary applications, simplify browser sources, or reduce output settings. |
| Viewers report an echo | Duplicate microphone or desktop audio sources | Mute duplicate devices and test with headphones. |
| Voice sounds distorted | Microphone gain or clipping | Lower input gain, move the microphone slightly farther away, and repeat the loudest part of the rehearsal. |
| Camera is black or missing | Device access, another application using the camera, or wrong source | Close competing applications, reconnect the camera, and select the device again. |
| Overlay or alert does not appear | Browser source, network loading, file path, or scene visibility | Refresh the source and test the exact scene in which it will be used. |
For captioned replays and clips, plan accessibility during production rather than after publishing. The guides to caption generators and AI caption and subtitle tools can help you evaluate the next stage of the workflow.
Common mistakes
- Changing several settings at once: Make one change, test it, and record the result so you know what improved or caused a new problem.
- Trusting the preview without listening: A picture can look correct while the microphone is muted, delayed, or buried under desktop audio.
- Using maximum quality by default: Choose the most reliable settings your computer and connection can sustain, not the most demanding options available.
- Forgetting the starting scene: Viewers may see an empty layout, private desktop, or unfinished setup while you prepare.
- Leaving automatic updates for the last minute: Software, drivers, plugins, and operating-system updates can change devices or source behavior. Update before the rehearsal, not immediately before broadcast.
- Having no low-bandwidth fallback: A simplified scene and lower tested output can keep a useful broadcast running when conditions deteriorate.
- Ignoring the recording: The live stream may look acceptable from your dashboard while the local file has missing audio, dropped frames, or the wrong save location.
When to revisit
Use this checklist before every broadcast, even if the setup has worked for months. Revisit the full workflow when you change cameras, microphones, lighting, capture cards, monitors, scenes, plugins, encoder software, operating systems, internet providers, or streaming platforms.
Review platform ingest settings, supported resolutions, encoder requirements, moderation features, and hardware compatibility at least every six months, and sooner after a major platform or software update. Recheck before seasonal planning cycles, special events, guest broadcasts, multistreaming, or a change in audience size. The multistreaming platform comparison is a useful companion when your distribution plan expands.
After each stream, write down one successful setting and one issue to investigate. Before the next broadcast, run the one-minute rehearsal, inspect the audio and dropped-frame indicators, confirm the backup plan, and only then go live. This small routine turns troubleshooting into a repeatable production workflow instead of an emergency.