App StoreApp Store
Google PlayGoogle Play
Temp Mail Logo

Temp Mail safeguards your privacy while keeping your inbox free from spam.

🌐 Browser · OS · Device · Engine · Architecture

User Agent Parser

Free User Agent parser. Instantly detect browser, version, operating system, device type, rendering engine, and CPU architecture from any UA string. Auto-detects your own browser on load.

✓ Auto-detects your UA✓ Browser & version✓ OS detection✓ Device type✓ No signup
User Agent String Parser
Try a sample UA:
What this tool does

Free User Agent parser — detect browser, OS, device, and engine from any UA string

What User Agent strings are, how they work, and what each component means

This User Agent parser analyses any UA string and breaks it down into its components: browser name and version, rendering engine, operating system and version, device type (desktop, mobile, tablet, or bot), device brand and model, and CPU architecture. It runs entirely in the browser — no data is sent to a server, and parsing is instant.

The parser auto-detects your own browser's UA string on page load using the browser's navigator.userAgent API. You can also paste any UA string to parse it, or choose from the sample UAs covering Chrome on Windows, Safari on iPhone, Firefox on Linux, Edge, Samsung Browser, and Googlebot.

Common use cases include: debugging responsive layouts by checking which device type a UA resolves to, verifying bot detection logic in web applications, understanding analytics data by looking up unfamiliar UA strings, testing server-side UA parsing code against known strings, and investigating support tickets where a user's browser and OS are unknown.

Features and capabilities
Auto-Detection
Reads navigator.userAgent on load and pre-fills your own browser's UA string so you can see your own device info instantly.
Browser Detection
Identifies 18+ browsers including Chrome, Firefox, Safari, Edge, Opera, Brave, Vivaldi, Samsung Browser, UC Browser, and legacy IE.
OS Detection
Detects Windows (with version mapping: NT 10.0 → 10/11), macOS, iOS, iPadOS, Android, Linux, and ChromeOS.
Device Classification
Classifies device as desktop, mobile, tablet, or bot/crawler based on UA patterns — the same logic used in real analytics platforms.
Device Model
Identifies iPhone, iPad, Samsung Galaxy (SM- prefix), Google Pixel, Nexus, and generic Android devices where model is embedded.
Engine Detection
Detects Blink (Chrome/Edge/Opera), WebKit (Safari), Gecko (Firefox), and Trident (IE) — correctly separates Blink from WebKit forks.
Architecture
Identifies ARM64 (Apple Silicon, Android), x86_64 (64-bit Windows/Linux), x86 (32-bit), and ARM from UA hints.
Sample UA Library
6 ready-to-parse sample UAs covering the most common browsers, mobile, and bot scenarios — great for testing parsing logic.
100% Client-Side
All parsing happens in your browser with JavaScript regex — no UA string is ever sent to a server. Completely private.
No Signup Required
Paste any UA string and click Parse — no account, no API key, works on any browser.
Examples

User Agent string examples — Chrome, Safari, Firefox, bots, and mobile browsers

Annotated UA strings showing what each segment means
Chrome / WindowsGoogle Chrome 124 on Windows 11 — annotated breakdown
Mozilla/5.0 ← compatibility token (meaningless today) (Windows NT 10.0; Win64; x64) ← OS: Windows 10/11, 64-bit AppleWebKit/537.36 ← engine compatibility token (KHTML, like Gecko) ← more compatibility tokens Chrome/124.0.0.0 ← actual browser: Chrome 124 Safari/537.36 ← Safari compatibility token

Chrome's UA is packed with compatibility tokens from the browser wars era. The only genuinely useful parts are the Windows NT version (10.0 = Windows 10 or 11), the Win64/x64 architecture, and Chrome/124.0.0.0. Everything else exists for backward compatibility with old server-side sniffers.

Safari / iPhoneMobile Safari on iPhone running iOS 17
Mozilla/5.0 (iPhone; ← device: iPhone CPU iPhone OS 17_4 like Mac OS X) ← OS: iOS 17.4 (underscores instead of dots) AppleWebKit/605.1.15 ← engine: WebKit 605.1.15 (KHTML, like Gecko) Version/17.4 ← Safari version Mobile/15E148 ← mobile build identifier Safari/604.1 ← compatibility token

