OBS 33: overlay stops when OBS is not focused

This is a known regression in OBS Studio 33, confirmed by the OBS developers on Windows and on macOS. It affects every controller overlay that runs in a Browser Source, not only Padcraft. Nothing needs to change in your design or your link.

Is this your problem?

It is, if all of the following are true:

• you use OBS Studio 33.0 or later (Help, About shows the version);
• the overlay reacts while the OBS window is in front;
• it freezes, or stops reacting, as soon as you click into your game or any other window;
• it reacts again the moment you click back on OBS.

If the overlay never reacts, even with OBS in front, this guide is not the right one: see Controller not detected.

What changed in OBS 33?

OBS 33.0, released on 23 October 2026, updated the browser inside OBS from version 127 to version 150 of Chromium. On Windows, that version of Chromium reads controllers through the Windows Gaming Input interface, and Windows only sends controller input to the application that has focus. While you play, the game has focus, so the Browser Source receives nothing. The setting that used to turn this behaviour off no longer exists in Chromium 150. On macOS, a separate bug in the same Chromium version produces the same symptom.

Chrome and Edge behave the same way when they are in the background. This is why no web-based overlay, Padcraft included, can work around it from its own page. The OBS developers track the issue on GitHub for Windows and for macOS (both checked on 6 November 2026).

Fix 1: go back to OBS 32.2.2

This is the fix the OBS developers suggest, and the only one that works for everyone, on Windows and on macOS. OBS 32.2.2 is the last version before the change.

1. Back up your setup. In OBS, open Scene Collection, Export and Profile, Export, and save both files somewhere safe.
2. Download OBS 32.2.2 from the official OBS release page on GitHub. Pick the installer for your system. Do not download OBS from any other site.
3. Install it over OBS 33. Your scenes are normally kept. If one is missing, import the files you exported in step 1.
4. Stop the update prompt. In Settings, General, clear Automatically check for updates on startup, so OBS does not offer version 33 again before the fix ships.
5. Check the overlay. Open your game, play for a few seconds, and watch the preview in OBS: the overlay should follow your inputs.

Fix 2: run OBS as administrator (Windows)

Several users report that the overlay follows their inputs again when OBS runs with administrator rights. It is quicker than going back to 32.2.2, but it does not work on every computer: Steam Input, User Account Control settings or an antivirus can prevent it. It does not apply to macOS.

1. Close OBS completely, including from the icon next to the clock.
2. Right-click the OBS shortcut, then choose Run as administrator.
3. Start your game and check the overlay as in Fix 1.
4. If it works, make it permanent: right-click the shortcut, choose Properties, open the Compatibility tab and tick Run this program as an administrator.

If the overlay still freezes, use Fix 1.

What does not work

• Refreshing the Browser Source or recreating it. The page is not the problem, so a new one behaves the same way.
• Launch options found online. The option --disable-features=EnableWindowsGamingInputDataFetcher fixed a similar issue in OBS 31, but it no longer exists in OBS 33. Other options that circulate do not restore background input either, according to the OBS developers.
• Another overlay website. Every overlay that runs in a Browser Source is affected in the same way.

When will it be fixed?

The OBS team has confirmed the regression and is preparing a patch to the browser it ships, for Windows and for macOS. No release date has been announced as of 6 November 2026. We follow both issues and will update this page as soon as a version of OBS fixes it.

FAQ