# My Computer Specs > What graphics card does your browser use? Is hardware acceleration on? WebGPU, CPU threads, RAM, Windows 10 or 11, plus a local AI test. Nothing uploaded. - URL: https://bytescope.dev/en/my-computer-specs/ - Locale: en · Also: [ja](https://bytescope.dev/ja/my-computer-specs.md) · [zh-Hant](https://bytescope.dev/zh-Hant/my-computer-specs.md) - Runs: Your files never leave your browser — all processing is local. - Requires: Any modern browser (Chrome, Edge, Firefox, Safari), desktop and mobile. Chrome and Edge expose the most (GPU adapter, OS version, RAM); Firefox and Safari show fewer fields and the page says which ones. - Updated: 2026-09-08 ## What it does A browser is not a system-information utility, but it does know a lot about the machine it runs on, and this page shows you all of it in one place: the graphics card the browser is actually drawing with, whether hardware acceleration is on or Chrome has fallen back to software rendering, which WebGPU features and limits are available, how many CPU threads you have, how much RAM the browser is willing to admit to, which OS and version you are on, and what your screen can do. Every row is labelled measured, estimated or “the browser does not expose this”, so you always know how much to trust a value. Nothing runs on a server: detection needs no network, there is no share button, and the Copy JSON button only puts a report on your clipboard for you to paste into a support ticket or a forum post — it includes the number of installed fonts, never their names. ### Shown as soon as the page loads The GPU the browser is using, from the WebGPU adapter (vendor and architecture) and the WebGL renderer string. The page asks twice — once for a low-power adapter and once for high-performance — and lists both when they differ, which is how you find out that your laptop has a dedicated GPU the browser is not using. Whether hardware acceleration is on, off, or whether Chrome fell back to a software renderer: SwiftShader, `llvmpipe` on Linux, or “Microsoft Basic Render Driver” on Windows. WebGPU features such as `shader-f16`, `subgroups` and `timestamp-query`, and the adapter limits — these are not VRAM, and the page says so. Logical CPU threads from `navigator.hardwareConcurrency`, which counts threads, not cores. CPU architecture and bitness via UA Client Hints, Chromium only — this is also how it tells an Apple Silicon Mac from an Intel one. OS name and version: Windows 11 still says “Windows NT 10.0” in the user agent and macOS has been frozen at “10_15_7” for years, so the real version comes from UA Client Hints on Chromium and is an estimate everywhere else. RAM from `navigator.deviceMemory`, rounded and capped, so the top value means “at least”. Screen resolution, device pixel ratio, colour depth, colour gamut, HDR and a measured refresh rate. Browser and version. A network type estimate — not a speed test. Touch points and pointer precision. Battery level and charging state, which on a desktop usually reads 100 % and charging. ### Shown only when you click Some things need a permission prompt or a device gesture, so each of these is a button that asks only when pressed: cameras and microphones (names need permission; the streams are stopped the moment the names are read), speakers, all connected screens, installed fonts (count and list, Chromium only), MIDI devices, and gamepads (press a button on the controller so the browser can see it). USB, HID and serial devices are not listed here — the site's USB device info, HID inspector and serial monitor tools each do that properly. This page is also the entry point for the site's hardware checks: the screen test, HDR test, codec check (can this machine hardware-decode HEVC and AV1?), webcam, microphone, speaker, gamepad and MIDI tests, the speech-model comparison and the Chrome built-in AI test. ### Can this computer run local AI? One button runs the test. It checks whether WebGPU is available, whether the adapter is a software renderer, whether `shader-f16` is supported, and whether a 256 MB and a 1 GB GPU buffer can actually be created. Then it runs a short matrix-multiply benchmark — under ten seconds, and your fans may spin up — and reports GFLOPS as a median with the p10–p90 range, because a single number from a laptop on battery is noise. Finally it tells you which build of the site's live-captions speech models this browser would pick, and how large that download is. There are exactly four conclusions: this machine can run the site's WebGPU models; it runs, but only on software rendering and will be very slow; WASM only; or this browser has no WebGPU. There is no ranking and no percentile, because there is no crowd data behind the page to rank against. Chrome's built-in AI (Gemini Nano) is a separate question and links to the built-in AI test. Benchmark numbers move with power, heat and other tabs: on a laptop, plug in and close other tabs before you read too much into them. ### What you will not see, and why No VRAM, no CPU model, no disk size. Browsers deliberately do not expose them, because together with the values above they would make a browser far easier to recognise across sites. Rather than guess, this page says “the browser does not expose this” and leaves it there. The storage quota is not used to estimate disk size either, because it is a per-site budget and not a measurement of your drive. Two more honest limits: “the GPU the browser uses” is not always “your graphics card” — dual-GPU laptops often hand the browser the integrated GPU, the operating system can assign a GPU to the browser (on Windows: Settings → System → Display → Graphics, pick the browser, set it to high performance), and the power-preference hint may be ignored on some platforms. And Firefox and Safari may coarsen the renderer string: Safari often reports just “Apple GPU” and cannot tell an M1 from an M3. ### The same facts are a fingerprint The values that answer “what are my specs” — the renderer string, the font list, the screen size, pixel ratio and colour depth combination, the time zone, the language, the thread count — are exactly what trackers combine to recognise a browser without a cookie. That is why so many of them are rounded, capped or missing. Some browsers go further: Firefox with `resistFingerprinting`, Safari and Brave may coarsen or randomise several of these values, and if you use one of them, a few rows here will look wrong on purpose. This page does not rank browsers on privacy and does not compute a uniqueness score; it only shows you what the page you are reading could already see. ## Limits Does not show VRAM, the CPU model or disk size (browsers do not expose them), does not rank your hardware against other machines, and does not upload or store anything. Values a browser rounds or hides are labelled estimated or not exposed rather than guessed. ## FAQ ### Why don't I see my dedicated GPU? Because the browser is probably not using it. On a laptop with both an integrated and a dedicated GPU, the operating system often gives the browser the integrated one to save power, and the browser reports what it draws with — not what is installed. This page asks for a low-power and a high-performance adapter separately and shows both when they differ, but the hint may be ignored on some platforms. On Windows you can choose: Settings → System → Display → Graphics, add your browser, set it to High performance, then restart the browser and reload this page. Safari and Firefox may also coarsen the renderer string, so a short or generic name there is the browser being deliberately vague, not a missing card. ### Why is there no CPU model or VRAM? Browsers do not expose them. A CPU model, the amount of video memory and the disk size would make a browser much easier to recognise across sites, so none of the web APIs report them, and this page does not guess — rows that cannot be known say “the browser does not expose this”. What you do get is the number of logical CPU threads (`navigator.hardwareConcurrency`, threads not cores, and some browsers lower it), the GPU vendor, architecture and renderer string, and the WebGPU adapter limits — which are buffer and binding sizes, not VRAM. ### What is SwiftShader, and how do I turn hardware acceleration back on? SwiftShader is the software renderer Chrome falls back to when it cannot, or is not allowed to, use the GPU: everything is drawn on the CPU, so video, WebGL and WebGPU get slow and the fans spin. On Linux the equivalent is `llvmpipe`, on Windows it shows up as “Microsoft Basic Render Driver”. If this page says software rendering, or that acceleration is off, check the switch: in Chrome open Settings → System and turn on “Use graphics acceleration when available”, then Relaunch; in Edge it is Settings → System and performance, same switch. Note that in recent Chrome versions, turning acceleration off may remove WebGL and WebGPU entirely rather than fall back to SwiftShader, and this page reports that state as “hardware acceleration is off”. ### Does this page upload my data? No. Every value is read from browser APIs in this tab, the detection needs no network, and nothing is sent anywhere. There is no share button. The only way data leaves is the Copy JSON button, which puts a report on your clipboard so that you can paste it into a support ticket or a forum post yourself — and even that report lists how many fonts are installed, never which ones. ### Am I on Windows 10 or 11? The user agent cannot tell you: Windows 11 still identifies itself as “Windows NT 10.0”, exactly like Windows 10. On Chrome and Edge this page asks for the high-entropy UA Client Hints instead, where a platform version of 13 or higher means Windows 11, and shows the result as measured. On Firefox and Safari there are no Client Hints, so the row is an estimate and says so. The same applies to macOS, whose user agent has been frozen at “10_15_7” since Catalina regardless of the real version. ### How much RAM do I have? The page shows `navigator.deviceMemory`, which is rounded to a power of two and capped. Measured on 2026-10-01, Chrome 154 on desktop reports at most 32, while older browsers, and possibly phones, stop at 8, so the top value means “at least” — a machine with 64 GB shows as 32, and a phone with 12 GB may show as 8. Firefox and Safari do not implement the API at all, so there the row reads “the browser does not expose this”. For the exact figure, use your operating system's own settings. ### Is this an Apple Silicon or an Intel Mac? On Chrome and Edge the page reads the CPU architecture and bitness from UA Client Hints: `arm` with 64 bits is Apple Silicon, `x86` is Intel. In Safari the user agent says “Intel Mac OS X” on every Mac, including M-series ones, and the GPU renderer often reads just “Apple GPU”, so Safari cannot answer this question and the row is marked as not exposed. The WebGPU adapter architecture, when available, is a second hint. ### Why does my phone show “not exposed” for so many rows? Because mobile browsers expose less. iOS Safari has no UA Client Hints, no `deviceMemory`, no battery API, no local-fonts API and no multi-screen API, and Firefox is similar, so on a phone a large part of the table is honestly empty — which is itself information: it tells you what a website can and cannot learn about your device. Chrome on Android fills in more of them. Everything that can be measured on a phone — screen, pixel ratio, refresh rate, touch points, GPU renderer and the WebGPU test — still works. ## Related tools - [Display & Monitor Test](https://bytescope.dev/en/screen-test.md) — Dead pixels, backlight bleed, refresh rate and colour patterns → - [Codec Check](https://bytescope.dev/en/codec-check.md) — Which video codecs this browser can decode in hardware → - [Built-in AI Test](https://bytescope.dev/en/built-in-ai-test.md) — Is Chrome's built-in Gemini Nano available here? → - [Phone Sensor Test](https://bytescope.dev/en/phone-sensor-test.md) — On a phone? Test its motion sensors, compass, GPS and vibration live.