Device & Browser Info

Free browser device info checker: see your browser version, user agent, OS, screen resolution, viewport, GPU, network, storage, and privacy signals locally.

Processed locally in your browser

Local Processing

UtilityNova does not receive or store these details unless you copy or download them yourself.

Important Disclaimer

These calculators/tools are provided for informational and educational purposes only. Results are estimates and approximations that may contain errors, inaccuracies, or omissions. Do not rely on these calculations for any critical, financial, legal, engineering, medical, health, or other professional decisions.

All results are provided "as is" and "as available" without any warranties, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, accuracy, completeness, or non-infringement
Calculations may contain errors, bugs, or inaccuracies and are subject to change without notice
Always verify all calculations independently using multiple sources and methods
Consult with qualified, licensed professionals (accountants, engineers, lawyers, doctors, physicians, registered dietitians, nutritionists, fitness professionals, etc.) for any decisions that may have legal, financial, safety, or health implications. Health and fitness calculators are not a substitute for professional medical advice, diagnosis, or treatment.
The accuracy of results depends entirely on input data, assumptions, and algorithms, which may be incorrect or outdated
We disclaim all liability for any damages, losses, costs, or expenses of any kind arising from or related to the use of these calculators, including but not limited to direct, indirect, incidental, consequential, special, or punitive damages
You assume full responsibility and all risk for any decisions, actions, or consequences resulting from the use of these calculators

By using these calculators/tools, you acknowledge that you have read, understood, and agree to this disclaimer. If you do not agree, do not use these calculators/tools. For any professional, commercial, or critical applications, you must consult with certified experts and refer to applicable laws, regulations, standards, and industry best practices.

Use this free Device & Browser Info Checker to answer questions like "what browser am I using?", "what is my user agent?", "what is my screen resolution?", and "what device information can websites see?" The report shows your browser name and version, operating system, user-agent string, screen size, viewport size, device pixel ratio, GPU/WebGL details, network hints, storage quota, permissions, media support, and browser feature support. Everything is detected locally in your browser, so UtilityNova does not receive your system report unless you choose to copy or download it yourself.

How to Use Device & Browser Info

Run an automatic browser and device info check

Open the page and the browser info checker scans your current environment automatically. There is no sign-up, extension, download, or permission prompt. Results appear in grouped sections for Browser & Engine, Operating System, Hardware & Device, Display & Screen, Graphics & GPU, Network, Storage, Permissions, Supported Features, and Readiness Checks.

Copy browser details for support or QA

Use "Copy report" (or the mobile Copy button) to create a plain-text system information summary with your browser version, operating system, screen resolution, viewport size, user agent, device type, GPU status, and key web capabilities. Paste it into a help desk ticket, bug report, Jira issue, GitHub issue, or support chat so developers can reproduce your environment faster.

Download a JSON browser system report

Click "Download JSON" to save a structured device and browser report on your computer. The JSON export is useful for QA logs, browser compatibility testing, regression reports, remote troubleshooting, and comparing Chrome, Edge, Firefox, Safari, Android, iPhone, tablet, and desktop environments.

Check your user agent, browser version, and Client Hints

The Browser & Engine section identifies your browser name, browser version, rendering engine, cookies status, PDF viewer support, Do Not Track value, and full user-agent string. When User-Agent Client Hints are available in Chromium browsers, the checker uses structured hints for more precise browser and OS detection. Otherwise it falls back to the legacy user-agent string and labels estimated values clearly.

Check screen resolution, viewport, and device pixel ratio

The Display & Screen section separates screen resolution from browser viewport size. Screen resolution is your monitor or phone display pixel grid; viewport is the live browser content area that changes when you resize the window, rotate a device, zoom, or open dev tools. Device pixel ratio helps explain Retina, HiDPI, and mobile rendering differences.

Inspect GPU, WebGL, WebGPU, and feature support

Open Graphics & GPU to check WebGL support, WebGL2 support, GPU vendor and renderer when exposed, max texture size, and WebGPU availability. The Supported Features checklist covers common compatibility questions around WebRTC, IndexedDB, Service Workers, Clipboard, WebAssembly, localStorage, media APIs, and other browser capabilities.

Review network, storage, permissions, and privacy-limited data

Network shows online status, effective connection type, downlink, RTT, save-data mode, and link type when your browser exposes it. Storage shows this site's browser storage quota and usage, not your total disk size. Fields shown as "—", "Not exposed by browser", or "Blocked or unavailable" usually mean the browser withheld the value for privacy or compatibility reasons.

