Live Streaming Setup Checklist: Camera, Microphone, Lighting, Internet, and OBS Settings

Overview

A good streaming checklist follows the signal from your room to the audience: capture, audio, lighting, computer, internet, streaming software, platform settings, and recording. Checking each layer in that order makes troubleshooting faster because you can identify where a problem begins instead of changing several settings at once.

Your ideal setup depends on the type of show you produce. A talking-head broadcast may need one camera, a microphone, and a simple scene. A gaming stream may require game capture, alerts, chat display, and separate audio sources. A music performance, podcast, class, or shopping stream may need multiple cameras, a mixer, guests, or additional monitoring. Start with the minimum equipment needed for a clear, stable broadcast, then add complexity only when it improves the viewer experience.

Before buying anything, define your primary format, target resolution, platform, and room. This prevents mismatched purchases. For example, a camera upgrade will not solve an echo problem, and a higher video resolution will not help if your upload connection cannot sustain the required bitrate.

Checklist by scenario

For a basic talking-head stream

• Place the camera at or slightly above eye level and frame your head and shoulders with enough space for natural movement.
• Use a microphone positioned close to your mouth, but outside the camera frame if possible. A modest microphone placed well often sounds better than an expensive microphone placed across the room.
• Position a soft light in front of you and slightly to one side. Keep bright windows or lamps from appearing directly behind you unless you intentionally want a backlit look.
• Remove distracting background noise, including fans, notifications, appliances, and loose cables that may be touched during the show.
• Create at least three OBS scenes: starting soon, live, and ending. Include a camera source, microphone source, and a simple transition between scenes.
• Run a short private or unlisted test to check framing, exposure, focus, audio level, and sync.

For gaming or screen-sharing streams

• Open the game or application before launching the final test, then confirm that OBS captures the correct window or display.
• Separate desktop, game, microphone, and guest audio in the mixer when possible. This gives you more control during editing and makes it easier to mute a single source.
• Check that alerts, chat, overlays, and browser sources load correctly. Test them without relying on a live audience.
• Use a scene that shows your camera and another that prioritizes the screen. Keep overlays away from important interface elements or subtitles.
• Monitor system performance while the game or application is running. If frames are dropped or the preview stutters, reduce output complexity before increasing bitrate.

For podcasts, interviews, and guest streams

• Confirm how each guest joins and whether the call platform sends separate audio or video feeds to your streaming software.
• Ask every guest to use headphones, a quiet room, and a microphone placed close to them. Echo is difficult to repair after the broadcast.
• Prepare a backup contact method in case a guest drops from the call.
• Keep a host-only scene ready so private setup conversations do not reach the audience.
• Record a local copy when your workflow and storage allow it. A local recording can be useful if the platform replay has a connection problem.
• For more workflow ideas, see this guide to repurposing a live stream into clips, Shorts, Reels, and podcasts.

For music and performance streams

• Test the complete audio chain, including instruments, microphones, mixer, interface, monitoring, and OBS input.
• Keep monitoring volume low enough to avoid feedback, and verify that the audience receives the performance rather than only your room microphone.
• Use a camera angle that shows the performer and the important instruments or equipment without blocking the hands or stage area.
• Prepare a silent holding scene for tuning, breaks, or technical interruptions.
• Make a short test recording and listen on headphones before going live. Room sound can appear acceptable through speakers but become harsh or muddy on headphones.

What to double-check before going live

Camera and lighting

Clean the lens, disable unwanted autofocus behavior, and check that your face is not overexposed. Lock exposure or focus when movement causes the image to brighten, darken, or hunt for focus. Make sure the camera is securely mounted and that its cable cannot be pulled during the show. If you use a mirrorless or DSLR camera, check its power source and any automatic sleep settings.

Lighting should separate you from the background without making the scene uncomfortable to watch. A large, diffused light source is usually easier to manage than a small, harsh light. Look at the preview with your intended background, clothing, and overlays active; colors can change when the complete scene is visible.

Microphone and audio

Speak at your normal broadcast volume and watch the OBS audio meter. Leave enough headroom so enthusiastic speech, laughter, or music does not clip. Listen for hum, hiss, keyboard noise, room echo, and delayed monitoring. Do not rely only on the meter: record a sample and listen to it.

Use filters carefully. Noise suppression can reduce a constant fan, while a compressor can make speech more even. Excessive processing can make a voice sound thin, metallic, or unnaturally loud. If you are choosing the best microphone for streaming, prioritize placement, room conditions, and reliable connectivity over specifications alone.

Internet and bitrate

Test upload performance in the same location and on the same connection you will use for the broadcast. A wired connection is often preferable for a stationary setup because it reduces variables. Leave practical headroom between your measured upload capacity and your chosen stream bitrate; a connection that barely meets the target may become unstable when other devices use the network.

Choose bitrate settings for streaming based on your platform, resolution, frame rate, content movement, and available upload capacity. Fast-moving gameplay and detailed scenes generally require more data than a static talking-head shot. If you see dropped frames caused by the network, lower the bitrate or output resolution before repeatedly restarting the stream.

OBS and recording

• Confirm the correct stream account, destination, title, category, privacy setting, and thumbnail.
• Check every scene source, especially browser overlays, media files, capture cards, and guest windows.
• Verify the canvas and output resolutions, frame rate, encoder, and recording location.
• Make sure the recording drive has sufficient free space and that the selected format suits your editing workflow.
• Start a short local recording, then review the first minute for audio sync, black screens, missing sources, and unexpected notifications.
• Save or export your scene collection and note any settings that are specific to the computer or platform.

For a deeper production workflow, use an overlay, alert, and on-screen branding tool only after the core video and audio path is stable. Visual polish cannot compensate for unclear speech or an unreliable broadcast.

Common mistakes

1. Changing several settings at once. Change one variable, test, and record the result. This creates a useful troubleshooting history.
2. Prioritizing video over audio. Viewers will often tolerate a simple camera image, but inconsistent volume, echo, and clipping make a stream difficult to follow.
3. Testing only the OBS preview. The preview may not reveal platform-side processing, viewer playback behavior, or audio balance. Use a private test and monitor the actual output when possible.
4. Using too many browser sources. Animated overlays and alerts consume resources and can fail when a service, browser session, or network request changes. Keep a clean fallback scene.
5. Ignoring room acoustics. A microphone cannot fully correct a reflective, echo-heavy room. Soft furnishings, closer microphone placement, and lower room noise are often more effective.
6. Having no interruption plan. Keep a holding scene, a short explanation ready for viewers, and a way to contact collaborators if a device or connection fails.
7. Skipping the post-stream check. Review the replay for audio problems, unintended private information, missing segments, and moments worth clipping. Guides to using AI for faster stream clips can help once the recording itself is usable.

When to revisit this checklist

Use the full checklist before a new show format, a new platform, a major gear change, or a move to another room. Revisit it before seasonal planning cycles when your schedule, set design, guests, or network usage may change. It is also worth checking after an operating system update, OBS update, capture-card change, camera firmware update, or router replacement.

For routine broadcasts, create a shorter version that takes five minutes: confirm the destination, camera, microphone, lighting, internet, scenes, recording, and backup plan. Keep the full checklist available for monthly reviews or whenever a broadcast produces dropped frames, desynced audio, black sources, or unexplained interruptions.

After each stream, write down one technical observation and one improvement. Over time, these notes become a setup log: the bitrate that remained stable, the scene that failed, the microphone position that worked, and the backup procedure that saved the show. If your platform workflow changes, compare the log against the platform-specific guidance for YouTube Live, Twitch, or TikTok Live. Then run a short test before the next public broadcast rather than discovering the change in front of your audience.