Question 1

What is a User-Agent string?

Accepted Answer

Every HTTP request from a browser includes a User-Agent header, a string identifying the browser, version, OS, and device. Originally meant for servers to send appropriate content (a mobile site for mobile UAs). Modern UA strings are long, lying, and overstuffed because of decades of fake-compatibility hacks. Parsing them reliably requires careful regex against accumulated quirks.

Question 2

Why do User-Agent strings look so weird?

Accepted Answer

Historical accident. In 1995, Netscape's UA was 'Mozilla/3.0'. When IE3 launched, many sites checked for 'Mozilla' to serve modern HTML, so Microsoft made IE's UA include 'Mozilla' for compatibility: 'Mozilla/4.0 (compatible; MSIE 5.0...)'. Then every other browser did the same. Today every UA starts with 'Mozilla/5.0', most include 'WebKit', many include 'Chrome', and Edge says it's Chrome which says it's Safari which says it's a Mozilla browser. The string is a fossil record of browser-detection bug workarounds.

Question 3

Should I rely on User-Agent detection in my code?

Accepted Answer

Avoid it where possible. Use feature detection (does navigator.share exist? does the browser support service workers?) instead of browser detection. UA strings can be spoofed, are inconsistent, and break when new browsers launch. Use UA detection only for analytics, bot blocking, and edge cases where feature detection isn't possible (e.g., iOS-specific quirks).

Question 4

How accurate is bot/crawler detection?

Accepted Answer

Good for honest bots (Googlebot, Bingbot, Twitterbot, Facebook crawlers identify themselves cleanly). Useless against bots that mimic real browsers (scrapers, automation tools, malicious bots). For comprehensive bot protection, combine UA detection with: rate limiting, behavioral analysis (mouse movement, scroll patterns), JS challenges, and IP reputation services. UA alone is the easiest signal but also the easiest to forge.

Question 5

What's the difference between Chromium, Chrome, and Edge in UA strings?

Accepted Answer

Chromium is the open-source browser project; Chrome, Edge, Opera, Brave, and many others are built on it. They share the rendering engine (Blink) and a lot of the codebase. UA strings reflect this: Edge's UA mentions Chrome (because it IS Chrome with extensions), Opera's mentions Chrome, Brave's mentions Chrome. Parsing requires checking specific markers (Edg/, OPR/, Brave/) to distinguish them.

Question 6

Why does iPad sometimes look like a Mac?

Accepted Answer

iPadOS 13+ defaults to a 'desktop class browsing' mode where Safari sends a Mac UA string. This was intentional, Apple wanted iPad users to get the desktop version of websites rather than mobile versions. Detection workarounds: check 'iPad' explicitly in the UA, or use the navigator.maxTouchPoints API (which Macs return 0 for, iPads return >0).

Question 7

Will UA strings disappear?

Accepted Answer

Probably. Google has been pushing 'User-Agent Client Hints' as a replacement, structured fields the browser sends only when servers ask. This reduces fingerprinting and makes detection more honest. Chrome has been freezing/reducing UA strings since 2021. UA strings won't vanish overnight (too much code depends on them), but expect their detail to shrink and Client Hints to grow.

Question 8

What standards does User Agent Parser validate against?

Accepted Answer

User Agent Parser checks compliance with Input format specification.

Question 9

What are the limitations of User Agent Parser?

Accepted Answer

Parsing is client-side, limited by browser memory Does not handle all edge cases in malformed input

Browser	Engine	Distinguishing Token	UA Dialect
Chrome	Blink	`Chrome/X`	Modern
Edge	Blink	`Edg/X`	Chromium-based
Safari	WebKit	`Version/X Safari/X`	Legacy Apple
Firefox	Gecko	`Firefox/X`	Open Standard

User Agent Parser

User Agent Parser

Learn More

Browser Crypto Speed Test: Web Crypto API Benchmarks for AES, PBKDF2, and RSA in 2026

WebAssembly in 2026: SIMD, Threads, Wasm 3.0, and the New Browser-First Toolkit

What is User Agent Parser?

Frequently Asked Questions

Technical Deep Dive

User Agent Parser

Browser, OS, engine, device

Bot & crawler flags

Runs on the string you paste

01 Browser & Engine Hierarchy

02 Parsing Logic Pipeline

Runs 100% in your browser

You Might Also Need

Git Commit Message Generator

Regex Explainer

AI Code Review Assistant

API Client Code Generator