What is a User-Agent string?
The User-Agent HTTP header tells servers which client made a request—a desktop browser, mobile app, API client, or search crawler. Analytics pipelines, WAF rules, and responsive design often read it from access logs.
Decode UA strings. Identify browser, OS, device, and bots
Use this free user agent parser to decode any HTTP User-Agent string instantly. Identify browser, engine, operating system, device type, and bot/crawler status. Perfect for debugging analytics, log analysis, and compatibility checks. Single and bulk modes. 100% client-side — your data never leaves your browser.
How time-bound leases give cluster nodes exclusive access without holding it forever when things go wrong
Parsing runs as you type. Click My Browser to inspect your current session.
One UA per line. Up to 5,000 lines. Processed locally in your browser.
Mozilla/5.0 | Compatibility prefix (historical) |
AppleWebKit | WebKit-based rendering engine |
Gecko | Firefox engine family |
Chrome/ | Chromium version (also Edge, Opera) |
Safari/ | Safari or WebKit version token |
Edg/ | Microsoft Edge (Chromium) |
Windows NT | Windows desktop |
iPhone / iPad | Apple mobile / tablet |
Android | Android OS |
Mobile | Mobile-optimized browser |
bot / crawl | Likely crawler or spider |
curl / wget | Command-line HTTP client |
The User-Agent HTTP header tells servers which client made a request—a desktop browser, mobile app, API client, or search crawler. Analytics pipelines, WAF rules, and responsive design often read it from access logs.
Mozilla/5.0 for compatibility with legacy server sniffing.Windows NT 10.0, Macintosh, or iPhone; CPU iPhone OS 17_2.AppleWebKit/537.36 or Gecko/20100101 identifies the rendering engine.Chrome/120.0.0.0 or Firefox/121.0, often after a Safari compatibility token.Modern Chromium browsers also send Client Hints headers (Sec-CH-UA, Sec-CH-UA-Mobile, Sec-CH-UA-Platform) with structured, less spoofable metadata. The classic User-Agent string is still widely logged; this tool parses that header. For Client Hints, inspect request headers in your browser Network tab.
navigator.userAgent from your session.A User-Agent string is sent in the User-Agent HTTP header. It describes the client—browser, app, or bot—making the request. Servers log it for analytics, compatibility, and bot filtering.
Most browsers start with Mozilla/5.0, then platform tokens, engine details (AppleWebKit or Gecko), and end with the real browser name like Chrome/120.0.0.0.
Look for bot, crawl, spider, or names like Googlebot. CLI tools send curl, python-requests, or similar. This parser flags likely bots automatically.
Mobile UAs include Mobile, Android, or iPhone. Tablets often list iPad. The device class badge shows desktop, mobile, tablet, or bot.
Client Hints (Sec-CH-UA-*) are newer headers with structured browser/platform data. They complement the User-Agent string. This tool parses the classic User-Agent header.
Yes. Any client can send a fake UA. Use it for analytics and coarse hints—not as a security boundary. Combine with Client Hints, CAPTCHAs, or rate limiting for bots.
This tool runs 100% in your browser. UA strings are never uploaded. Your log data stays on your machine unless you export it.
Python ua-parser, npm packages, and log processors offer similar output for scripts. This browser tool is ideal for quick checks, sharing with teammates, and bulk paste without installing tools.