What is My Device? Get All Info of Your Device

What this page shows

“What is My Device” reads the information your browser is willing to expose and puts it on one screen. There is nothing to upload and nothing to install: open the page and the panels fill in as the browser answers each question. The result is useful when you are filing a bug report, checking why a site behaves differently on one machine, or simply want to see how much a normal web page can learn about the device you are using.

The page is a reader, not a scanner. It does not install anything, does not open your camera or microphone, and does not ask for your GPS position. It reports what the browser already knows and, for the IP address, what the server can see when you connect.

The panels, one by one

IP address and IP location

The address shown at the top is the public IP the site sees for your connection, fetched from the site's own IP endpoint. A second request looks up an approximate location for that address: country, region, city, postal code, timezone, ISP or organisation, and an ASN. This is network-level geolocation, not GPS. It usually lands on your city or your ISP's regional hub, and a VPN moves it to the VPN's exit point.

User agent

The full user-agent string is printed verbatim. It is the line your browser sends with every request, and it is the source for most of the browser and operating-system labels elsewhere on the page.

Network

Status, connection type, effective type, estimated downlink, round-trip latency and the Save Data flag come from the browser's Network Information API. These are estimates supplied by the browser, not a speed test. Browsers that do not implement the API show “Not supported”.

Browser

Name, version, rendering engine, engine version, interface language, cookie support, built-in PDF viewer, Do Not Track and WebDriver status. WebDriver is the flag automation tools such as Selenium and Playwright usually set, so a “Detected” value is a hint that the browser may be controlled by software.

OS and device

Operating-system name and version, device type (desktop, mobile or tablet), CPU core count, architecture and approximate RAM. Device model is filled for iPhone and iPad; other hardware is shown as not available because the browser does not expose a reliable model name.

Browser capabilities

A grid of twenty support checks: WebGL and WebGL 2, WebAssembly, service workers, web workers, IndexedDB, local and session storage, WebSockets, the Fetch API, the Clipboard API, Web Share, notifications, fullscreen, geolocation, Bluetooth, USB, Web Crypto, Wake Lock and WebRTC. Each chip is a yes-or-no result from a feature test in your current browser.

Permissions

Geolocation, notifications, camera, microphone and clipboard read/write are shown as granted, denied or prompt. This is a status read, not a request: the page asks the Permissions API what the current state is and does not trigger a permission popup. “Prompt” means the browser would ask if a site requested it.

Languages, battery and screen

The language panel lists the languages your browser advertises, with the primary one first. The battery panel shows charge level, charging state and the browser's estimates for charge and discharge time, where the Battery Status API is available. The screen panel reports resolution, current viewport, available screen area, colour depth, device pixel ratio and orientation.

Storage and media devices

Storage shows whether local storage, session storage, IndexedDB and the Cache API exist, plus an estimate of how much space this site is using against the browser's quota. Media devices counts cameras, microphones and speakers. Without camera or microphone permission the browser hides device labels and may report fewer devices, which is why that panel can say “Permission needed”.

Extra browser info

Platform, vendor, product, application name and version, standalone display mode and the user-agent brand list. Some of these fields are legacy and return fixed strings in modern browsers; they are shown for completeness rather than as reliable identifiers.

What it is good for

• Bug reports. Paste the browser, OS, screen and user-agent values into a ticket instead of asking a user to describe their setup.
• Compatibility checks. Confirm whether a browser supports WebGL 2, WebAssembly or a particular storage API before relying on it.
• Privacy awareness. See how much a page can infer without any permission prompt: IP, approximate city, browser, OS, screen size and language.
• Support triage. A “WebDriver detected” result or a Save Data flag can explain behaviour that looks mysterious otherwise.
• Device handover. Check the viewport and pixel ratio when testing a responsive layout on a new phone or tablet.

How accurate is it?

The browser and OS labels are derived from the user-agent string with pattern matching. That works for mainstream browsers but can mislabel a niche browser, a webview inside another app, or a browser that deliberately disguises its identity. The IP location is approximate and depends on the lookup provider's database; it can be a nearby city rather than your exact one. Network speed and battery times are estimates, and several panels are simply unavailable in browsers that do not implement the underlying API, most notably Safari and Firefox for some of the battery and network fields.

Privacy: what leaves your device

Two things leave the device for the IP panels: the request to the site's IP endpoint, which necessarily reveals your address, and a second request that sends that address to the location lookup service. Everything else is read inside the page with JavaScript. The camera, microphone and location are not accessed; the permissions panel only reads the current permission state. The page does not ask for GPS coordinates and does not show a map. As with any website, the server also sees the usual request metadata, including the user agent that is printed on the page.

Common mistakes

• Reading “Prompt” as access granted. It means the browser would ask; nothing has been shared.
• Expecting an exact address. IP location is approximate and often city-level.
• Treating the device model as universal. Only iPhone and iPad are labelled; other hardware is intentionally reported as unavailable.
• Assuming every panel works everywhere. Battery and network details depend on browser support and can be missing by design.
• Using the user agent as a security signal. It is self-reported text and can be changed by the browser or an extension.

Limitations

The page reports what the current browser exposes. It cannot see installed applications, files, other browser tabs, precise GPS coordinates or hardware identifiers that the platform withholds. Results vary by browser, by privacy settings and by whether an extension is spoofing the user agent. Nothing is saved between visits, and the values refresh when you reload.

Frequently Asked Questions