12 Issues Covered — Jump to Yours
00 Diagnose First
01 Dropped Frames
02 Encoding Overload
03 Stream Disconnections
04 Silent / Dead Audio
05 Distorted / Bad Audio
06 Audio / Video Desync
07 Black Screen / No Video
08 Pixelated / Blurry Stream
09 High Latency / Lag
10 Viewer-Side Buffering
11 Stream Won't Start
12 Platform-Specific Issues
Live streaming problems fall into a finite set of categories. Every frame drop you've ever experienced, every audio cutout mid-stream, every viewer complaint about buffering — they all trace back to one of about a dozen root causes, each of which has a systematic fix. The panic that accompanies mid-stream problems makes them feel unique and impossible to solve; the reality is that 95% of streaming problems are caused by the same underlying issues and fixed by the same steps, once you know what to look for.
This guide covers every common streaming issue in the same structure: the symptoms you observe, the likely root causes, and the step-by-step fix in priority order — from the fastest free solution to the more involved fixes needed when the fast solutions don't work. Where specific OBS settings values are involved, they're provided as copy-ready configurations, not vague recommendations. Read through the diagnostic section first, then jump to the specific issue you're experiencing.
73%
Of mid-stream issues are caused by only 3 problems: dropped frames, encoding overload, or audio failure
5 min
Most streaming problems are diagnosable and fixable in under 5 minutes with the right checklist
68%
Of "connection problems" are actually resolved by switching from WiFi to Ethernet — before any other fix
CBR
The single most impactful encoder setting change for connection stability — Constant Bit Rate vs VBR
Before Anything Else — The Diagnostic Workflow
The most common troubleshooting mistake is applying fixes without identifying the problem first. This diagnostic flow takes 2 minutes and identifies which issue category you're dealing with before you change any settings.
🔍 Streaming Problem First-Response Diagnostic
1
Check OBS status bar (bottom of window) — what does it show?
Look at: CPU %, Dropped Frames %, KB/s bitrate, and the colored status indicator circle.
CPU above 80% → Encoding Overload (Issue 02). Dropped Frames above 0% → Issue 01. KB/s fluctuating wildly → Connection (Issue 03).
2
Is the problem audio or video? Check each independently.
In OBS: mute your mic, play a test tone through desktop audio. If desktop audio appears in the Audio Mixer but the stream is silent → audio routing issue. If the video is black but audio works → capture issue. If both are bad → usually connection or encoding.
Silent stream → Issue 04. Black screen → Issue 07. Audio/video out of sync → Issue 06.
3
Run a 5-minute sustained upload test at fast.com. What do you see?
Note the minimum speed — not the peak. If minimum upload is below 2× your stream bitrate, your connection is the bottleneck. If upload is consistent but stream is still dropping, the problem is encoder-side.
Low upload → Issue 01 and 03. Fine upload but drops → Issue 02 (encoding). Pixelated viewers → Issue 08.
4
Check OBS logs: Help → Log Files → Current Log. Scroll to the bottom.
OBS logs contain specific error messages that precisely identify most problems. Look for lines starting with [WARNING], [ERROR], or containing "encoding lag," "high load," "connect failed," or audio device names.
The log message almost always identifies the exact fix needed. Search this guide for the error text you see.
Quick Reference — All Issues at a Glance
| Issue | Severity | Primary Symptom | Fastest Fix |
|---|---|---|---|
| Dropped frames | Critical | OBS shows dropped % rising, viewers see freezing | Switch to Ethernet → lower bitrate |
| Encoding overload | Critical | OBS CPU % above 80%, "encoding lag" in log | Switch to NVENC/AMF hardware encoding |
| Stream disconnecting | Critical | Stream goes offline, OBS shows reconnecting | Enable auto-reconnect, lower bitrate |
| Silent audio | Critical | Viewers hear nothing, OBS audio mixer flat | Check OBS audio device, unplug/replug mic |
| Distorted audio | High | Crackling, clipping, echo, background noise | Lower mic gain, add noise suppression |
| Audio/video desync | High | Lip flap, voice behind or ahead of video | Set audio sync offset, match sample rates |
| Black screen | High | Video source shows black, no image | Right-click source → transform → fit, check GPU |
| Pixelated/blurry | High | Viewers see blocky, low-quality image | Increase bitrate or lower resolution |
| High latency/lag | Medium | Stream is 30+ seconds behind real time | Switch to "Low Latency" mode in OBS |
| Viewer buffering | Medium | Viewers report freezing, you see no issues | Reduce bitrate, check ingest server selection |
| Stream won't start | Critical | OBS shows error when clicking "Start Streaming" | Verify stream key, check platform status |
| Platform-specific | Varies | Works on one platform, fails on another | Match platform's required encoder settings |
Issue 01 — Dropped Frames
CRITICAL
ISSUE 01 · Dropped Frames
DROPPED / SKIPPED FRAMES
OBS reports dropped % rising — viewers see freeze-frames, stuttering, and degraded quality
Symptoms
- OBS status bar shows "Dropped Frames: X%"
- Viewers report video freezing then jumping
- Bitrate graph in OBS spikes and dips
- OBS log shows "insufficient bandwidth"
- Stream looks fine locally but broken for viewers
Root Causes
- Upload bandwidth insufficient for bitrate
- WiFi interference or packet loss
- ISP congestion or routing issues
- Wrong ingest server selected (too distant)
- Other devices consuming upload bandwidth
Fix Priority
- First: Switch to Ethernet cable
- Second: Lower stream bitrate 20%
- Third: Select nearest ingest server
- Fourth: Enable router QoS
- Fifth: Contact ISP about packet loss
🔧 Step-by-Step Fix
1
Identify whether drops are Network or Rendering. In OBS, click Settings → Output and note whether OBS shows "Dropped frames due to Network" or "Dropped frames due to rendering lag." Network drops = connection problem. Rendering drops = encoder problem (see Issue 02).
2
Switch to Ethernet immediately. Unplug your WiFi and run a physical Cat6 cable from your router to your streaming PC. Then disable WiFi in Windows network settings so only the wired connection is active. This single step resolves dropped frames for 68% of affected streamers.
3
Lower your stream bitrate by 20–30%. Go to OBS Settings → Output → Bitrate and reduce it. For a 6,000 kbps stream, try 4,500. Your stream bitrate should never exceed 75% of your sustained upload speed (not peak speed — run a 5-minute test at fast.com).
4
Select the nearest ingest server. In OBS Settings → Stream, click "Connect to Twitch to get stream key" which runs a bandwidth test, or manually select your closest geographic server from the server dropdown. Streaming to a distant server increases packet loss probability significantly.
5
Run continuous ping to identify packet loss. Open Command Prompt and run:
ping -t live.twitch.tv (Windows) | ping -c 100 live.twitch.tv (Mac/Linux)
Any packet loss above 0.1% contributes to dropped frames. Contact your ISP with the ping results as evidence of the problem.
If dropped frames persist after Ethernet + bitrate reduction: run the Twitch bandwidth test tool, test at different times of day (ISP peak congestion is time-dependent), and consider connection bonding software (Speedify) to combine your broadband with a 4G hotspot backup.
Issue 02 — Encoding Overload
CRITICAL
ISSUE 02 · Encoding Overload
ENCODING OVERLOAD / HIGH CPU
CPU cannot process frames fast enough — OBS shows "encoding overloaded!" warning
Symptoms
- OBS shows "Encoding overloaded!" in red at bottom
- OBS log contains "encoder is overloaded"
- CPU usage 85–100% in Task Manager during stream
- Stream is choppy but OBS shows 0% dropped frames
- FPS in OBS drops below your set target FPS
Root Causes
- Using software (x264) encoding on a weak CPU
- Encoder preset too slow (medium, slow, veryslow)
- Resolution too high for CPU to encode in real time
- Running too many apps simultaneously
- CPU thermal throttling due to heat
Fix Priority
- First: Switch to hardware encoding (NVENC/AMF)
- Second: Change preset to "faster" or "veryfast"
- Third: Reduce output resolution to 720p
- Fourth: Close all non-essential apps
- Fifth: Check CPU temperatures
🔧 Step-by-Step Fix
1
Switch to GPU hardware encoding immediately. Go to OBS Settings → Output → Encoder and change from "x264" to "NVENC H.264 (new)" if you have an NVIDIA GPU, or "AMD HW H.264 (AVC)" if you have an AMD GPU. Hardware encoding uses your GPU's dedicated encoder chip, freeing the CPU completely. This single change resolves encoding overload for 80% of affected streamers.
2
If you must use x264, change the preset to "veryfast" or "ultrafast". In OBS Settings → Output → Preset. The preset controls CPU usage vs quality — "slow" produces better quality but uses 3-4× more CPU than "veryfast." For most viewers, the quality difference is imperceptible; the stability difference is enormous.
3
Reduce output resolution to 1280×720. OBS Settings → Video → Output (Scaled) Resolution. Scaling from 1920×1080 to 1280×720 reduces encoding workload by approximately 50%. Most streaming platforms downscale 1080p streams for lower-bandwidth viewers anyway — viewers on your stream often see 720p regardless of what you broadcast.
4
Check CPU temperature with HWMonitor or HWiNFO. If CPU temperature exceeds 90°C during streaming, thermal throttling is reducing your effective CPU speed. Clean your CPU cooler of dust, reapply thermal paste (if the cooler is 2+ years old), or improve case airflow. Thermal throttling commonly causes encoding overload on otherwise capable systems.
5
Close all non-OBS applications before streaming. Web browsers, Discord video calls, cloud sync services, antivirus scans, and game launchers all consume CPU. Especially close any application that produces video — video calls are particularly CPU-intensive when running alongside OBS.
⚙️ Optimal OBS Settings for Low-End CPU Settings → Output → Streaming
Encoder
NVENC H.264 (new) / x264 if no GPU
GPU encoding always preferred
Rate Control
CBR
Never VBR — CBR is more stable
Bitrate
4500 kbps (720p) / 6000 kbps (1080p)
Keyframe Interval
2
Required by all major platforms
Preset (x264 only)
veryfast or faster
Reduces CPU usage 60%
Profile
main
Not "high" — too demanding
Tune (x264 only)
zerolatency
If NVENC is unavailable (no NVIDIA GPU) and x264 at "ultrafast" still causes overload: your CPU is genuinely insufficient for 1080p encoding. Consider streaming at 720p/30fps, using a cloud streaming service that handles encoding server-side, or upgrading to a PC with a dedicated GPU.
Issue 03 — Stream Disconnections
CRITICAL
ISSUE 03 · Disconnections
STREAM KEEPS DISCONNECTING
Stream goes offline unexpectedly — OBS shows "Reconnecting" or stops entirely
Symptoms
- Stream goes offline every 15–60 minutes
- OBS shows "Disconnected from server" message
- Reconnects successfully then drops again
- Only fails when other devices are active on network
- Pattern disconnections at specific times of day
Root Causes
- Router DHCP renewal dropping connection
- ISP line fault or modem instability
- Network bandwidth contention
- Ingest server instability
- Stream key invalidated mid-session
Fix Priority
- First: Enable OBS auto-reconnect
- Second: Lower bitrate to reduce bandwidth strain
- Third: Change to a different ingest server
- Fourth: Enable router QoS
- Fifth: Contact ISP with ping loss evidence
🔧 Step-by-Step Fix
1
Enable OBS auto-reconnect with aggressive settings. OBS Settings → Stream → Enable auto-reconnect ON. Set retry delay to 2 seconds, max retries to 20. This ensures brief ISP hiccups are recovered automatically without the stream going permanently offline.
2
Check router logs for DHCP renewals. Log into your router admin panel (192.168.1.1) and check the DHCP lease log. If your streaming PC's IP is renewing every 15–30 minutes, that renewal can briefly drop the network connection. Set a static IP for your streaming PC in the router DHCP settings to prevent this.
3
Try a different ingest server region. If disconnections follow a pattern (every X minutes), the ingest server you're connecting to may have an instability issue. In OBS Settings → Stream, switch to a different server in the same region and test for 30 minutes. Platform status pages (status.twitch.tv, status.youtube.com) show if there's a known ingest issue.
4
Run a continuous connection quality test.
pathping live.twitch.tv (Windows — more detailed than ping)
PathPing shows packet loss at every hop between you and the ingest server. If you see consistent packet loss at a specific hop, that's the location of the network problem — report it to your ISP with a screenshot.
Recurring disconnections that persist after all fixes indicate a physical line problem between your home and the ISP's exchange. Request a physical line quality check (not just a speed test) from your ISP. If the line is deteriorated, replacement resolves it. Consider a 4G backup connection for the interim.
Issue 04 — Silent / Dead Audio
CRITICAL
ISSUE 04 · Silent Audio
STREAM IS COMPLETELY SILENT
Viewers hear nothing — mic or game audio not reaching the stream output
Symptoms
- Audio mixer in OBS shows flat/no movement
- Stream VOD has no sound
- Viewers report silence
- Mic works in other apps but not OBS
- Audio track appears in OBS but viewers can't hear
Root Causes
- Wrong audio device selected in OBS
- Audio source muted in OBS mixer
- Output audio track not assigned to stream
- USB mic lost connection during session
- Windows exclusive mode blocking OBS access
Fix Priority
- First: Check OBS mixer for muted sources
- Second: Verify correct audio device in settings
- Third: Unplug/replug USB mic
- Fourth: Check audio track assignments
- Fifth: Disable Windows exclusive mode
🔧 Step-by-Step Fix
1
Check the OBS Audio Mixer for muted sources. Look at the mixer at the bottom of the main OBS window. A speaker icon with an X means that source is muted. A volume fader all the way to the left means the volume is at zero. Un-mute and raise the fader if needed.
2
Verify the correct audio device is selected. OBS Settings → Audio. Check "Mic/Auxiliary Audio Device" — if it shows a device that doesn't match your actual microphone (e.g., shows a headset when you're using a USB mic), change it to the correct device. Also confirm "Desktop Audio Device" matches your default playback device.
3
Check audio track assignments. OBS Settings → Output → Audio Tab. Confirm Track 1 is enabled. Then in Settings → Output → Recording (or Streaming), ensure "Audio Track" is set to 1. A common misconfiguration has audio going to Track 2 while the stream outputs Track 1 only.
4
Disable Windows exclusive audio mode for your mic. Windows Control Panel → Sound → Recording tab → right-click your microphone → Properties → Advanced tab → uncheck "Allow applications to take exclusive control of this device." Exclusive mode lets other apps block OBS from accessing the microphone.
5
For USB microphones: unplug and replug. USB audio devices can lose their driver connection without showing any visible error. Unplugging and replugging the USB cable while OBS is open forces a driver reconnect. You may need to re-select the device in OBS Audio Settings afterward.
If audio appears in OBS mixer (levels are moving) but viewers can't hear it: the problem is in the stream output configuration, not the audio capture. Check OBS Settings → Output → Audio Track assigned to the stream, and ensure you're not using a multi-track recording config that routes audio differently for stream vs recording.
Issue 05 — Distorted / Bad Audio Quality
HIGH
ISSUE 05 · Audio Quality
DISTORTED / CRACKLING / NOISY AUDIO
Audio reaches viewers but sounds bad — crackling, clipping, echo, reverb, or background noise
Symptoms
- Crackling or popping sounds in audio
- Microphone sounds "clipped" or distorted at loud moments
- Echo: viewers hear themselves through your speakers
- Constant background hiss, hum, or fan noise
- Audio sounds like it's underwater or reverberant
Root Causes
- Microphone gain too high — clipping the signal
- Sample rate mismatch (44100 vs 48000 Hz)
- Desktop audio routing through speakers + mic
- Poor room acoustics — excessive reflections
- Electrical interference or USB power issue
Fix Priority
- First: Reduce mic gain until peaks stay green
- Second: Match sample rates to 48000 Hz
- Third: Switch to headphones (stop echo)
- Fourth: Add OBS noise suppression filter
- Fifth: Add acoustic treatment to room
🔧 Step-by-Step Fix
1
Check your audio meter during a test — peaks must stay in the green/yellow range. In OBS's audio mixer, speak at your loudest streaming volume. The volume meter should peak around -6 to -12 dB, never reaching the red zone at the right. If it hits red, reduce the mic gain using the fader in OBS's mixer or in Windows Sound settings → Recording → microphone Properties → Levels.
2
Match sample rates across all audio devices. OBS Settings → Audio → Sample Rate: set to 48000 Hz. Then: Windows Control Panel → Sound → Recording tab → Properties → Advanced: set to 48000 Hz for every audio device. Then: Sound → Playback → Properties → Advanced: set to 48000 Hz. Mismatched sample rates cause crackling and audio artifacts.
3
Add OBS audio filters for noise and clipping. In OBS's Audio Mixer, click the gear icon on your microphone → Filters → click + to add filters in this order:
1. Noise Suppression (RNNoise method) — removes background hiss
2. Noise Gate (Close Threshold: -40 dB, Open: -36 dB) — cuts mic when not speaking
3. Compressor (Ratio 4:1, Threshold -18 dB) — prevents clipping
4. Limiter (Threshold: -1 dB) — hard ceiling to prevent any clipping
4
For echo: switch from speakers to headphones. Echo occurs when your microphone picks up the game/stream audio playing through your speakers. Use headphones during any stream where your mic is active. If you cannot use headphones, enable OBS's "Desktop Audio" monitoring → set to "Monitor Off" for desktop sources so OBS doesn't loop the audio.
Issue 06 — Audio / Video Desync
HIGH
ISSUE 06 · Audio Desync
AUDIO / VIDEO OUT OF SYNC
Voice doesn't match lip movement — audio arrives ahead of or behind the video
Symptoms
- Viewers see lips moving but hear sound later
- Game audio is ahead of the gameplay video
- Desync worsens the longer the stream runs
- VOD replay has visible desync even if stream seemed fine
- Specifically with capture cards or HDMI sources
Root Causes
- Capture card introducing video processing delay
- Browser source audio not synchronized with video
- Mixed audio sources with different buffer sizes
- -use_wallclock_as_timestamps not set (reconnect desync)
- Growing desync = clock drift between audio/video
Fix Priority
- First: Set audio sync offset on delayed source
- Second: Match all audio sources to 48000 Hz
- Third: Enable "Use device timestamps" in audio
- Fourth: Add video delay to match audio latency
- Fifth: Update capture card drivers
🔧 Step-by-Step Fix
1
Measure the desync in milliseconds. Record a 30-second clip of yourself clapping near the mic while visible on camera. Play back the recording in VLC and use it to measure exactly how many milliseconds the audio lags or leads the video. This number is your required sync offset.
2
Set the Audio Sync Offset in OBS. In the OBS Audio Mixer, click the gear icon on the audio source that's out of sync → Advanced Audio Settings → set "Sync Offset" to your measured millisecond delay. Positive values delay the audio; negative values advance it. If video is behind audio: add sync offset to the video source instead using Video Capture Device → Sync Offset.
3
For capture card sources, enable low-latency mode. In OBS, right-click your Video Capture Device → Properties → Buffering: set to "None" (Disable) or "Low Latency." Capture cards buffer video by default; disabling this reduces the processing delay that causes desync with the direct audio signal.
4
For growing desync (worsens over time): fix the clock drift. Go to OBS Settings → Audio → "Force Mono" OFF → ensure all sources are the same sample rate. Then right-click each audio source → Properties → enable "Use Device Timestamps." This anchors audio timing to the hardware clock rather than OBS's internal clock, preventing clock drift over long sessions.
Issue 07 — Black Screen / No Video
HIGH
ISSUE 07 · Black Screen
BLACK SCREEN / NO VIDEO SOURCE
Stream output shows a black rectangle where the game, webcam, or window capture should be
Symptoms
- Black rectangle in OBS preview where game/window should be
- Webcam source shows black (no image)
- Stream goes live but viewers see a black screen
- Works for one application, black on another
- Worked previously, stopped after Windows/driver update
Root Causes
- Game/app running on different GPU than OBS
- Hardware acceleration blocking screen capture
- OBS and game running with mismatched privileges
- Wrong capture method selected
- Window minimized or off-screen on capture
Fix Priority
- First: Switch capture method to Game Capture
- Second: Run OBS as Administrator
- Third: Disable hardware acceleration in app
- Fourth: Force OBS to use the correct GPU
- Fifth: Update GPU drivers
🔧 Step-by-Step Fix
1
Try "Game Capture" instead of "Window Capture" or "Display Capture". Right-click your existing source → Remove. Add a new source → Game Capture → "Capture specific window" → select your game. Game Capture uses a different API that works with most full-screen applications and avoids the hardware acceleration conflicts that cause Window Capture black screens.
2
Run OBS as Administrator. Close OBS, right-click the OBS icon → "Run as administrator." Games with anti-cheat or elevated permissions can block screen capture from non-elevated processes. Running OBS as admin matches the permission level and resolves the majority of "works in other apps but not this game" black screen cases.
3
Disable hardware acceleration in the application you're capturing. For browser-based content: Chrome Settings → System → "Use hardware acceleration when available" OFF, then relaunch. For Discord: Settings → Advanced → Hardware Acceleration OFF. Hardware acceleration moves rendering to the GPU in a way that bypasses screen capture APIs.
4
Force OBS to use the same GPU as the game (NVIDIA multi-GPU systems). Windows Settings → Display → Graphics Settings → find OBS → set to "High performance." Laptops with both integrated Intel graphics and discrete NVIDIA GPU often have OBS running on Intel while the game runs on NVIDIA, preventing capture.
Also: NVIDIA Control Panel → Manage 3D Settings → Program Settings → OBS → preferred GPU → High-performance NVIDIA processor
For "Display Capture" specifically: try adding a new Display Capture source and select a different display from the dropdown — even if you only have one monitor. Sometimes the display index shifts after Windows updates and OBS is capturing the "wrong" display index (now invalid). Updating GPU drivers often resolves this permanently.
Issue 08 — Pixelated / Blurry Stream Quality
HIGH
ISSUE 08 · Video Quality
PIXELATED / BLURRY / BLOCKY STREAM
Stream is visible but looks low quality — blocky artifacts, blurry motion, or muddy details
Symptoms
- Viewer screenshots show blocky compression artifacts
- Fast-motion content looks especially bad
- Viewers complain about quality despite stream being up
- Text and fine details are unreadable
- Stream looks fine in OBS preview but bad for viewers
Root Causes
- Bitrate too low for the resolution and content type
- Keyframe interval too long (above 2 seconds)
- Platform downscaling your stream
- x264 preset too fast reducing quality
- VBR encoding causing quality variance
Fix Priority
- First: Increase bitrate (if upload allows)
- Second: Set keyframe interval to exactly 2
- Third: Switch to CBR rate control
- Fourth: Reduce FPS from 60 to 30
- Fifth: Slow down x264 preset for quality
🔧 Step-by-Step Fix
1
Calculate the correct bitrate for your resolution and FPS. Minimum bitrate requirements: 720p/30fps = 2,500–4,000 kbps. 720p/60fps = 4,500–6,000 kbps. 1080p/30fps = 4,500–6,000 kbps. 1080p/60fps = 6,000–8,000 kbps. If your current bitrate is below these minimums, increase it — but only to 75% of your sustained upload speed.
2
Set keyframe interval to exactly 2 seconds. OBS Settings → Output → Keyframe Interval: 2. A keyframe interval above 2 seconds causes platforms to produce larger visual artifacts between keyframes. The platforms' default viewer experience is calibrated around 2-second keyframes — any higher produces noticeable quality degradation.
3
Switch from 1080p/60fps to 1080p/30fps if upload is marginal. 60fps requires significantly more bitrate than 30fps for equivalent quality. For most content types (educational, music, ambient, non-gaming), 30fps is visually indistinguishable from 60fps. Halving the FPS allows the same bitrate to produce twice the quality per frame.
4
Ensure you're using CBR, not VBR. OBS Settings → Output → Rate Control: CBR. VBR (Variable Bit Rate) adjusts quality dynamically, which means complex scenes get compressed heavily. CBR maintains consistent bitrate and produces more consistent quality across the stream — especially important for fast-moving content like gameplay.
Issue 09 — High Latency / Viewer Lag
MEDIUM
ISSUE 09 · High Latency
HIGH LATENCY — STREAM IS BEHIND REAL TIME
Viewers are watching events 30–60+ seconds after they happen — chat interaction feels broken
Symptoms
- Chat messages lag 30–90 seconds behind action
- Viewers reference things that happened "earlier"
- Stream timestamp in platform dashboard shows large delay
- Reacting to chat is awkward and disjointed
Root Causes
- OBS network buffer too large
- Platform latency mode set to "Normal" instead of "Low"
- B-frames enabled in encoder (adds latency)
- Platform edge CDN buffering for quality
Fix Priority
- First: Enable "Low Latency" in platform dashboard
- Second: Set OBS network buffer to 0
- Third: Disable B-frames in NVENC settings
- Fourth: Switch to "Ultra Low Latency" (Twitch)
🔧 Step-by-Step Fix
1
Enable Low Latency mode on YouTube. In YouTube Studio → Live Dashboard → Stream Settings → Latency: change from "Normal" to "Low Latency" or "Ultra Low Latency." Normal latency on YouTube is 20–30 seconds. Low latency is 5–10 seconds. Ultra-low is 2–5 seconds but requires a more stable connection to maintain without buffering.
2
Enable Low Latency mode on Twitch. Creator Dashboard → Stream Manager → Preferences → enable "Low Latency Mode." Twitch defaults to 5–8 seconds; Low Latency reduces this to 2–3 seconds.
3
Reduce OBS network buffer. OBS Settings → Advanced → Network → "Use network optimizations" ON → set network buffer to 0 KB. A large network buffer gives your stream more resilience to brief connection dips but adds latency. For interactive streams, a smaller buffer is preferable.
4
Disable B-frames for NVENC. OBS Settings → Output → NVENC H.264 → B-frames: set to 0. B-frames (bidirectional frames) improve video quality slightly but add 1-2 frames of encoder latency per B-frame. Disabling them reduces encoding latency at negligible quality cost for live streams.
Issue 10 — Viewer-Side Buffering
MEDIUM
ISSUE 10 · Viewer Buffering
VIEWERS REPORT BUFFERING / FREEZING
OBS shows no issues on your end — viewers experience freezing and loading spinners
Symptoms
- Viewers report buffering, you see no OBS issues
- Affects some viewers, not others
- Happens at peak hours (platform traffic high)
- Viewers on mobile buffer more than desktop
Root Causes
- Stream bitrate exceeds viewer's connection speed
- Platform CDN delivery issue (not your fault)
- Bitrate fluctuation causing viewer player rebuffering
- Ingest server overloaded, causing CDN issues
Fix Priority
- First: Reduce stream bitrate to 4,500 kbps max
- Second: Switch ingest server region
- Third: Check platform status page
- Fourth: Use CBR for more consistent delivery
🔧 Step-by-Step Fix
1
Reduce bitrate to 4,500–5,000 kbps if above. Platforms transcode your high-bitrate stream into multiple quality options for viewers. If your input bitrate is too high (above 6,000 kbps for most platforms), the transcoding can create artifacts and buffering at the CDN edge. YouTube recommends 4,500–6,000 kbps for 1080p; Twitch recommends 3,500–6,000 kbps.
2
Check platform status pages for CDN issues. If multiple viewers in different locations are buffering simultaneously and your OBS shows clean output, the problem is almost certainly on the platform's CDN side. status.twitch.tv and status.youtube.com show real-time platform issues. If there's a CDN incident, wait — nothing on your end will fix a platform CDN problem.
3
Try a different ingest server. Ingest servers relay your stream to the platform's CDN. An overloaded ingest server produces intermittent CDN delivery issues that manifest as viewer buffering even when OBS shows clean stats. Switching to a different ingest server in the same geographic region often resolves this.
Issue 11 — Stream Won't Start
CRITICAL
ISSUE 11 · Won't Start
STREAM WON'T START — OBS ERROR
Clicking "Start Streaming" produces an error — nothing goes live
Symptoms
- OBS shows error popup when clicking Start Streaming
- "Failed to connect to server" error
- "Invalid stream key" error
- Worked yesterday, fails today
- Works on one platform, fails on another
Root Causes
- Stream key copied incorrectly or expired
- Firewall or antivirus blocking port 1935
- Platform ingest server is down
- OBS server URL incorrect for the platform
- Account not verified or restricted on platform
Fix Priority
- First: Regenerate and re-enter stream key
- Second: Check platform status for outages
- Third: Add OBS firewall exception
- Fourth: Try RTMPS (port 443) instead of RTMP
- Fifth: Check account streaming eligibility
🔧 Step-by-Step Fix
1
Regenerate your stream key on the platform and re-enter it in OBS. Platforms invalidate stream keys occasionally — especially after password changes, suspicious activity, or extended periods of inactivity. Go to your platform's Creator Studio/Dashboard → Stream Keys → Reset/Regenerate. Then copy the new key into OBS Settings → Stream → Stream Key. Never type it manually — copy/paste directly.
2
Check the platform status page before troubleshooting locally. If the platform's ingest servers are down, no local fix will work. Check status.twitch.tv, status.youtube.com, or your platform's status page. If there's an active incident affecting streaming, wait for it to resolve before proceeding.
3
Try RTMPS (port 443) instead of standard RTMP (port 1935). In OBS Settings → Stream → Server, change the RTMP URL to use port 443 if the platform supports it. Some corporate networks, ISPs, and firewalls block port 1935 (the standard RTMP port). Port 443 (HTTPS) is almost never blocked because it's used for all web traffic.
Example for YouTube: rtmps://a.rtmps.youtube.com:443/live2/ (instead of rtmp://a.rtmp.youtube.com/live2/)
4
Add OBS as a firewall exception in Windows Defender. Windows Security → Firewall & network protection → Allow an app through firewall → Add OBS Studio to both Private and Public network access. Windows Defender occasionally blocks OBS's outbound RTMP connection after updates, producing "failed to connect" errors even with a valid stream key.
Issue 12 — Platform-Specific Issues
Some streaming problems occur only on specific platforms due to each platform's unique encoder requirements, CDN behavior, or policy settings. These are the most common platform-specific issues and their fixes.
YouTube-Specific Issues
- "This stream is not optimized" warning in YouTube Studio: YouTube expects specific encoder settings. Ensure: H.264 codec, CBR rate control, keyframe interval exactly 2 seconds, audio codec AAC at 44100 or 48000 Hz, 128–320 kbps audio bitrate. The warning disappears when these parameters match YouTube's recommended settings.
- Stream scheduled but not appearing in search/browse: YouTube live streams don't appear in search until they go live. If a scheduled stream is not visible, it may have a privacy setting other than "Public" — check YouTube Studio → Content → Live tab → stream settings → visibility: Public.
- Super Chats not appearing: Super Chats require channel monetization to be enabled AND the stream to be set to "Public" and "Not made for kids." Check YouTube Studio → Monetization → Live streaming monetization settings.
Twitch-Specific Issues
- Twitch stream quality poor despite high bitrate: Twitch non-partners are limited to 6,000 kbps bitrate and may not receive transcoding options (720p, 480p, 360p quality levels for viewers). Without transcoding, all viewers must watch at your source quality — viewers on slow connections buffer. Becoming a Twitch Affiliate or Partner unlocks transcoding. Alternatively, reduce source bitrate to 4,500 kbps to be accessible to more viewers.
- Auto-hosting triggering unexpected content: Twitch's auto-host feature shows your viewers content from channels you follow when you're offline. Disable in Creator Dashboard → Settings → Channel → Hosting if undesired.
- "Your stream is being flagged for low quality" Twitch notification: Twitch's quality detection system flags streams below 720p or with excessive dropped frames. Increase resolution to at least 720p and ensure dropped frames stay below 5%.
General Platform RTMP Requirements
⚙️ Universal Platform-Safe OBS Settings Works on All Platforms
Video Codec
H.264 (not H.265/HEVC)
HEVC not supported by most platforms
Audio Codec
AAC
Not MP3, not Opus — AAC only
Audio Sample Rate
44100 Hz or 48000 Hz
Never 22050 Hz — causes audio issues
Audio Bitrate
160 kbps minimum
128 kbps absolute minimum
Keyframe Interval
2 seconds exactly
1 increases bandwidth; 3+ degrades quality
Rate Control
CBR
VBR causes problems on every platform
Video Bitrate Range
4,500–6,000 kbps for 1080p
Match to 75% of sustained upload
Profile
main (not high or baseline)
Pre-Stream Technical Checklist — Prevent Problems Before They Start
🔧 Pre-Stream Technical Verification Checklist
- Ethernet cable confirmed — not WiFi; WiFi adapter disabled in network settings
- Upload speed tested at fast.com — stream bitrate is max 75% of minimum speed
- OBS set to CBR with keyframe interval of exactly 2 seconds
- Encoder set to NVENC/AMF if GPU available — not x264 unless hardware encoding unavailable
- All non-essential apps closed — browser, Discord video, cloud sync disabled
- Audio test recorded — 30-second clip played back to confirm quality
- Mic peaks confirmed in OBS mixer — -6 to -12 dB, never hitting red
- Sample rates matched — OBS, Windows mic, Windows playback all set to 48000 Hz
- GPU temperature under 80°C and CPU under 75°C before starting
- Test stream run to "unlisted" or secondary account for 3 minutes — review playback
- Stream key confirmed — pasted directly from platform dashboard, not typed
- Platform status page checked — no active incidents before going live
- Nearest ingest server selected — not "Auto" if you had connection issues previously
- OBS auto-reconnect enabled — Settings → Stream → retry delay 2s, max retries 20
- Backup audio device configured and muted in OBS, ready to unmute if primary fails
- OBS log open (Help → Log Files → Current Log) to monitor for issues during stream
The most reliable way to have a problem-free stream is to have a problem-free pre-stream. The checklist above is the difference between streams that run smoothly and streams that fail mid-session. Most mid-stream problems are caused by conditions that were already present before the stream started — conditions that a 5-minute pre-stream check would have caught. Build the checklist into your routine. It costs 5 minutes before every stream and saves 20+ minutes of mid-session panic over the course of a year.