Scan again after resizing, rotating, or switching networks

Click "Scan again" after resizing the browser window, changing zoom, rotating a phone or tablet, connecting a different monitor, enabling a VPN, or switching Wi-Fi networks. The tool also refreshes automatically on resize and orientation changes so viewport and display information stays current.

Calculator Features

🔒

Private local browser diagnostics

Check browser and device information client-side. No account, no extension, and no server upload of your system details.

🌐

Browser version and user-agent checker

Find your browser name, version, rendering engine, cookies status, PDF support, Do Not Track value, and full user-agent string.

💻

Device, operating system, and hardware info

See OS, platform, device type, CPU cores, architecture, bitness, approximate memory, touch points, and mobile/desktop signals.

🖥️

Screen resolution, viewport, and DPR checker

Compare monitor resolution, browser viewport size, device pixel ratio, color depth, color gamut, HDR, orientation, and accessibility preferences.

🎮

GPU, WebGL, and WebGPU checker

Verify WebGL, WebGL2, WebGPU, GPU vendor/renderer when exposed, and max texture size for games, maps, and 3D apps.

📡

Network and connection information

Check online status, effective connection class, downlink, RTT, save-data mode, link type, and a local connection sample.

💾

Storage quota, permissions, and media codecs

Review browser storage quota and usage, cache status, IndexedDB, service workers, permission states, media devices, and codec support.

✅

Browser compatibility and readiness checks

Get pass/partial/fail readiness for video calls, PWAs, WebGL games, WebGPU apps, and a checklist of modern web APIs.

📋

Copy report and download JSON

Copy a readable browser system report for support tickets or download structured JSON for QA, debugging, and compatibility logs.

📱

Works on desktop, mobile, and tablet browsers

Use the same browser diagnostics page on Windows, macOS, Linux, Android, iPhone, iPad, Chromebooks, and tablets.

Complete Function List

Automatic browser info check on page load
Answers "what browser am I using?" instantly
Browser name, version, engine, and detection source
Full user-agent string checker with expand/collapse panel
User-Agent Client Hints support when available
Operating system name, platform, and OS version
Device type detection for desktop, mobile, and tablet
CPU cores, architecture, bitness, and approximate device memory
Touch support and max touch points
Screen resolution, available screen area, and monitor metrics
Browser viewport size and device pixel ratio
Color depth, color gamut, HDR, and orientation
Tab visibility, window size, and display mode (PWA)
Secure context, cross-origin isolation, and origin
Primary pointer, hover, contrast, and motion preferences
Timezone, languages, calendar, and local time
Online status, effective connection, downlink, and RTT
Link type (Wi-Fi/Ethernet when exposed by browser)
Local speed sample via favicon fetch
Storage quota, usage, caches, and IndexedDB count
Service worker registration status
WebGL, WebGL2, GPU vendor, renderer, and max texture size
WebGPU supported detection
WebP, AVIF, H.264, VP9, and AV1 codec probes
MediaDevices API and device counts
Page load timing, TTFB, and resource count
JS heap stats (Chrome desktop)
Permission states (camera, mic, geolocation, etc.)
20+ web API feature checklist
Readiness checks for video calls, PWAs, WebGL, and WebGPU
Copy plain-text report to clipboard
Download JSON device and browser report
Auto-refresh on resize, orientation, and network change
Mobile-first sticky action bar
Local processing with no automatic server upload

Common Calculations & Examples

Example 1: Find browser details for a support ticket

Problem: A website bug only happens on your machine and support asks, "what browser and operating system are you using?"

Steps:

Open this device and browser info checker on the affected machine.
Review Browser & Engine, Operating System, Display & Screen, and Supported Features.
Click "Copy report" and paste the result into your support ticket, bug tracker, or chat.

Result: Support receives your browser version, OS, screen resolution, viewport, user agent, and capability flags in one paste.

Explanation: Developers need exact environment details to reproduce layout bugs, JavaScript errors, video call failures, API issues, and compatibility problems. A structured browser system report saves multiple round-trip questions.

Example 2: Check screen resolution and viewport for responsive design

Problem: Your layout breaks at a certain breakpoint, but you are not sure what width the browser actually sees.

Steps:

Open the tool and note screen resolution, viewport size, and device pixel ratio.
Resize the browser window slowly and click Scan again (or wait for auto-refresh).
Compare viewport width against your CSS breakpoints.
Check screen resolution separately—it does not change when you resize the window.

Result: You know the exact viewport dimensions and DPR your CSS media queries respond to.