iOS Safari is interesting because iOS version numbers use underscores (17_4 = 17.4). All browsers on iOS must use WebKit due to Apple's App Store rules — so Chrome, Firefox, and Edge on iPhone all have essentially the same UA as Safari, just with an extra token identifying the wrapper app.

GooglebotGooglebot — the most important bot to recognise
Mozilla/5.0 (compatible; ← signals compatibility mode Googlebot/2.1; ← bot name and version +http://www.google.com/bot.html) ← documentation URL Verification: to confirm a request is really from Google, reverse-DNS lookup the IP → must resolve to *.googlebot.com

Googlebot identifies itself clearly so sites can serve crawlable content and apply appropriate rules. However, UA strings can be spoofed — anyone can send a request claiming to be Googlebot. To verify a request is genuinely from Google, perform a reverse DNS lookup on the requesting IP and confirm it resolves to a *.googlebot.com hostname.

FAQ

Frequently asked questions about User Agent strings

What is a User Agent string?
A User Agent (UA) string is a text identifier that your browser sends to every web server with each HTTP request, in the User-Agent request header. It tells the server which browser, version, operating system, and device made the request. Servers use this information for analytics, to serve browser-specific content, to block scrapers, and to provide appropriate layouts for different devices. The UA string is completely controlled by the client — it can be changed or spoofed.
How do I find my own User Agent string?
This tool automatically detects and displays your current browser's User Agent string when the page loads — it appears pre-filled in the text box. You can also find it by opening browser DevTools (F12), going to the Console tab, and typing navigator.userAgent. Alternatively, search 'my user agent' in Google, which shows it directly in the search results.
Can User Agent strings be faked?
Yes, completely. User Agent strings are just text sent by the client and can be changed to anything. All major browsers allow you to change your UA in Developer Tools (DevTools → Network conditions → User agent). Browser extensions can also spoof UAs. This means server-side UA detection for security purposes is unreliable — it should only be used for progressive enhancement, analytics, and content optimisation, never for access control.
Why do all browsers include Mozilla/5.0?
The Mozilla/5.0 prefix at the start of almost every modern browser's UA string is a historical quirk. When Netscape (which used Mozilla as its code name) was dominant, many servers only served rich content to browsers that identified as Mozilla. Internet Explorer and other browsers started including Mozilla/5.0 in their UAs to receive the same content. The practice propagated to every browser since. Today it is a meaningless compatibility token.
What is the difference between browser engine and browser?
The browser engine (also called rendering engine or layout engine) is the core software component that interprets HTML, CSS, and JavaScript and renders the visual output. Browsers are built on top of engines. Chrome, Edge, Opera, Brave, and Samsung Browser all use Blink (a fork of WebKit). Firefox uses Gecko. Safari uses WebKit. Internet Explorer used Trident. A browser engine can have many browsers built on it, which is why Blink-based browsers look similar in DevTools.
What does the 'like Gecko' part mean in Safari's UA?
Similar to the Mozilla/5.0 prefix, 'like Gecko' and 'KHTML, like Gecko' are compatibility tokens that tell servers the browser is compatible with Gecko-based rendering. They don't mean the browser actually uses Gecko. Safari uses WebKit, but includes the 'like Gecko' string for historical compatibility with content-sniffing servers that only served rich content to Gecko-compatible browsers. These historical artefacts are why UA parsing is notoriously tricky.
How do bots identify themselves?
Well-behaved bots like Googlebot, Bingbot, and other legitimate crawlers include identifiable strings in their User Agent so servers can recognise them and apply appropriate rules (e.g. respecting robots.txt, serving crawlable content). Malicious bots often spoof popular browser UAs to avoid detection. You can verify whether a request claiming to be from Googlebot is actually from Google by performing a reverse DNS lookup on the requesting IP and checking it resolves to a googlebot.com domain.
Related Tools

Need a disposable email address?Get a free instant throwaway email — no signup, no trace.

Get Free Temp Mail →