This guide helps you find technical and setup problems in your own stream: audio, picture, connection, encoder load, scenes, privacy and chat. It names no products, and it does not promise views or growth. The microphone, camera, audio interface and capture card guides cover choosing equipment. This one covers checking what you already have, using OBS and platform documentation read in November 2026. For the full gear picture, see our streaming setup guide.

Audio that is too quiet, too loud or uneven

You can hear most audio problems in a short test recording of your own stream. Listen on speakers or headphones other than the ones you monitor with.

OBS’s audio mixer guide describes the meter in three zones. Speech should sit in the upper yellow range and may reach the lower end of the red zone, which OBS describes as close to clipping. Music and alerts belong in the green zone. The top dot shows the loudest level in the last 20 seconds, which OBS calls a good way to see whether you are clipping. OBS also warns that sounds that look equally loud on the meter can sound louder to viewers, so use the meter to find problems and your ears to judge them.

OBS’s gain filter page says gain should generally be applied at the source before the signal reaches OBS. Set the level on the microphone or interface first, then check it in the meter. The microphone guide covers placement for specific microphone types.

Illustration of a generic microphone setup, not a photo of a specific model and not a Gimaxo test.

Lighting and camera position

A picture that is dark or flat shows up in your preview. The usual cause is where the light is. Put the main light in front of you rather than behind, and keep a bright window out of the frame behind you. We found no maker source for exactly how cameras react to a window behind you, so this is our reasoning from general practice. Test it in your own preview at the time of day you stream.

Many cameras let you lock exposure and focus in their own settings. In OBS on Windows, the Video Capture Device source has a Configure Video option that opens the device’s own configuration utility. The camera guide covers the camera side.

Illustration of a streaming desk, not a photo of a specific setup and not a Gimaxo test.

Dropped frames: the connection

OBS’s stream connection guide says dropped frames mean your connection to the remote server is not stable, or you cannot keep up with your set bitrate. It lists first steps: use a wired connection rather than WiFi, restart your modem and router, and try a different ingest server. It gives a starting point for the bitrate: 75% of your total upload speed. Treat that as a place to begin, not a guarantee.

A separate guide posted on the OBS forums by a community member, Videophile, in 2020 also advises keeping the bitrate under 75% of your upload and adds that other people on your network uploading can saturate it. That is that author’s advice, not OBS Project documentation, and it is not a rule for every connection. We use it only for that extra point.

Take bitrate, resolution and frame rate from your platform’s current help page for your type of stream. The figures differ between platforms and change, so we quote none here.

Rendering and encoding load

Not every glitch is a network problem. OBS’s encoding troubleshooting guide covers choppy output when OBS shows “encoding overloaded” messages. Its suggestions include running OBS as administrator on Windows, limiting the game’s frame rate, reducing the game’s graphics settings, reducing OBS output settings and building simpler scenes. Videophile’s 2020 forum guide, which is community advice and not OBS documentation, also describes “frames missed due to rendering lag”. The author says this happens when OBS cannot get frames off the GPU to the encoder fast enough, and names a GPU at 100% usage and too many overlays as causes. These are one author’s observations from 2020. Treat them as leads to check against the current OBS documentation, not as universal rules.

Look at OBS’s status indicators during a test recording. A network problem and a load problem need different fixes, so identify which one you have before you change a setting.

Scenes that confuse or leak

A single scene leaves you with few options when something goes wrong. OBS has a tutorial for building a Be Right Back scene, which is a simple second scene for when you step away. Name your scenes clearly and check what each one shows.

OBS’s overview guide says Studio Mode lets you change scenes in the background without viewers seeing the changes. You see the live scene on one side and the scene you edit on the other, and a Transition swaps them. That is useful for testing a scene before it goes live.

Capturing a whole display shows anything that appears on that display. Capturing a single window or a game limits it. This is our reasoning, not an OBS statement.

Privacy

Twitch’s stream key FAQ says: “Never share your stream key with anyone. Don’t show your stream key on stream!” It adds that sharing it could compromise your channel, and that you can reset it from the Creator Dashboard under Settings and Stream. Twitch also says the key resets when you change your password. Check your platform’s equivalent page if you stream elsewhere.

Think about what else can appear on screen: notifications, browser tabs, a window title, an email, a document. The reliable steps are to choose the capture source carefully, close what you do not need and turn off notifications while you stream. This is our own advice, with the reasoning above.

Chat

A stream is a conversation, and a recording shows how much of it you answered. Acknowledge new arrivals, answer questions and say what you are doing.

Platforms provide moderation tools, so set them up before a problem. Twitch’s help page describes AutoMod, which holds risky messages so a channel moderator can approve or deny them before viewers see them. The streamer chooses one of four strictness levels, and AutoMod does not time out, ban or mute anyone itself. Other platforms have their own tools, which we did not read.

Test and review

Make a test recording, or use your platform’s test mode if it has one, and watch it as a viewer would. Then change one thing at a time. We cannot say how long any fix takes to show a result.

A short checklist before you go live

• Does your voice sound clear on a recording, with the meter used only as a guide?
• Is the main light in front of you, and is the picture steady?
• Is your bitrate at or below about 75% of your measured upload, with the current platform guidance in hand?
• Do the OBS status indicators show a network problem or a load problem, and have you fixed that one?
• Do your scenes make sense, and have you checked what each one shows?
• Are notifications off, and are your stream key and personal information out of view?
• Are the platform’s moderation tools set up?

What we could not verify

We found no official source for the following, so this page does not state them: how much any fix improves viewer numbers or retention, a safe bitrate figure for your platform (the platforms’ own pages hold the current ones), how OBS’s stats panel counts skipped frames (the OBS guide we read does not describe it), and the moderation tools of platforms other than Twitch. We did not test any of the settings described here.

Sources

Named here as plain text. Pages read in November 2026.

• OBS Project, Knowledge Base: Audio Mixer Guide, Gain Filter, Stream Connection Troubleshooting, Encoding Performance Troubleshooting, OBS Studio Overview Guide, Video Capture Sources, Stream Layout Tutorial 3: Be Right Back screen
• OBS Forums, “Status indicators and what they mean”, by the community member Videophile, 8 May 2020. Hosted on the OBS site but a user-contributed resource, not OBS Project documentation
• Twitch Help, “Twitch Stream Key FAQ” and “How to Use AutoMod”
• Twitch and YouTube help pages on encoder settings are named as places to look, and no figure from them is used