Is this accurate, and does it show my real CPU and GPU?

It shows what the browser is willing to report, and every browser hides something. Chrome and Edge give the exact thread count and GPU name and round memory to a coarse value. Firefox names only the GPU maker. Safari and every iPhone browser report CPU threads only as under 8 or 8+, show the GPU as Apple GPU and give no memory figure.

Can it show my exact CPU model and how much RAM I have?

No. Browsers don't let a web page read the CPU model, its clock speed or your exact RAM. You get the thread count (Safari only says under 8 or 8+). Chrome, Edge and Opera add a rounded memory figure, and no other browser does. On an Apple silicon Mac, Chrome and Edge do name the chip, because it's part of the GPU name. For the exact model and RAM on Windows, open Task Manager and click the Performance tab. On a Mac, choose About This Mac from the Apple menu.

Why does device memory show 32+ GB when I have more RAM?

Chrome, Edge and Opera round your RAM to the nearest power of two and stop at 32 GB on a computer (8 GB on Android), so you are harder to track. A 64 GB PC reads 32+ GB, and a 12 GB laptop reads ~8 GB. Firefox and Safari don't report memory at all, so you'll see a dash there.

Is any of this sent to a server?

No. Every value is read in your browser with standard JavaScript and rendered on the page. Nothing is uploaded, logged, or stored. Share is the one exception: the link carries your specs and GPU verdict, so anyone who opens it sees them. It never carries your user agent, languages or timezone.

Why is my GPU shown as a generic name?

The GPU name comes from WebGL's debug renderer extension. Some browsers and privacy settings hide it. Firefox swaps the model for an older card from the same maker, so the page shows only the maker, like NVIDIA (model hidden). Safari reports every Apple chip as Apple GPU. With hardware acceleration off, older browsers fall back to a software renderer like 'Google SwiftShader', while current Chrome gives the page no WebGL at all, so GPU shows a dash and GPU acceleration reads Unavailable.

Does it show whether my GPU decodes AV1 or HEVC?

Yes. The 4K60 video decode group probes H.264, HEVC, VP9, and AV1. Hardware means your GPU has a dedicated decoder for that codec at 4K60, so playback stays smooth and light on battery. Software means the CPU does the work, which runs hotter and slower. A dash means the codec is unsupported.

Which GPUs hardware-decode AV1 and HEVC?

HEVC plays in hardware on most cards from the past several years. AV1 is pickier. As a rule it wants an NVIDIA RTX 30 series card or newer, an AMD Radeon RX 6000 series card or newer, Intel Arc or 11th-gen and newer Intel graphics, or an Apple M3 chip or later. A few budget cards in those lines skip AV1, which is why this tool checks your actual GPU instead of trusting a spec sheet.

A codec shows Software next to it. Should I worry?

Not really. Software decode still plays the video. The CPU just does the work, so the fan spins up and a laptop drains faster, and a 4K60 stream can stutter on an older chip. Updating your GPU driver sometimes adds the missing codec, and support varies by browser, so Chrome or Edge may read Hardware where Firefox shows Software.

Why does screen resolution differ from what I set in Windows?

The screen size is in CSS pixels. Multiply by the pixel ratio to get physical pixels: a 4K display at 150% scaling reports 2560×1440 with a 1.5× ratio. That math holds at 100% page zoom, because Chrome and Edge count page zoom in the ratio. For the panel size in real pixels, open the Screen Resolution Checker.

System Info

See what your browser reports about your machine: CPU threads, memory, GPU, screen, video decode and locale. Read locally in the browser, nothing uploaded.

Vadim Cheban October 28, 2026

Checking GPU

Asking your browser which renderer it draws with.

Hardware

CPU: -
CPU threads: -
Architecture: -
Device memory: -
GPU: -
GPU acceleration: -
Touch points: -

Display

Screen resolution: -
Viewport: -
Pixel ratio: -
Refresh rate: -

Browser & OS

OS: -
Browser: -
Languages: -
Timezone: -
User agent: -

4K60 video decode

H.264: -
HEVC: -
VP9: -
AV1: -

See your screen's real resolution in physical pixels

Everything is read locally in your browser and never uploaded. A dash means your browser doesn't report that field. Firefox hides the GPU model. Safari and every iPhone browser report CPU threads only as under 8 or 8+, and draw pages near 60 fps by default, so Refresh rate reads about 60 there. On a Mac, turn off Prefer Page Rendering Updates near 60fps in Safari's Feature Flags to see the full rate.

Everything below is read locally in your browser the moment this page opens. No permission prompt, nothing uploaded. Hit Copy all to grab the full report for a support ticket or forum post.

How to use

Open the page. Everything loads automatically. No permission prompt and no install. The readouts populate the moment the page opens.
Read your specs. Scan the Hardware, Display, Browser and video decode groups. A dash means your browser chose not to expose that field.
Copy the report. Hit Copy all to put the whole report on your clipboard, handy for a support ticket or a forum post.

