Loading…
Show browser, OS, screen, and network details. Use for live device data; for parsing UA strings use user-agent-parser. Input: none, auto-detected. Returns device table. 100% client-side.
Device Information is loading — interactive editor will appear here. Use examples below to try instantly once loaded.
Press ? for keyboard shortcuts
Displays detailed information about your device, browser, screen, hardware, and network connection by reading data from the navigator API and window object. Shows user agent, screen resolution, color depth, language, platform, cookies status, connection type, available memory, CPU cores, and touch support in a clean card layout.
Developers and support technicians frequently need to know a user's browser and device details for debugging, compatibility testing, and troubleshooting. This tool provides all that information in one place without requiring developer tools.
This tool is part of the DevStackIO platform — a collection of free online developer tools from DevStackIO. Browse more free developer resources on DevStackIO.
Web developers debugging cross-browser issues, QA testers verifying device configurations, IT support staff diagnosing user problems, and curious users who want to learn more about their device capabilities.
Open this tool in the browser you want to inspect — the information is read from the current browser session
Review the Browser section for user agent, language, and cookie settings
Check the Display section for screen resolution, window size, and pixel ratio
Review the Hardware section for CPU cores, device memory, and touch capability
Check the Network & System section for connection details and timezone
Click "Copy All" to copy all device information to your clipboard for sharing
Desktop Chrome on Windows: Screen 1920×1080, 8 CPU cores, 8 GB memory, No touch, Ethernet connectionMobile Safari on iPhone: Screen 390×844, 4 CPU cores, 6 GB memory, Touch supported, 4G connectionWhy is some information showing "Not available"?
Some APIs (like Network Information or Device Memory) are not supported by all browsers.
Is my data sent anywhere?
No, all information is read locally from your browser. Nothing is transmitted.
Why does my user agent look different from what I expect?
Some browsers modify the user agent for privacy, and extensions can alter it too.
Can I test a different device?
Open this page in a different browser or on a different device to see its information.
Authoritative specifications, standards, and in-depth reading for Device Information.
Parse raw HTTP headers into readable name-value pairs. Use when debugging responses; for URL parts use url-parser. Input: header text ≤10MB. Returns table of headers. 100% client-side.
Split any URL into protocol, host, path, and query params. Use when inspecting URLs; for encoding query strings use url-encoder. Input: URL text. Returns component table. 100% client-side.
Parse user-agent strings into browser, OS, and device. Use when debugging traffic; for live device data use device-information. Input: UA string. Returns parsed fields. 100% client-side.
Calculate network, broadcast, and host range from CIDR. Use for subnet math; for geo lookup use ip-lookup. Input: IP/CIDR. Returns network details. 100% client-side.
Look up DNS records for any domain. Use when checking DNS; for IP geo use ip-lookup. Input: domain name. Returns A, MX, TXT records. 100% client-side.
Look up geolocation and ISP for any IP address. Use for geo data; for subnet math use ip-calculator. Input: IPv4/IPv6. Returns location and ASN. 100% client-side.
Generate Basic Auth headers from username and password. Use when testing APIs; for JWTs use jwt-generator. Input: credentials text. Returns Authorization header. 100% client-side.
Calculate IPv4 subnets, masks, and host counts. Use for IPv4 planning; for IPv6 use ipv6-calculator. Input: CIDR or mask. Returns subnet table. 100% client-side.