Explanation: Screen resolution is fixed to your monitor; viewport is the live browser content area. Confusing the two is a common responsive design mistake.

Example 3: Audit browser fingerprint and privacy signals

Problem: You want to know what device information websites can see without asking for permission.

Steps:

Run the scan and review Browser, Device, Display, Locale, Graphics, Network, and Features sections.
Note user agent, browser version, screen size, timezone, languages, CPU cores, GPU renderer, and API availability.
Compare results in a normal window vs private/incognito mode if curious.

Result: A clear picture of browser fingerprint signals exposed to any website you visit.

Explanation: Websites may combine user agent, screen metrics, timezone, language, WebGL renderer, hardware hints, and API support to create a fingerprint. This tool shows the underlying signals without calculating or storing a fingerprint hash.

Example 4: Troubleshoot WebGL, WebGPU, and GPU support

Problem: A WebGL game or 3D app fails and you need to verify GPU support in the browser.

Steps:

Open the Graphics & GPU section after the scan completes.
Check WebGL supported, WebGL2 supported, and WebGPU supported.
Read GPU vendor and renderer—if blocked, your browser is limiting fingerprinting data.
Review Readiness Checks for "WebGL games" and "WebGPU apps" status.

Result: You know whether WebGL is available and whether the browser exposes GPU details.

Explanation: Many browsers block unmasked GPU strings. WebGL support can still be Yes while vendor/renderer show "Blocked or unavailable".

Example 5: Compare mobile, tablet, and desktop browser environments

Problem: Your app works on desktop but fails on a phone or tablet.

Steps:

Run the tool on desktop and on the mobile device (same URL).
Compare device type, browser version, viewport, pixel ratio, touch points, codecs, and Supported Features.
Check media codec and permission sections for mobile-specific differences.
Copy both reports side by side for your team.

Result: Side-by-side browser system information highlighting mobile vs desktop gaps.

Explanation: Mobile browsers often expose different APIs, viewport sizes, media codecs, memory buckets, touch support, permission behavior, and WebGL capabilities than desktop Chrome, Edge, Firefox, or Safari.

Example 6: Create a repeatable QA browser compatibility log

Problem: A QA team needs consistent browser environment reports across different devices and browsers.

Steps:

Run the checker on each test device and browser.
Click "Download JSON" after each scan.
Attach each JSON file to the regression test run or compatibility matrix.
Compare browser, OS, viewport, GPU, storage, permissions, and feature support between devices.

Result: Each QA result includes a consistent device and browser information snapshot.

Explanation: Structured JSON reports make it easier to compare browser environments over time, especially when debugging issues that only appear on one browser version, operating system, or device type.

Effective connection "4g" does not mean cellular

The Effective connection field from navigator.connection.effectiveType is a speed class based on RTT and downlink, not your physical network type. Fast Wi-Fi and Ethernet often show "4g" because the browser estimates a high-quality connection. Use Link type for Wi-Fi, Ethernet, or cellular only when the browser exposes it.

Link type may be hidden on desktop

Wi-Fi vs Ethernet detection through navigator.connection.type has limited browser support. Windows and macOS browsers often return "none" or withhold the value even when you are online on Wi-Fi. That is a browser/platform limitation, not a device info checker failure.

GPU strings may be blocked for privacy

WebGL debug info, including GPU vendor and renderer, is restricted in many browsers to reduce fingerprinting. WebGL supported can be Yes while vendor or renderer show "Blocked or unavailable".

Storage and memory are not full hardware specs

Storage quota is the amount this website may use in your browser through IndexedDB, Cache Storage, and related APIs. It is not total disk space. Device memory is a coarse browser bucket such as 4 GB or 8 GB when exposed, not exact installed RAM.

Viewport changes; screen resolution does not

Resize the window, zoom the page, open dev tools, rotate a phone, or split the screen and viewport size updates. Screen resolution stays tied to the display. Scan again after layout changes to capture current responsive design values.

Unavailable fields are normal

Values shown as "—", "Not exposed by browser", or "Blocked or unavailable" mean your browser did not provide that API result. Privacy-focused browsers, strict tracking protection, private windows, and non-Chromium browsers may hide more fields than mainstream Chrome or Edge.

Pair with display testing

For color accuracy, dead pixels, and HDR checks, use our Universal Color Palette Display Tester alongside this browser system information report.

A browser info checker cannot see everything

Normal websites cannot read serial numbers, installed apps, files, other tabs, exact CPU model, exact RAM modules, or full disk inventory. This page reports only what standard browser APIs expose to JavaScript.