Why test this

When you're filing a support ticket, posting on a hardware forum, or checking whether a site will run well, the first question is always 'what are you running?' Digging through OS settings for cores, GPU, and screen details is slow. This page answers it in one glance, straight from the browser that will actually run the web app or game you care about. That last part matters: a benchmark of your OS specs doesn't tell you whether hardware acceleration is even on in this browser, but the GPU string here does. If it reads as a software renderer, your browser isn't using the graphics card and pages will feel sluggish. Does your GPU play AV1 and HEVC without leaning on the CPU? Normally you'd install GPU-Z to check. The 4K60 video decode group reports it from the browser, so you can tell whether 4K streams run efficiently and stay light on a laptop battery. YouTube and Netflix push AV1 for 4K, so that codec is the one worth watching. It's also a quick privacy check: everything on this page is what any website you visit can silently read about you, with no permission prompt.

What the results mean

CPU threads is the number of logical cores the browser can use. More means smoother multitasking and faster web apps. Safari and every iPhone browser report only under 8 or 8+, so a 10-core Mac reads 8+. Device memory is a privacy-rounded RAM figure (Chromium only). The browser reports the nearest power of two and stops at 32 GB on a computer, so 64 GB shows as 32+ GB and a 12 GB laptop as ~8 GB. The GPU line is the real tell for performance, and GPU acceleration spells it out. On means the browser draws on your graphics card. Off means a software renderer like SwiftShader, so graphics will be slow. Unavailable means the page got no WebGL at all, which is what current Chrome does when hardware acceleration is off or the GPU driver is blocked. The 4K60 video decode group shows how each codec plays. Hardware means the browser decodes it on the GPU efficiently at 4K60, so the picture stays smooth and the CPU stays cool. Software means the CPU does the work. Expect more heat and faster battery drain, and a stutter on weak chips. AV1 is the one to watch, since only newer GPUs decode it and YouTube and Netflix rely on it for 4K. Screen resolution is in CSS pixels. Multiply by the pixel ratio for true physical pixels, at 100% page zoom, since Chrome and Edge count page zoom in the ratio. Refresh rate is how often this browser draws a frame, which matches your display unless something caps it. Safari and every iPhone browser draw pages near 60 fps by default, so a 120Hz screen reads about 60 there. On a Mac, turn off Prefer Page Rendering Updates near 60fps in Safari's Feature Flags to see the full rate. OS names Windows 11 or 10 in Chrome and Edge, which report the exact version. Firefox only says Windows 10 or 11, and Safari says macOS or iOS without a number, since their user agent can't tell the versions apart or is frozen. A dash anywhere just means your browser declined to expose that field, not an error.

Example result of System Info: the verdict GPU not in use, with Microsoft Basic Render Driver listed as the GPU and GPU acceleration Off.

FAQ

Is this accurate, and does it show my real CPU and GPU?: It shows what the browser is willing to report, and every browser hides something. Chrome and Edge give the exact thread count and GPU name and round memory to a coarse value. Firefox names only the GPU maker. Safari and every iPhone browser report CPU threads only as under 8 or 8+, show the GPU as Apple GPU and give no memory figure.
Can it show my exact CPU model and how much RAM I have?: No. Browsers don't let a web page read the CPU model, its clock speed or your exact RAM. You get the thread count (Safari only says under 8 or 8+). Chrome, Edge and Opera add a rounded memory figure, and no other browser does. On an Apple silicon Mac, Chrome and Edge do name the chip, because it's part of the GPU name. For the exact model and RAM on Windows, open Task Manager and click the Performance tab. On a Mac, choose About This Mac from the Apple menu.
Why does device memory show 32+ GB when I have more RAM?: Chrome, Edge and Opera round your RAM to the nearest power of two and stop at 32 GB on a computer (8 GB on Android), so you are harder to track. A 64 GB PC reads 32+ GB, and a 12 GB laptop reads ~8 GB. Firefox and Safari don't report memory at all, so you'll see a dash there.
Is any of this sent to a server?: No. Every value is read in your browser with standard JavaScript and rendered on the page. Nothing is uploaded, logged, or stored. Share is the one exception: the link carries your specs and GPU verdict, so anyone who opens it sees them. It never carries your user agent, languages or timezone.
Why is my GPU shown as a generic name?: The GPU name comes from WebGL's debug renderer extension. Some browsers and privacy settings hide it. Firefox swaps the model for an older card from the same maker, so the page shows only the maker, like NVIDIA (model hidden). Safari reports every Apple chip as Apple GPU. With hardware acceleration off, older browsers fall back to a software renderer like 'Google SwiftShader', while current Chrome gives the page no WebGL at all, so GPU shows a dash and GPU acceleration reads Unavailable.
Does it show whether my GPU decodes AV1 or HEVC?: Yes. The 4K60 video decode group probes H.264, HEVC, VP9, and AV1. Hardware means your GPU has a dedicated decoder for that codec at 4K60, so playback stays smooth and light on battery. Software means the CPU does the work, which runs hotter and slower. A dash means the codec is unsupported.
Which GPUs hardware-decode AV1 and HEVC?: HEVC plays in hardware on most cards from the past several years. AV1 is pickier. As a rule it wants an NVIDIA RTX 30 series card or newer, an AMD Radeon RX 6000 series card or newer, Intel Arc or 11th-gen and newer Intel graphics, or an Apple M3 chip or later. A few budget cards in those lines skip AV1, which is why this tool checks your actual GPU instead of trusting a spec sheet.
A codec shows Software next to it. Should I worry?: Not really. Software decode still plays the video. The CPU just does the work, so the fan spins up and a laptop drains faster, and a 4K60 stream can stutter on an older chip. Updating your GPU driver sometimes adds the missing codec, and support varies by browser, so Chrome or Edge may read Hardware where Firefox shows Software.
Why does screen resolution differ from what I set in Windows?: The screen size is in CSS pixels. Multiply by the pixel ratio to get physical pixels: a 4K display at 150% scaling reports 2560×1440 with a 1.5× ratio. That math holds at 100% page zoom, because Chrome and Edge count page zoom in the ratio. For the panel size in real pixels, open the Screen Resolution Checker.

