Common symptoms
- Video, canvas, or 3D content stutters
- WebGL renderer suggests SwiftShader or software rendering
- Browser CPU usage rises during visual workloads
Possible causes
- Hardware acceleration switched off in browser settings
- Driver blocklist or outdated graphics driver
- Remote desktop or virtual machine fallback
- GPU process crash or enterprise browser policy
How to diagnose it
- Run the DeviceTriage GPU test and inspect the renderer label
- Check the browser's internal graphics status page
- Restart after toggling hardware acceleration
- Retest outside remote desktop when possible
Solutions to try
- Enable hardware acceleration in browser system settings
- Update the graphics driver from the device or GPU vendor
- Update the browser and operating system
- Remove experimental graphics flags before retesting
- Contact an administrator if a managed policy disables acceleration
Frequently asked questions
Is a hidden renderer string a problem?
Not by itself. Browsers may hide or generalize renderer details for privacy while graphics acceleration still works.
Should hardware acceleration always be enabled?
Usually, but a specific driver bug can make disabling it a useful temporary comparison. It is not a universal fix.