How it works
The Browser Info tool displays comprehensive information about your current browser and device — user agent string, browser name and version, OS and version, screen resolution, viewport size, device type, language settings, timezone, and network type.
This information is essential for debugging cross-browser issues, reporting bugs with precise environment details, and understanding what clients your application serves. When a user reports "it doesn't work on my phone," knowing their exact browser, OS, and viewport is the first step toward reproducing and fixing the issue.
How to use it: open the tool and all information is collected instantly from the browser's JavaScript APIs — no input required. Click "Copy all" to get a formatted summary ready to paste into a bug report or support ticket.
Information provided: - User agent string (full, for direct use in debugging) - Parsed browser name, engine, and version - OS name and version - Device type (desktop, tablet, mobile) - CPU architecture (x86, ARM, etc.) - Screen resolution (physical pixels, not logical) - Device pixel ratio (1 = standard, 2 = Retina, 3 = high-DPI mobile) - Viewport size (visible browser window dimensions) - Color depth (bits) - Language(s) configured - Timezone - Connection type (wifi/cellular/ethernet if available)
Developer use case: paste the "Copy all" output into GitHub issues, Jira tickets, or support emails to give developers the complete picture without back-and-forth.
Frequently Asked Questions
- Yes. All information shown — user agent, screen resolution, viewport, language, timezone, device pixel ratio — is accessible to any website through browser JavaScript APIs. This is a major component of browser fingerprinting.
- Device pixel ratio (DPR) is the ratio of physical screen pixels to CSS logical pixels. DPR 1 = standard display (1 physical pixel per CSS pixel). DPR 2 = Retina display (4 physical pixels per CSS pixel in a 2×2 grid). Knowing DPR helps decide when to serve @2x images.
- Bugs are often browser, OS, or device specific. A CSS rendering bug in Safari 16 on iOS 16 won't reproduce in Chrome on Windows. Including the complete browser info eliminates back-and-forth and lets developers reproduce the issue immediately.
- No — the tool reads your own browser's APIs. To see another user's browser info, they would need to visit the tool themselves and share the output.