Fix overlay delay

A delay on a controller overlay comes from one of two places: the time the browser takes to read and draw the button state, or the time your streaming software takes to mix and encode that drawing into the stream. It is almost always a setting, not a hardware fault. Here are the causes, from the most frequent to the least.

Is the Browser Source frame rate too low?

Most common

If the Browser Source runs below your canvas frame rate, for example 30 FPS in a 60 FPS scene, the overlay looks late or choppy next to your gameplay, even though your inputs are read instantly.

Fix In OBS, open the Browser Source properties, enable Use custom frame rate and set it to your output frame rate, usually 60 FPS.

Is hardware acceleration off?

OBS and Streamlabs draw Browser Sources with a built-in browser engine. When hardware acceleration is off, that drawing falls back to the CPU and can lag visibly under load.

Fix In OBS, go to Settings, Advanced, enable Browser Source Hardware Acceleration, then restart OBS.

Is the page throttled in the background?

Browsers slow down tabs that are in the background. If you test the overlay in a regular tab behind your game, it can look late, while the same overlay runs smoothly inside a Browser Source.

Fix Always judge responsiveness from the OBS or Streamlabs preview, never from a background tab.

Is the connection adding latency?

Bluetooth and 2.4 GHz dongles add a little latency compared with a USB cable, usually a few milliseconds. It is rarely visible on its own, but it can add up with the causes above.

Fix When every millisecond matters, for competitive checks or rhythm content, play wired.

Is the encoder dropping frames?

An overloaded encoder, common with a high bitrate and resolution on modest hardware, drops frames across the whole scene. The overlay stutters too, which looks like overlay lag but is not.

Fix Check the OBS Stats window for rendering or encoding lag. If a counter keeps rising, lighten the scene first: remove duplicate Browser Sources and keep their size close to what is displayed. Lower the output settings only if the scene still drops frames.

How do I measure the delay myself?

1. Set your phone to slow motion, 240 frames per second if it can.
2. Film your hands and your monitor together, with the OBS preview on screen.
3. Tap a button a few times, then step through the video frame by frame.
4. Count the frames between your thumb pressing and the overlay reacting. At 240 frames per second, one frame is about 4 milliseconds.

Your monitor adds its own delay to both the game and the overlay, so compare the two on the same footage rather than trusting an absolute number.

How much delay is normal?

If the overlay reacts within one or two frames of the game on your recording, 17 to 33 milliseconds at 60 FPS, it is working as intended. Viewers watch your stream several seconds late, but the game and the overlay are delayed together: what matters is that they stay in sync with each other.

FAQ