Smart Floor Lamp Setup For Your Gaming Room: A Beginner’s Matter Guide
A good gaming setup is more than a fast controller and a sharp screen. The light around you changes how long you can…
Only in Chrome my screen flickers, especially when scrolling or watching videos. Sometimes parts go black for a split second. Games and other apps are fine. Your FPS test also flickers in Chrome but not in Edge. What's going on?
Flicker in one browser usually comes from how it uses the graphics card. Update the graphics driver first. If it continues, try turning hardware acceleration off in Chrome to test, check Chrome's graphics settings flags are default, and test with variable refresh off.
Since the flicker appears in Chrome but not in Edge or games, the issue is how Chrome is drawing through your graphics card, not the monitor.
Update the graphics driver first. Browser flicker issues are frequently caused by driver bugs and fixed in later releases. Restart afterwards.
Test hardware acceleration. In Chrome's settings, under System, turn off the option to use graphics acceleration when available, and restart Chrome. If the flicker stops, the driver and Chrome are not getting on. Hardware acceleration is generally better on, so after a driver update, turn it back on and test again.
Check for experimental settings. If you have changed anything in Chrome's flags page, reset them all to default.
Variable refresh. With G-Sync or FreeSync, some setups flicker in browsers as the refresh rate changes during scrolling. Test with variable refresh off, or set Chrome to fixed refresh in the graphics driver's per-app settings.
Multiple monitors with different refresh rates can also cause it, so test with one monitor connected.
Our FPS test is a good repeatable check after each change.
Tested on: Applies to Chrome on Windows 11 with NVIDIA, AMD or Intel graphics. Frame timing per MDN's requestAnimationFrame documentation.
Checked by Simon Fletcher on . How we verify answers
Front-End Web Architect And Gamepad API Lead at Gamepad Tester
Calder is a front-end web architect working with the HTML5 Gamepad API. His focus is the part most browser testers get wrong: reading a controller often enough, and timing it well enough, that the numbers on screen match what the hardware is actually sending. He writes the polling loops that capture analog trigger tension and stick travel without dropping samples, and renders them on 2D vector layouts that hold a steady 60+ FPS on ordinary laptops. On Gamepad Tester he maintains the main tester tool, the button test and the trigger pressure test, and reviews any answer that explains how a reading on this site should be interpreted.
Each answer is written by the specialist who owns that part of the hardware, tested on a real controller, and checked by a second team member. How we verify answers
Answers are free general guidance from the Gamepad Tester Team and the community. Opening a controller or replacing a thumbstick module can void your warranty, so check the maker's support or warranty first. Battery and soldering work carries a real risk of damage or injury.
Every test runs in your own browser with the Gamepad API. No sign up, no download, and your controller data never leaves your device.
A good gaming setup is more than a fast controller and a sharp screen. The light around you changes how long you can…
Gaming stopped being a teenage hobby a long time ago. The Entertainment Software Association's 2025 report put the…
Android RPGs no longer feel like small games made to fill a few spare minutes. Some now offer large open worlds…
The newest replies from players and the Gamepad Tester Team.