Device information
Get information about your current device (screen size, pixel-ratio, user agent, ...)
Enable JavaScript to use the interactive tool. The guide below explains how it works.
Device Information: Technical Specification & Debugging Guide
1. What the Tool Does
The Device Information tool is a comprehensive diagnostic utility that surfaces real-time metadata about a user's hardware, operating system, and browser environment. By querying various browser APIs (like Navigator, Screen, and Window), it provides a unified dashboard of the technical constraints and capabilities of the current device.
The tool categorizes information into two primary sections:
- Screen: Details about the physical display, its orientation, pixel density, and the available viewport area.
- Device/Browser: Information about the software environment, including vendor identification, language preferences, and the underlying platform architecture.
All data is retrieved client-side, providing an instantaneous snapshot of the environment without requiring any network requests or server-side analysis.
2. Why Someone Uses It
In modern web development, "it works on my machine" is a common but dangerous phrase. This tool is designed to bridge the gap between different environments.
Responsive Design Debugging
Web designers use this tool to see the exact "Window size" (viewport) as they resize their browser. This helps them identify the precise pixel width where a layout breaks, making it easier to write accurate CSS media queries.
Cross-Browser Testing
When a user reports a bug, developers need to know their "User Agent" and "Platform." This tool allows the user to simply screenshot or copy their device info to help the developer reproduce the issue in an identical environment.
High-DPI Assets Optimization
By checking the "Pixel ratio," developers can determine if a device has a "Retina" or high-DPI display. This informs decisions about whether to serve @2x or @3x image assets to ensure visual clarity without wasting bandwidth.
Privacy Awareness
For security-conscious users, this tool reveals exactly how much information a website can "see" about them. It serves as an educational resource regarding browser fingerprinting and the breadth of data exposed by standard web APIs.
3. Step-by-Step Instructions
Step 1: Open the Tool
Simply navigate to the Device Information page. The data is populated automatically the moment the page loads.
Step 2: Observe Real-Time Updates
Try resizing your browser window. You will notice the "Window size" values under the Screen section update dynamically as you drag the window edges.
Step 3: Check Device Orientation
If you are on a mobile device or a tablet, rotate the device from portrait to landscape. The "Orientation" and "Orientation angle" fields will update to reflect the new state.
Step 4: Extract Information
Review the Device section for your "User Agent." This long string is the most valuable piece of information for troubleshooting complex browser-specific bugs.
4. Examples
Typical Desktop Result
- Screen Size:
1920 x 1080 - Pixel Ratio:
1 dppx - Platform:
Win32 - Browser Vendor:
Google Inc.
Typical Mobile (Retina) Result
- Screen Size:
390 x 844 - Pixel Ratio:
3 dppx - Platform:
iPhone - Orientation:
portrait-primary
5. Technical Deep Dive: Key Concepts
Screen Size vs. Window Size
- Screen size refers to the physical resolution of the monitor or mobile display.
- Window size (or Viewport) refers to the actual area where the website is rendered. This is always smaller than the screen size because it excludes browser toolbars, address bars, and OS taskbars. For developers, Window size is the more important metric.
Device Pixel Ratio (DPR)
The "Pixel ratio" (e.g., 2.0 or 3.0) explains how many physical pixels are used to represent a single "CSS pixel." A ratio of 2.0 means a 100x100 square in your code actually uses 200x200 physical pixels on the screen. High ratios are the reason why websites look sharp on modern smartphones but can look "blurry" on older monitors if images aren't optimized.
The User Agent String
The "User Agent" is a legacy string that browsers send to identify themselves. While it looks messy (e.g., Mozilla/5.0 (Windows NT 10.0; Win64; x64)...), it contains crucial clues about the browser engine (WebKit, Blink, or Gecko) and the operating system version.
6. Common Mistakes
- Confusing Browser Vendor with Browser Name: The "Browser vendor" field often shows "Google Inc." even for browsers like Brave or Microsoft Edge, because they all use the underlying Chromium engine.
- Ignoring Zoom Level: If you have zoomed in your browser (e.g., to 125%), the "Window size" and "Pixel ratio" will change. Always ensure your zoom is at 100% when using this tool for design debugging.
- Privacy Over-Reliance: Assuming that "unknown" fields mean you are anonymous. Even if some fields are empty, other metadata can still be used for "fingerprinting."
7. Use Cases
Front-End Breakpoint Validation
Use the "Window size" to confirm that your max-width: 768px media query is triggering exactly where you expect it to.
Bug Reporting
When submitting a ticket for a web app, include the "Platform" and "User Agent" to help the engineering team rule out OS-specific bugs (like those often found in Safari on macOS).
Internationalization (i18n) Testing
Check the "Languages" field to see which language codes your browser is broadcasting. This is how websites decide whether to show you the English or Spanish version of their content.
Color Depth Verification
Designers working on high-fidelity graphics can check "Color depth" to ensure the user's display can actually render the millions of colors in their design without "banding."
8. Related Tools
- Camera Recorder: Uses the device information to identify compatible hardware.
- Benchmark Builder: Useful for comparing performance results across the different platforms identified here.
- JSON Formatter: For parsing the raw User Agent string into a more readable format.
Technical Note: This tool utilizes the window.devicePixelRatio and navigator.userAgent properties. Note that some modern browsers are beginning to "freeze" the User Agent string to protect user privacy, so some version numbers might appear outdated even on the latest browser releases.