Developer Tools
What's My Browser? (User Agent, Screen & Viewport)
See your browser, version, operating system, user agent, screen resolution, viewport size, pixel ratio, language, time zone and supported features — handy for bug reports.
How to use
- 1Open the page — everything is detected instantly.
- 2Press Copy report to paste the details into a support ticket or bug report.
Frequently asked questions
What is a user agent?
A text string your browser sends to websites describing the browser, version and operating system.
Why is the viewport smaller than my screen?
The viewport is the visible page area — it excludes toolbars, tabs and scrollbars, and changes as you resize the window.
What is device pixel ratio?
How many physical pixels make up one CSS pixel. Retina and most phone screens have a ratio of 2 or 3.
"It's broken on my phone" isn't a bug report
A support ticket or GitHub issue is only actionable once it names a browser, version, OS and screen size — the four things this page detects automatically and formats into one plain-text block via Copy report. Pasting that block saves the back-and-forth of asking a user to check Settings → About, and it captures details they'd never think to mention, like device pixel ratio or whether cookies are disabled.
The user agent string is self-reported, and that's the catch
Detection here parses navigator.userAgent with ordered pattern matching — checking for Edg/, OPR/, SamsungBrowser/ and CriOS/ before falling back to Chrome/ or Safari, since Edge, Opera, Samsung Internet and Chrome-on-iOS all include "Chrome" or "Safari" somewhere in their UA string too. But the UA string is just text the browser chooses to send: it can be spoofed with DevTools' device toolbar, and Chrome has been progressively "freezing" and simplifying its UA string for privacy, which is also why fields like deviceMemory and connection.effectiveType often show "not exposed" — Safari and Firefox never implemented those APIs at all.
Worked example: screen size vs. physical pixels
Screen resolution and viewport size are reported in CSS pixels, but the Physical pixels row multiplies screen width and height by window.devicePixelRatio to show the real hardware density. A 13-inch MacBook Pro reports a screen resolution of roughly 1512 × 982 with a device pixel ratio of 2, so the physical pixels row works out to about 3024 × 1964 — the actual panel resolution. That gap is exactly why a 1512px-wide layout still looks sharp on that screen: every CSS pixel is drawn with four physical pixels.
Live settings, not fixed specs
Dark mode preferred and Reduced motion preferred read matchMedia('(prefers-color-scheme: dark)') and '(prefers-reduced-motion: reduce)' live from the OS, and Viewport updates on every window resize — useful for confirming your site's dark-mode or reduced-motion CSS is actually wired to the right media query, without digging through DevTools' rendering tab to fake the setting.
Touch points and CPU cores explain layout bugs, not just curiosity
Touch screen reports navigator.maxTouchPoints as a count rather than a yes/no — a laptop with a touchscreen can show "Yes (10 points)" while still having a mouse as the primary input, which is exactly the kind of device that breaks a "touch means phone" assumption in hover-dependent UI. CPU cores (navigator.hardwareConcurrency) is a hint, not a guarantee, since some browsers cap the reported number below the real core count for fingerprinting resistance — useful context if a site's claimed worker-thread pool seems to assume more cores than a visitor actually has.
Cookies enabled and Do Not Track are stated preferences, not enforcement
Cookies enabled reflects navigator.cookieEnabled, which only tells you whether the browser allows cookies to be set at all — it says nothing about third-party cookie blocking, which most current browsers apply by default regardless of this flag. Do Not Track mirrors navigator.doNotTrack, a header sites can see but are never obligated to honor; it's been dropped by Safari and several other browsers entirely because it had no legal teeth, so seeing "Off" here usually means the browser no longer sends the signal at all rather than that tracking is deliberately permitted.
Related tools
- HTML Boilerplate Generator
Generate a modern HTML5 starter page with the viewport meta tag, SEO description, Open Graph tags, favicon and stylesheet links.
- Semantic Version Calculator
Compare two semantic versions, check whether a version satisfies an npm range like ^1.2.0 or ~2.3, and see the next major, minor and patch versions.
- Python Online Compiler & Playground
Write and run Python 3 in your browser — no install, no account. Real CPython (Pyodide) with input(), NumPy, pandas and Matplotlib charts, and shareable links.
- AI API Cost Calculator (LLM Token Pricing)
Estimate what an LLM-powered feature will cost — tokens per request, requests per month, input/output prices per million tokens, prompt caching and batch discounts. Works for any model: enter your provider's current prices.
- Online Screen Recorder
Record your screen, a window or a browser tab — with optional microphone — right in your browser, then download the video. No install, no watermark.
- Browser Fingerprint Test
See what your browser reveals to websites without cookies — canvas and WebGL fingerprints, fonts, screen, time zone and hardware — and how identifiable that makes you.