Problem
High-resolution browser sources consume GPU resources and trigger rendering lag even though encoder utilization appears acceptable.
Solution
Root Cause / Diagnostic:
Browser sources render web pages via embedded Chromium (CEF) processes that offload 2D/3D compositing, DOM reflows, and CSS animations onto the system GPU. When browser sources are set to unnecessarily high canvas resolutions (such as 4K or unscaled 1440p) or execute unthrottled JavaScript animations, GPU 3D rendering usage peaks. This starves the OBS compositing thread and induces severe rendering lag despite hardware video encoder (NVENC/VCE) utilization staying well within safe margins.
Actionable Fix:
1. Downscale browser source width and height in source properties to match the exact display dimensions on the canvas (e.g., set to 1920x1080 or custom widget sizes like 600x800 rather than native monitor resolution).
2. Enable 'Shutdown source when not visible' and 'Refresh browser when scene becomes active' on all non-essential browser sources to reclaim GPU VRAM.
3. Open the OBS Stats window (View > Stats) and monitor 'Frames missed due to rendering lag' to confirm render frame drop drops to 0.0%.
Pro Tip:
Consolidate third-party alerts, stream overlays, and event feeds into a single unified browser overlay URL within services like StreamElements, drastically reducing CEF process overhead.
Browser sources render web pages via embedded Chromium (CEF) processes that offload 2D/3D compositing, DOM reflows, and CSS animations onto the system GPU. When browser sources are set to unnecessarily high canvas resolutions (such as 4K or unscaled 1440p) or execute unthrottled JavaScript animations, GPU 3D rendering usage peaks. This starves the OBS compositing thread and induces severe rendering lag despite hardware video encoder (NVENC/VCE) utilization staying well within safe margins.
Actionable Fix:
1. Downscale browser source width and height in source properties to match the exact display dimensions on the canvas (e.g., set to 1920x1080 or custom widget sizes like 600x800 rather than native monitor resolution).
2. Enable 'Shutdown source when not visible' and 'Refresh browser when scene becomes active' on all non-essential browser sources to reclaim GPU VRAM.
3. Open the OBS Stats window (View > Stats) and monitor 'Frames missed due to rendering lag' to confirm render frame drop drops to 0.0%.
Pro Tip:
Consolidate third-party alerts, stream overlays, and event feeds into a single unified browser overlay URL within services like StreamElements, drastically reducing CEF process overhead.