Browser reports software graphics rendering: what to do

System Info says your browser is using software graphics rendering, and you are wondering whether the graphics card is broken. That message can be worrying, but it does not prove the GPU has failed.

Use the System Info and GPU Test to check what the browser reports and how a graphics workload behaves. Then try the settings most likely to change the result.

Check the renderer and test graphics

1. Open System Info and look at the graphics information. Note any wording that identifies software rendering, along with your browser name and version.
2. Open the GPU Test in the same browser. Run it once and note whether it completes, stutters, freezes, or shows a very low score.
3. Check how you are using the computer. A remote desktop session or virtual machine can expose a virtual graphics device or a software renderer instead of your computer's physical GPU.
4. After trying the fixes below, repeat both checks in the same browser and on the same computer. Changing several things at once makes it harder to tell what helped.

The GPU Test is a browser graphics workload, not a complete inspection of the graphics card. Its score can change with browser settings, other open programs, power mode, and device temperature.

What the result means

Software rendering is reported, but the GPU Test completes

The browser may be using a software path for some graphics work, but the successful test does not establish exactly which parts of the device use the GPU. A browser can use different paths for page drawing, video, and 3D content. The renderer label alone is not a hardware fault diagnosis.

The GPU Test is very slow or does not complete

This points to a graphics problem in the browser or its environment, but it still does not identify the cause. Hardware acceleration may be disabled, the browser may have blocked a driver, or the session may be running through a virtual or remote display.

The result changes between sessions

If software rendering appears only in a remote session, virtual machine, or one browser profile, the graphics setup or browser configuration is a more likely cause than a failed GPU. Compare results from a normal local desktop session before considering repair.

How to fix it

1. Restart the browser. Close all browser windows, then reopen the browser and run the checks again. If the message appeared after a graphics or browser crash, restart the computer too.
2. Turn on browser graphics acceleration. In Chrome, open Settings › System and enable Use graphics acceleration when available, then relaunch the browser. In Edge, open Settings › System and performance and enable Use graphics acceleration when available, then restart Edge. In Firefox, open Settings › General › Performance, clear Use recommended performance settings, and enable Use hardware acceleration when available.
3. Choose the high-performance graphics option in Windows. In Windows 11, open Settings › System › Display › Graphics, select or add your browser, choose Options, then select High performance if that choice is available. This can help laptops with both integrated and dedicated graphics. Close and reopen the browser afterward.
4. Update the graphics driver and operating system. In Windows 11, check Settings › Windows Update for updates, including optional driver updates. If the problem continues, use the computer or graphics card maker's official driver update method. On a Mac, open System Settings › General › Software Update. macOS normally manages graphics selection automatically and does not offer a general per-browser high-performance switch.
5. Test outside a remote session or virtual machine. Sign in directly at the computer and repeat the tests. If you must use a virtual machine, check its settings for 3D acceleration. The option and its name depend on the virtualization software.
6. Undo graphics-related browser changes. If you changed experimental browser flags or a setting that disables acceleration, restore the default setting and restart the browser. You can also try the test in another up-to-date browser to see whether the result is specific to one browser.

When the GPU may need service

A software renderer label by itself is not a reason to replace a graphics card. The case for hardware service is stronger if graphics glitches also appear in desktop applications or games, the computer crashes under graphics load, or the same symptoms remain after driver updates and a local-session test.

A browser test cannot confirm a damaged graphics chip or memory. If the computer shows artifacts across several applications, save any important work and contact the computer maker or a repair shop. For a desktop PC, a technician can check the card, its power connections, and cooling before you buy a replacement.

Why a browser chooses software rendering

Browsers sometimes avoid a graphics feature when a driver is known to be unreliable, acceleration has been turned off, or the browser has recently crashed. Remote desktop software and virtual machines can also change which graphics device the page can see. A software renderer is often a fallback that keeps pages working, even if drawing them is slower.

If the message appears only on one website or one graphics test, rather than in System Info, see what to check when a page falls back to software rendering.