Browser Info

Inspect browser and device environment data instantly—runs locally, no upload.

By Muhammad Abdullah Rauf · Founder, EverydayTools.proUpdated 2026-05-20

What is a browser info tool?

A browser info tool reads standard JavaScript APIs (navigator, screen, window) and shows your user agent, viewport, screen size, language, timezone, and hardware hints—locally in the tab, with no server upload.

Modern web apps need to know the client environment: how wide the viewport is, whether cookies are enabled, how many CPU cores are available, and what user-agent string the browser sends. A browser info tool collects these fields in one place by calling APIs your browser already exposes—navigator.userAgent, window.screen, window.innerWidth, navigator.language, Intl for timezone, and optional hints like deviceMemory and hardwareConcurrency.

Unlike a user-agent parser that interprets the UA string into browser/OS families, a browser info snapshot is raw environment data: ideal for bug reports, responsive-design QA, and feature detection. EverydayTools runs entirely in your browser: values are read when the page loads and are never transmitted to our servers.

Quick answers

Concise answers for common searches — definitions, steps, and comparisons.

What is the difference between screen size and viewport size?

Screen width/height come from window.screen—the physical display. Viewport (inner) width/height come from window.innerWidth/innerHeight—the area your CSS layout uses inside the browser window. They differ when toolbars, devtools, or split-screen reduce the window.

What is device pixel ratio (DPR)?

window.devicePixelRatio is the ratio between physical pixels and CSS pixels. A DPR of 2 or 3 on mobile means one CSS pixel maps to multiple device pixels—important for sharp images and media queries.

How do I export browser info for a ticket?

Click Copy All Info to place a JSON object on your clipboard, then paste into your bug tracker. Include user agent and viewport fields so engineers can reproduce layout issues.

How to use Browser Info

  1. Open the tool

    The page loads and reads browser APIs automatically—user agent, screen dimensions, viewport size, language, timezone, and feature flags appear in grouped sections.

  2. Check viewport vs screen

    Compare screen width/height (monitor) with window inner width/height (layout viewport). Note device pixel ratio (DPR) for high-density mobile layouts.

  3. Copy fields for a bug report

    Use the copy button on User Agent or Full URL, or Copy All Info to grab a JSON blob you can paste into Jira, GitHub, or Slack.

  4. Refresh after resize

    Window dimensions are captured on load. Resize the browser, then refresh the page to see updated innerWidth and innerHeight—screen dimensions stay fixed unless display settings change.

Browser Info examples

Mobile layout bug on a high-DPR phone

Input

innerWidth 390, devicePixelRatio 3, maxTouchPoints 5

Output

JSON snapshot attached to a GitHub issue

QA can reproduce CSS issues that only appear on narrow, high-DPR viewports without guessing device settings from the UA string alone.

Verify cookies and online status

Input

cookieEnabled false, onLine true

Output

Feature flags listed under Browser Features

Helps debug auth flows when third-party cookies are blocked or when offline detection affects your SPA.

Who uses Browser Info?

Common real-world scenarios where this tool saves time.

Responsive design QA

Confirm screen vs viewport sizes and DPR while testing breakpoints—especially when emulators disagree with a real device.

Support and bug reports

Attach a JSON environment snapshot so engineers see exact user agent, timezone, and window metrics without a screen-share.

Feature detection sanity checks

Verify hardwareConcurrency, deviceMemory (when exposed), touch points, and cookie/online flags before enabling performance or touch UI paths.

Cross-browser compatibility

Compare environment fields across Chrome, Firefox, Safari, and Edge when a layout or API behaves differently per engine.

Workflow guides

Step-by-step chains that connect related tools for common tasks.

Bug report with environment context

  1. Open Browser Info and click Copy All Info for a JSON snapshot.
  2. If the issue involves UA interpretation, paste the user agent into User-Agent Parser for browser/OS/device labels.
  3. For breakpoint-specific layout checks, compare with Screen Resolution Checker for DPR and breakpoint context.

Reference tables

Browser info vs user-agent parser

Choose the right developer tool for environment debugging.

ToolBest for
Browser InfoRaw JSON snapshot: screen, viewport, DPR, language, timezone, hardware hints
User-Agent ParserStructured browser, OS, and device labels from a UA string
Screen Resolution CheckerViewport, DPR, and CSS breakpoint focus for responsive QA

Common mistakes to avoid

Expecting window size to update live while resizing

Values are read on page load—refresh after resize to refresh innerWidth and innerHeight.

Confusing user agent with IP or geolocation

This tool shows client-side JavaScript environment data, not your network IP. Use a dedicated IP lookup tool for public address info.

Using browser info instead of a UA parser for OS names

For structured browser/OS/device labels from the UA string, use the User-Agent Parser; use Browser Info for raw metrics and screen/viewport numbers.

Troubleshooting

Window dimensions did not change after I resized

Likely cause: Metrics are captured once when the page loads.

Fix: Refresh the page after changing the window size to see updated innerWidth and innerHeight.

Device memory shows Unknown

Likely cause: Some browsers hide navigator.deviceMemory for privacy.

Fix: Treat it as unavailable; rely on hardwareConcurrency and viewport metrics instead.

Advertisement

Frequently Asked Questions

What browser information is displayed?

User agent, app name/version, platform, vendor, screen and window dimensions, device pixel ratio, page URL parts, languages, timezone, hardware concurrency, device memory (when available), max touch points, and flags such as cookies enabled and online status.

Is my browser information private?

Yes. Data is read and displayed only in your browser. We do not collect, store, or transmit your environment snapshot to EverydayTools servers.

Does the tool upload my data?

No. Everything runs locally via standard JavaScript APIs. Copy actions use your clipboard only—nothing is sent to our servers.

Can I copy the browser information?

Yes. Copy individual values (such as user agent or full URL) or use Copy All Info to export the full snapshot as formatted JSON.

Does it work on mobile devices?

Yes. Phones and tablets show the correct screen dimensions, DPR, and touch capabilities for that device when you open the page in the mobile browser.

Why do screen size and window size differ?

Screen dimensions describe the display; inner width/height describe the layout viewport inside the browser chrome. On desktop, the window is often smaller than the full screen.

How accurate is device memory?

deviceMemory is optional and may show as Unknown when the browser withholds it for privacy. hardwareConcurrency (CPU cores) is more widely available.

Can I use this for responsive design testing?

Yes. Combine viewport width, DPR, and screen metrics with the Screen Resolution Checker when you need breakpoint labels and layout-oriented checks.

Privacy, accuracy, and trust

Privacy

Environment data is read in your browser from standard APIs. Nothing is uploaded to EverydayTools—safe for internal URLs and local debugging.

Accuracy

Values reflect what your browser exposes at load time; they match the same APIs used in feature detection and responsive scripts.

Snapshots are point-in-time on load. Refresh after viewport changes. Not a substitute for security auditing or fingerprinting analysis.

Part of Developer Tools

More free tools for the same workflow.

Advertisement

Reviewed by EverydayTools Editorial Team on 2026-05-20.