A full checkup for your device.
See what your screen, browser, hardware, network and graphics actually report — and which modern web features your browser supports. Open a diagnostic below; every reading runs locally and nothing is uploaded.
Pick a diagnostic
Each check lives on its own page and runs live in your browser. Choose one to open it.
Screen & Display
Resolution, pixel density, colour depth and a sampled refresh rate.
Open panelGraphics (GPU)
The renderer and vendor behind WebGL on this machine.
Open panelBrowser & System
How your browser identifies itself, with a copy-ready health summary.
Open panelHardware & Battery
Logical cores, memory, input capabilities and charge state.
Open panelNetwork
Effective connection type, downlink, latency and data-saver mode.
Open panelFeature Support
A pass/fail readout of the web platform APIs your browser ships.
Open panelWhy DeviceScope
Private by default
Every reading is taken with standard browser APIs and rendered on the page. There is no server, no account and no analytics — nothing you see is uploaded anywhere.
Instant & live
No spinners and no waiting. Values appear the moment a page loads and update live as you resize, rotate or reconnect.
Honest about limits
When a browser hides a signal for privacy — a public IP, battery status or network details — we say it is not available instead of guessing or inventing a number.
English & Russian
The whole site — every diagnostic, guide and help note — is fully bilingual. Switch languages anytime from the header.
Know your device, without giving anything away
DeviceScope is a free online device checker that answers the questions people ask every day: what browser am I using, what is my screen resolution and pixel ratio, how many CPU cores does my machine report, what GPU is behind WebGL, what does my network connection look like, and which modern web features my browser actually supports. Each check lives on its own focused page and runs the moment it opens, so you get a clear, copy-ready answer without installing anything.
Everything works client-side in your browser, which makes it fast, private and available the instant a page loads. There is no server, no account and no tracking. Because it runs only on your device, a browser-based tool cannot show things that require a network service — your public IP address, for example, is only visible to a server, so we never pretend to know it. When an engine hides a value for privacy, we label it honestly rather than inventing a number, and each diagnostic is backed by a plain-language guide that explains what the reading means.
Guides & articles
Plain-language explainers on browsers, screens, GPUs, networks and the privacy trade-offs behind them.
What Your Browser Reveals About You (and What It Doesn't)
A web page can read a surprising amount about your setup with no permission at all — and there are hard limits it cannot cross. Here is exactly where the line sits.
Screen Resolution, DPR and Retina Displays Explained
Why the resolution your browser reports may not match the pixels in the panel, what device pixel ratio really means, and why "Retina" is just marketing for a number you can read yourself.
What Is a User Agent String?
Every request your browser sends carries a strange line of text claiming to be several browsers at once. Here is what it means, why it is full of historical fibs, and why it is slowly being retired.
Frequently asked questions
Does DeviceScope send my information anywhere?+
No. Every reading is taken with standard browser APIs and rendered directly on the page. There is no server call, no account and no analytics — the report you see never leaves your device unless you copy it somewhere yourself.
Why is my IP address or exact location not shown?+
Your public IP address is only visible to a network service, and DeviceScope has no server, so we do not show it rather than guess. Precise location needs your explicit permission through the Geolocation API, which we never request silently. We only report what the browser exposes locally.
Some values say “Not available” or “Not exposed by this browser”. Why?+
Browsers deliberately hide some signals for privacy, and support differs between engines. Battery status, network details and device memory are common examples that Safari and Firefox often withhold. When a value is missing we say so honestly instead of inventing a number.
How is the refresh rate estimated?+
We count how many animation frames the browser paints over a short sampling window and convert that to hertz. It is an estimate: background tabs, power-saving modes and variable-refresh displays can shift the number, so treat it as a close approximation rather than a hardware spec.
Why does the GPU name look strange, like “ANGLE (…)”?+
On Windows, Chromium browsers route WebGL through ANGLE, so the renderer string wraps your real GPU inside an ANGLE description. The underlying vendor and model are still there. Some browsers also mask this string entirely for privacy, in which case a generic value is reported.
Can I trust these numbers for benchmarking or support tickets?+
They are exactly what your browser reports, which is ideal for copying into a bug report or support ticket. For hard performance benchmarking, remember that logical cores, device memory and refresh rate are browser-provided hints and can be rounded or throttled for privacy.