Hardware Information device info viewport DPR

Device Information

View viewport, pixel ratio, and device capability signals.

Interactive tool

Run the test

Runs in your browser

Live device signals from this browser session. Resize the window to refresh viewport values.

Collecting device information…

Cameras

Camera details stay local

Labels appear after permission. Settings and capabilities come from the active MediaStreamTrack APIs. The stream never leaves your device.

Permission status

Checked in your browser. DeviceHub does not store permission grants.

  • Special permission Not required

Live results

Metrics update as you run the test. Nothing is uploaded.

Loading

Waiting for interactive tool output…

Device information

Labels and capability details reported by your browser.

No device details yet.

Description

About Device Information

Introduction

Device Information summarizes what this browser exposes about your device: viewport and screen size, device pixel ratio, touch hints, logical CPU count, approximate memory when available, and optional camera device details after you allow video. It is a web capability readout, not an OEM inventory or serial report.

What this tool does

It reads standard window, screen, and navigator signals, refreshes on resize, and can list videoinput devices plus track settings when camera permission allows. Network details stay brief with a pointer to Connection Information. Hardware and OS framing stay here; engine and feature matrices belong on Browser Information.

When to use it

Use it for support tickets, responsive layout bugs, and QA matrices when you need geometry and hardware hints together. Prefer Screen Resolution for layout-only sizes, Display Information for HDR or gamut hints, and Browser Information for engine identity.

How it works

CSS pixels and devicePixelRatio come from layout APIs. hardwareConcurrency is a logical processor hint, often clamped. deviceMemory, when present, is a coarse GiB bucket (usually Chromium). Camera enumeration uses the same media APIs as Webcam Test, scoped here as hardware context. No mic or clipboard prompt is required for the basic hub.

Step-by-step instructions

  1. Open Device Information on the device and browser where the issue appears.
  2. Note viewport, screen size, and DPR at 100% zoom.
  3. Scan concurrency, touch, memory, and any camera rows you need.
  4. Copy only the fields for your ticket; open sibling tools for deeper single-topic notes.

Common problems

Zoom above 100%, DevTools emulation, mobile URL bars, and dual-monitor DPI mixes often look “wrong.” Missing memory or battery rows are normal on Safari and Firefox. Marketing 4K labels may not match CSS pixels under OS scaling.

Privacy explanation

Values are shown locally from APIs any page can read. DeviceHub does not upload a hardware fingerprint for ads. Share only what a ticket needs; camera listing appears only after you grant video access.

Runtime principles

Built for the browser

What happens when you run this test — without downloads or accounts.

  1. 01

    Runs in your browser

    Device Information uses standard web APIs — no install, extension, or desktop app required.

  2. 02

    Reads what the browser allows

    Results come from events and capability signals the web platform exposes for this session.

  3. 03

    Private by default

    Input and diagnostic values stay in your browser session for display — nothing is sold as media.

Compatibility

Supported browsers

Expected support for modern engines. Individual APIs may still vary by device.

  • Chrome

    supported

    Latest stable

  • Firefox

    supported

    Latest stable

  • Safari

    supported

    Latest stable

  • Edge

    supported

    Latest stable

Devices

Supported devices

Hardware and form factors this browser test is designed to exercise.

  • Desktop browsers

    Chrome, Firefox, Safari, and Edge on Windows, macOS, Linux.

  • Laptops

    Reports viewport, DPR, and capability signals for the active session.

  • Phones & tablets

    Mobile browsers with responsive viewport and touch hints.

Privacy

Your data stays with you

Device Information is built privacy-first. Diagnostics run in your browser session whenever web APIs allow.

Read our privacy policy

Troubleshooting

Common problems

Quick fixes before you dig into FAQs.

Viewport size looks wrong
Zoom level, browser chrome, and device pixel ratio change reported CSS pixels. Set zoom to 100%, exit DevTools device emulation, and resize once to refresh live readings.
Memory or battery fields are blank
Those APIs are Chromium-oriented or restricted. Open RAM Information or Battery Information for focused honesty notes, absence is often a platform limit, not a DeviceHub defect.
Numbers disagree with marketing specs
Web readouts are CSS-pixel and capability hints, not EDID warranty labels or CPU model strings. Compare Screen Information and Display Information for geometry versus gamut/HDR signals.

FAQ

Frequently asked questions

Structured answers for users and FAQ rich results.

Browse FAQs
Is this a full hardware serial report?
No. It shows browser-exposed capability signals such as viewport, DPR, concurrency, and optional camera device details after permission.
How is this different from Browser Information?
Device Information focuses on hardware and layout signals. Browser Information focuses on engine identity and feature detection.
Why are memory or battery fields blank?
Those APIs are limited or missing in many browsers. Blank usually means a platform limit, not a broken page.
Can it list my cameras?
Yes, after you allow camera access. Friendly names often appear only after a grant.
Is anything uploaded?
No. Values are read and shown locally for diagnostics.

Newsletter

Updates coming soon

A lightweight email digest for new tools and release notes is planned. No signup form is live yet — check Release Notes for product updates.

Release notes

Need another diagnostic after Device Information?

Explore related DeviceHub tools that pair well with this test.