Racira Developers

Browser Info Detector

Detect browser details.

Output
Enter input to see results
Runs entirely in your browser. No data leaves your device.

More in Browser / Storage Utilities

Local Storage Viewer

Inspect localStorage entries.

Local Storage Manager

Manage localStorage entries.

Session Storage Viewer

Inspect sessionStorage entries.

JWT Local Inspector

Inspect JWTs from storage.

IndexedDB Viewer

Browse IndexedDB stores.

Canvas Drawing Tool

Draw on an HTML canvas.

WebGL Shader Playground

Experiment with WebGL shaders.

What is Browser Info Detector

The Browser Info Detector is a client-side diagnostic tool that reads and displays comprehensive information about the current browser environment. It accesses the Navigator, Screen, and Window APIs to collect 12 properties: the full user agent string (identifying browser name, version, and OS), the platform identifier, the primary language and full language list, whether cookies are enabled, online status, screen resolution (width and height in pixels), device pixel ratio (DPR), color depth, touch support (via maxTouchPoints), CPU core count (hardwareConcurrency), and estimated device memory (deviceMemory, where available). The tool outputs all properties in a clean, labeled format, making it easy to copy and paste into bug reports, compatibility documentation, or support tickets. This information is invaluable when debugging cross-browser issues, verifying that responsive designs target the correct screen sizes, or documenting the testing environment for QA.

How to Use Browser Info Detector

  1. Step 1: Open the Browser Info Detector tool. No input is required.
  2. Step 2: Click the Transform button (or the tool may auto-detect on load). The output panel displays all browser properties in a labeled list.
  3. Step 3: Review the information: the User Agent line shows the full browser identification string, Screen shows the display resolution, and Device Pixel Ratio indicates whether you are on a retina/HiDPI display.
  4. Step 4: Copy the output using the copy button. The formatted text is suitable for pasting into bug reports, issue trackers, or documentation.

Why Use Browser Info Detector

When filing a browser bug or compatibility issue, including browser environment details is essential but tedious to gather manually. The Browser Info Detector collects all relevant information in one click, eliminating the need to navigate multiple DevTools panels or manually construct the user agent string. The device pixel ratio is particularly important for responsive design — a CSS pixel width of 375 on a device with DPR 3 (like an iPhone) actually renders at 1125 physical pixels, and this distinction affects image sizing, media queries, and touch target dimensions. The memory estimate (where supported) helps developers understand performance constraints on low-end devices.

Privacy & Security

This tool runs entirely in your browser — no data ever leaves your device. There is no server round-trip, no upload, no logging, and no account required. Your input is processed locally using client-side JavaScript and is never stored, transmitted, or accessible to anyone else. When you close the tab, everything disappears.

Frequently Asked Questions

Why is deviceMemory sometimes undefined?

<p>The deviceMemory property is only available in Chrome and Edge. Firefox and Safari do not expose this information for privacy reasons. When unavailable, the tool displays '?'.</p>

Is the user agent string reliable?

<p>The user agent string can be spoofed or modified by browser extensions. For precise browser identification, use feature detection (checking for specific API support) rather than parsing the user agent.</p>

Does this detect browser extensions?

<p>No. Browser extensions are not visible to web pages through standard APIs. The tool only detects properties exposed by the Navigator, Screen, and Window interfaces.</p>

Can I detect specific browser features?

<p>The tool shows environment properties, not feature support. For feature detection (Service Worker, Web Crypto, etc.), use feature-detection libraries like Modernizr or manual checks like "serviceWorker" in navigator.</p>

Why is my user agent different in DevTools?

<p>Some browsers allow user agent override in DevTools (Network tab > More > Network conditions). The tool reads the current navigator.userAgent, which may differ from the real user agent if overrides are active.</p>

What does hardwareConcurrency tell me?

<p>HardwareConcurrency reports the number of CPU logical cores available. This is useful for tuning worker thread counts, parallel processing, and estimating device capability. A value of 2 suggests a low-end mobile device; 8+ suggests a desktop or workstation.</p>