How we measure

The page reads each value from standard browser APIs when it opens. CPU threads is the number of logical processors the browser says it can use. Device memory is the browser's RAM figure, rounded to a power of two. The figure tops out at 32 GB on a computer and 8 GB on Android. A value at that ceiling shows as 32+ GB or 8+ GB, and anything under it gets a tilde, like ~16 GB.

GPU is the renderer name WebGL reports through its debug renderer extension, minus the ANGLE wrapper that Chrome and Edge put around it. GPU acceleration reads Off when that name is a software renderer: SwiftShader, llvmpipe, softpipe or Microsoft Basic Render Driver. No WebGL at all reads Unavailable. Anything else reads On. If the browser hides the name, the page can't tell a software renderer from a real card, so GPU acceleration shows a dash. On an Apple silicon Mac, Chrome and Edge put the chip in the GPU name, so the page lists it as the CPU too.

Chrome, Edge and Opera send client hints, and the page takes OS and architecture from them. A Windows platform version of 13 or higher reads Windows 11. Without hints, the page reads the user agent string instead.

Refresh rate times the frames this browser draws. The first 500 ms are a warm-up and don't count. Over the next 700 ms the page notes the gap between frames. Any gap more than 1.5 times the median counts as a dropped frame and stays out. The rate is one second divided by the average of the gaps that are left.

The 4K60 video decode group checks four codecs: H.264, HEVC, VP9 and AV1, all 8-bit. For each one the page asks the browser whether it can decode a 3840×2160 file at 60 fps and 15 Mbps, and whether that would be power efficient. Hardware means yes to both. Software means it can play the file, just not efficiently, and a dash means it can't play it at all.

What a browser cannot see

The page sees only what the browser hands over. Every browser keeps the CPU model, its clock speed and your exact RAM to itself.

Safari and every iPhone browser run on WebKit, which reports 8 threads on a machine with 8 or more and 4 below that, so the page shows 8+ or <8. Device memory shows a dash in Firefox and Safari, which don't report it.

Firefox swaps the real GPU name for a stand-in card from the same maker, and every Apple chip becomes an Apple M1. The page keeps just the maker's name. Safari names every Apple chip Apple GPU.

The decode check is the browser's prediction. No video plays. Chrome and Edge say power efficient when the graphics driver reports a hardware decoder for that format and size. Firefox only checks that it has a hardware decoder for the format, and Safari says yes when macOS or iOS has one. A driver update or another browser can change the answer.

WebKit draws pages near 60 fps by default, so in Safari or any iPhone browser a faster screen still reads about 60. Any other cap on how often the browser draws lowers the number the same way.

Firefox's user agent says Windows NT 10.0 on both Windows 10 and 11, and Safari's names the same old macOS version on every Mac. So in those browsers the page shows Windows 10 or 11, or plain macOS, never a version number.

Screen resolution counts CSS pixels, not physical ones. Chrome and Edge fold page zoom into the pixel ratio but leave the screen size alone, so there resolution times pixel ratio gives physical pixels only at 100% zoom.

Sources

Was this tool useful?

Related tests

Screen Resolution Checker

Check your screen resolution in real pixels, plus aspect ratio, pixel ratio, color depth and browser window size. Reads locally, nothing uploaded.

Embed on your site

Internet Speed Test

Free browser internet speed test for gaming: measure ping, jitter, download, upload and latency under load, then see if your line will lag in a match.

Share your result
Embed on your site

Refresh Rate Test

Measure your monitor's real refresh rate in the browser. Pick your rated Hz, see if your 60, 144, or 240Hz panel hits full rate, and count dropped frames.

Share your result
Embed on your site