60-second overlay lag check
- Watch the overlay inside OBS, not in a background browser tab.
- Open Browser Source properties and match its custom frame rate to your stream, usually 60 FPS.
- Open OBS Stats. If rendering or encoding lag rises, simplify the scene before changing the controller.
- Use a smaller Browser Source viewport and remove duplicate browser sources.
- Compare wired and wireless input with the controller latency test.
The short version
- Overlay delay is almost never the controller's fault — it's your Browser Source or your encoder.
- Check these two first: Browser Source FPS matching your canvas, and hardware acceleration enabled. Together they explain most cases.
- If the whole scene stutters and not just the overlay, you're encoder-bound — no overlay setting will fix that.
- Wireless adds real latency, but it's milliseconds. If your overlay looks visibly behind, the cause is in software.
Jump to a cause
Input lag on a controller overlay comes from one of two places: the time it takes your browser to read and render the button state, or the time your streaming software takes to composite and encode that render into your output. In practice, it's almost always a setting, not a hardware fault. Here are the causes in order of how often they're the actual problem.
1. Browser Source FPS set too low
Most common Browser Source frame rate
If your Browser Source's custom FPS is set below your canvas frame rate (say, 30 FPS while your scene runs at 60), the overlay will visually lag or feel choppy compared to your gameplay capture — even though the underlying input reading is instant.
Fix: in OBS, open the Browser Source properties, enable Use custom frame rate, and set it to match your stream output — usually 60 FPS. The audio-control option is unrelated to frame rate.
2. Hardware acceleration disabled
GPU rendering for the browser source
OBS and Streamlabs render Browser Sources using an embedded browser engine. If hardware acceleration is off (system-wide in OBS settings, or disabled to save GPU headroom), rendering falls back to software, which can introduce a visible delay under load.
Fix: in OBS, go to Settings → Advanced → check that "Browser Source Hardware Acceleration" is enabled, then restart OBS for the change to apply.
3. The overlay page gets throttled
Browser tab/process throttling
If you're previewing the overlay in a normal browser tab in the background while testing, most browsers throttle inactive tabs to save resources, which looks like lag but disappears once it's actually running inside a Browser Source (which isn't throttled the same way).
Fix: always judge overlay responsiveness from inside OBS/Streamlabs preview, not from a backgrounded browser tab.
4. Controller polling rate and wireless latency
Hardware-level input latency
Wireless controllers (Bluetooth or proprietary 2.4GHz dongles) add a small amount of latency compared to wired USB — typically a few milliseconds, rarely enough to be visually noticeable, but it can stack with other causes on this list.
Fix: if every millisecond matters (competitive verification, precise rhythm content), switch to a wired connection for the lowest possible input-to-render latency.
5. Encoder overload dropping frames
Whole-scene frame drops
If your encoder (CPU or GPU-based) is overloaded — common with high bitrate + high resolution on modest hardware — OBS will drop frames across the entire scene, including the overlay, which looks identical to overlay-specific lag but isn't.
Fix: check OBS's Stats window for rendering or encoding lag. If either counter keeps rising, reduce scene load first: remove duplicate Browser Sources, keep their width and height close to the displayed size, and lower output settings only if the full scene still drops frames.
Run our free tool to measure your controller's raw input latency and polling rate.
Test your controller latency →Follow our full walkthrough for OBS, Streamlabs and TikTok LIVE Studio.
Read the setup guide →