Chrome
Search Settings for graphics acceleration, enable it if available, and relaunch. In the graphics report, inspect Graphics Feature Status, WebGPU and Problems Detected.
Official Chrome guidanceBrowser graphics / Troubleshoot
Hardware Acceleration Test
Check available browser graphics paths and software rendering signs, then troubleshoot and retest. Some system settings need manual confirmation.
Run a check → save a baseline → inspect settings → restart your browser → run again → compare the two reports below.
Ready. Detection starts only when you choose to run it.
Local / No account
Reports & comparison
Up to 20 reports, stored only in this browser. A pinned baseline is retained. Imported reports are unverified external data.
Imported report text is shown in its original language.
Local history (0/20) · Select two to compare
No saved reports yet. Run a test or import a report.
Check your browser, then retest
Internal addresses must be pasted into the address bar. This website cannot open or read those pages, or change browser settings. Labels vary by version and managed policies.
Edge
Open System and performance and find the graphics acceleration setting. Apply changes and restart Edge, then inspect Graphics Feature Status and driver messages.
Official Edge guidanceFirefox
In Settings → General → Performance, clear Use recommended performance settings to inspect hardware acceleration when available. Restart Firefox. In Troubleshooting Information, inspect the Graphics section and decision log.
Official Firefox guidanceOther browsers and system checks
Update the browser and graphics driver from their official providers. Inspect graphics settings and any remote desktop, virtual machine or managed policy restrictions. Restart after changes, then repeat this check. For Safari, use Apple’s official Safari help . Do not infer permanent platform restrictions from one failed request.
How to use this result
Run detection in the foreground. WebGPU requests an adapter and device, compiles a shader, draws a triangle and checks pixels, then doubles four numbers and checks the result. WebGL 2 and WebGL 1 each draw a triangle and read a pixel. Save your result before changing settings; run again afterward.
A working graphics path does not confirm browser-wide acceleration. Low FPS is not software-rendering evidence. Frame rates depend on display refresh, browser scheduling and workload. See the methodology for validity and comparison rules.
Frequently asked questions
Can this detect my exact GPU model?
Only if your browser exposes it. Adapter information may be empty, generic or privacy-limited. This tool does not guess a model.
Why does it show integrated graphics?
The browser and operating system select the graphics path. Power preferences are requests, not proof that a discrete GPU is selected. Inspect your operating system graphics settings.
Why is the model hidden?
Privacy protections and unavailable debug extensions can hide identifying information. On Windows, inspect Task Manager → Performance → GPU or Device Manager → Display adapters. On macOS, inspect System Information → Graphics/Displays. These list system devices, not proof of which device this tab uses.
Why do browsers report different devices?
Browser versions, rendering backends, privacy settings, drivers and device selection can differ. WebGPU and WebGL sources are shown separately even when they disagree.
Can it read temperature or video memory?
No reliable temperature, fan, voltage, clock or total VRAM readings are available to this page. API limits such as maxBufferSize are not VRAM capacity.
What does a passed check mean?
This small workload produced the expected readback in this browser. It is not hardware health certification, a stress test, or a guarantee that every graphics application will work.