What browser am I using right now?

The Browser & Engine section shows your current browser name, browser version, rendering engine, and detection source automatically. It can identify common browsers such as Chrome, Edge, Firefox, Safari, Samsung Internet, and other Chromium-based browsers when the browser exposes enough information.

How do I check my user agent string?

Run the scan and open the full user-agent panel. The tool displays the raw navigator.userAgent string exactly as your browser exposes it, plus parsed browser, operating system, engine, and device details when available.

What operating system am I using?

The Operating System section lists the detected OS, platform, and OS version when your browser provides those values. Some browsers reduce or generalize OS details for privacy, so the result may be less specific in private or privacy-focused modes.

What device type does my browser report?

Hardware & Device shows whether your browser appears to be desktop, mobile, or tablet, along with CPU cores, approximate memory, touch support, architecture, and bitness when exposed. Serial numbers, exact device models, and installed apps are not available through standard web APIs.

How do I check my screen resolution online?

The Display & Screen section lists screen resolution, available screen area, viewport size, device pixel ratio, color depth, orientation, and related display signals. Screen resolution is the display size; viewport is the browser content area.

What is the difference between screen resolution and viewport size?

Screen resolution is the pixel size of the monitor or device display. Viewport size is the visible browser content area used by CSS media queries. Viewport changes when you resize the browser, zoom, rotate a phone, open split screen, or show developer tools.

Is my browser and device information sent to UtilityNova?

No. The report is built in your browser using local JavaScript APIs. UtilityNova does not receive your device and browser information unless you manually copy it, download it, or share it somewhere yourself.

What information can websites see about my device?

Websites can read many of the same signals this tool displays: user agent, browser version, screen and viewport size, timezone, language, CPU core count, connection hints, storage quota, WebGL GPU info when not blocked, and feature API support. They cannot see your files, other tabs, exact RAM, full disk inventory, serial number, or installed apps through these APIs.

Does this browser info checker show my public IP address?

No. This tool does not call external IP lookup services. It only reports what JavaScript browser APIs expose locally. For IP-related checks, use a dedicated network tool.

Can this show my exact RAM, CPU model, or full disk space?

No. Browsers intentionally limit exact hardware details. Device memory is rounded into coarse buckets when available, CPU cores are only a count, and storage quota is browser storage available to this site rather than total hard drive capacity.

Can a website see my open tabs or memory per tab?

No. Browsers block websites from seeing other tabs, other apps, or per-tab memory details. JS heap stats, when exposed, apply only to this page and are mostly available in Chromium desktop browsers.

Why is GPU information blocked or unavailable?

Graphics & GPU shows WebGL, WebGL2, WebGPU, and texture limits. Vendor and renderer strings are often withheld to reduce fingerprinting, so WebGL can still work even when GPU vendor or renderer reads "Blocked or unavailable".

Why does effective connection show 4g when I am on Wi-Fi?

effectiveType is a speed estimate such as slow-2g, 2g, 3g, or 4g. It is not the same as Wi-Fi, Ethernet, or cellular. Fast Wi-Fi and wired connections often show 4g because the browser estimates the connection quality as high.

Why does browser detection say "User-Agent (estimated)"?

When User-Agent Client Hints are unavailable, the tool parses the legacy user-agent string. Privacy browsers may send reduced, frozen, or generic strings, so version and OS detection can be less precise than Client Hints on secure Chromium browsers.

Does this device browser info checker work on mobile phones and tablets?

Yes. Mobile browsers expose display, locale, network, touch, media, and many feature APIs. Some desktop-only metrics, such as detailed JS heap stats, may be absent. The UI is mobile-first with a sticky action bar for Scan, Copy, and JSON.

Can I use this browser report for debugging website compatibility?

Yes. The copied report and JSON export are designed for support teams, developers, and QA testers who need browser version, OS, viewport, screen resolution, GPU/WebGL support, storage, permissions, codecs, and feature flags in one consistent report.

Is this the same as a user agent parser?

It includes user-agent parsing for your current browser, but it goes further than a basic user agent checker. It also reads browser APIs for screen metrics, viewport, hardware hints, network information, storage quota, permissions, GPU/WebGL support, media codecs, and feature availability.

User-Agent vs User-Agent Client Hints

The user-agent string is a text header your browser sends with HTTP requests. It usually contains browser, version, rendering engine, operating system, and device clues, but it can be reduced, frozen, or spoofed. User-Agent Client Hints (UA-CH) provide structured browser and platform data through navigator.userAgentData in supported secure Chromium browsers. This checker prefers Client Hints when available and falls back to parsing the legacy user-agent string when needed.

