How to Fix OBS Studio Browser Source High CPU Usage
This article provides a practical troubleshooting guide to help you resolve high CPU usage caused by browser sources in OBS Studio. You will learn how to optimize your settings, configure hardware acceleration, and manage your overlays to ensure a smooth, lag-free streaming and recording experience.
Enable Hardware Acceleration
By default, OBS Studio can render browser sources using your CPU, which quickly drains system resources. Enabling hardware acceleration offloads this work to your GPU.
- Open OBS Studio and go to Settings (located in the bottom right corner or under the File menu).
- Click on the Advanced tab in the left sidebar.
- Scroll down to the Sources section.
- Check the box next to Enable Browser Source Hardware Acceleration.
- Click Apply, then OK, and restart OBS Studio for the changes to take effect.
Optimize Browser Source Properties
Each browser source you add can run unnecessary background processes. You can minimize their impact by adjusting their individual properties.
- Double-click the problematic browser source in your Sources list to open its properties window.
- Check the box for Shutdown source when not visible. This stops the page from rendering when you switch to a different scene.
- Check the box for Refresh browser when scene becomes active if you want the overlay to reload fresh when you switch back to it.
- Lower the Resolution: If you are using a 1080p browser source for a small alert widget, reduce its width and height in the properties window (e.g., to 1280x720 or 640x480) and scale it down in your scene.
Consolidate Multiple Overlays
Running multiple individual browser sources (one for alerts, one for chat, one for a goal bar) forces OBS to run multiple instances of the Chromium browser in the background.
- Use an All-in-One Overlay: Most major streaming toolkits (like Streamelements or Streamlabs) allow you to combine your alerts, chat, and widgets into a single custom overlay scene.
- Reduce the Source Count: Replace three or four separate browser sources with one single browser source URL that contains all your widgets.
Limit Frame Rates on Heavy Web Pages
If you are hosting a custom local HTML file or a complex webpage as a browser source, complex JavaScript animations can cause CPU spikes.
- Cap the FPS: If the browser source supports it, limit its frame rate to 30 FPS instead of 60 FPS.
- Optimize Code: If you wrote the custom overlay
yourself, avoid heavy CSS filters (like
blurordrop-shadow) and complex loop animations. Use lightweight CSS transitions instead.
Update OBS Studio and Graphics Drivers
Outdated software can lead to compatibility issues between the Chromium Embedded Framework (CEF) used by OBS and your graphics card.
- In OBS Studio, click Help in the top menu and select Check For Updates. Install any pending updates.
- Update your graphics card drivers to the latest stable version via NVIDIA GeForce Experience, AMD Software, or Intel Graphics Command Center.