Browser-specific bugs
Support teams often ask for a user agent to reproduce issues that only happen in one browser family or version range.
Live browser-side detection
This page reads the user agent currently exposed by your browser session, then turns that raw string into a readable summary for debugging, QA, screenshots, and extension verification.
This is the raw string exposed by navigator.userAgent in your current browser.
Useful for reproduction steps, but not enough for strong identity decisions.
Support teams often ask for a user agent to reproduce issues that only happen in one browser family or version range.
Sites may adjust layout, downloads, or compatibility prompts depending on whether the string looks like desktop, mobile, or tablet.
Many dashboards group traffic by browser family and operating system using user agent parsing rules.
If you use a user agent switcher, this page is a quick way to check whether your browser-side value changed after the extension update.
User agents can be spoofed or reduced. They are a strong debugging clue, not a secure device fingerprint.
Some websites also rely on request headers, Client Hints, server-side detection, and feature checks. This page is meant to stay fast and readable.
Use the guide to understand why strings include tokens like Mozilla/5.0, AppleWebKit, and browser-specific version markers.
Generate representative strings for QA fixtures, parser tests, and allowlist examples with export-friendly results.
Generate sample stringsIt shows the browser-side user agent value available to JavaScript. It is an excellent quick check, but not a replacement for a full request-header inspector.
Modern browsers sometimes reduce or normalize version detail to improve privacy and reduce fragile browser-sniffing behavior.
Yes. That is one of the main uses of this page. Copy the raw string, then include it together with page URL, expected behavior, and screenshot.