Screen resolution vs viewport vs device pixel ratio

Screen resolution is your monitor or phone display pixel grid. Viewport size is the live browser content area measured by window.innerWidth and window.innerHeight, which is what CSS layout and media queries respond to. Device pixel ratio is the relationship between CSS pixels and physical pixels, often 2 or higher on Retina, HiDPI, and many mobile displays. For responsive design debugging, viewport width matters more than raw screen resolution.

What is browser fingerprinting?

Browser fingerprinting combines passive signals such as user agent, browser version, screen size, viewport, timezone, language list, CPU core count, device memory bucket, WebGL renderer, media support, and API availability to create a recognizable profile without cookies. This checker shows many of those signals so you can understand what websites may see. It does not compute a fingerprint score or store a fingerprint hash.

WebGL and WebGPU GPU detection in the browser

WebGL uses a canvas context to probe graphics capabilities such as WebGL support, WebGL2 support, texture limits, and sometimes GPU vendor or renderer. The WEBGL_debug_renderer_info extension may expose unmasked GPU strings, but many browsers block it for privacy. WebGPU through navigator.gpu indicates next-generation graphics API support. Readiness for games, maps, CAD viewers, and 3D apps depends on WebGL or WebGPU plus memory, CPU, and browser feature support.

Network Information API limitations

navigator.connection can provide effectiveType, downlink, RTT, saveData, and sometimes link type such as wifi, cellular, or ethernet. effectiveType is a heuristic speed class, not your ISP plan or physical network medium. Link type has limited desktop support, so Windows and macOS browsers may hide it even on Wi-Fi. navigator.onLine only indicates browser network status, not guaranteed internet reachability.

Why browsers hide exact hardware details

Exact RAM, disk size, CPU model, GPU model, device model, and network type can increase fingerprinting risk. Modern browsers reduce that risk by bucketing memory, masking WebGL strings, limiting Client Hints, and hiding certain APIs in private or strict modes. A browser diagnostics tool can only display what standard APIs return; missing values usually reflect browser policy rather than missing hardware.

Why device memory is rounded

The deviceMemory API returns coarse values such as 2, 4, or 8 GB to reduce fingerprinting. These values are approximate hints for adaptive web apps deciding how much work to do in the browser. They are not precise readings from RAM modules and should not be treated as a hardware inventory.

How browser compatibility checks help developers

A compatibility bug often depends on a combination of browser version, OS, viewport, device pixel ratio, GPU support, media codecs, permission behavior, storage availability, and feature APIs. Copying a complete browser system report gives developers and QA teams the context they need to reproduce issues without asking users to manually describe their setup.

Why a local system information report is safer

Many diagnostic tools ask users to upload logs or install software. This page uses standard browser APIs and builds the report locally, which makes it suitable for quick privacy-conscious troubleshooting. You stay in control: view the result, copy a plain-text summary, or download JSON only when you decide to share it.

Device & Browser Info

Processed locally in your browser

How to Use Device & Browser Info

Run an automatic browser and device info check

Copy browser details for support or QA

Download a JSON browser system report

Check your user agent, browser version, and Client Hints

Check screen resolution, viewport, and device pixel ratio

Inspect GPU, WebGL, WebGPU, and feature support

Review network, storage, permissions, and privacy-limited data

Scan again after resizing, rotating, or switching networks

Calculator Features

Private local browser diagnostics

Browser version and user-agent checker

Device, operating system, and hardware info

Screen resolution, viewport, and DPR checker

GPU, WebGL, and WebGPU checker

Network and connection information

Storage quota, permissions, and media codecs

Browser compatibility and readiness checks

Copy report and download JSON

Works on desktop, mobile, and tablet browsers

Complete Function List

Common Calculations & Examples

Example 1: Find browser details for a support ticket

Example 2: Check screen resolution and viewport for responsive design

Example 3: Audit browser fingerprint and privacy signals

Example 4: Troubleshoot WebGL, WebGPU, and GPU support

Example 5: Compare mobile, tablet, and desktop browser environments

Example 6: Create a repeatable QA browser compatibility log

Tips for Using Device & Browser Info

Frequently Asked Questions

Understanding Device & Browser Info

Related Calculators & Tools

Universal Color Palette Display Tester

IPv4 Subnet Calculator

Time Zone Meeting Planner

Text Encoder / Decoder

Ambient Sound Player

Background Remover