The vocabulary of the User Agent Parser API

The 10 fields and concepts you'll meet in the response — defined in plain English, each with a real example value.

10 terms
Client Identification6

User Agent

A string sent by browsers and applications that identifies the client software, operating system, and device type.

User agents follow loose conventions but vary widely. They typically include browser name/version, rendering engine, OS, and device type. Parsing libraries extract this information for device detection, analytics, and serving device-specific content.

ExampleMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 Chrome/120.0.0.0

Browser Detection

The process of identifying which web browser is making a request, including its name and version.

Browser detection helps serve compatible code, polyfills, and browser-specific features. Modern practice favors feature detection over browser detection when possible, but user agent parsing remains useful for analytics and debugging.

Examplebrowser: {name: "Chrome", version: "120.0.0.0", major: "120"}

Mobile Detection

Identifying whether a request comes from a mobile device (phone or tablet) versus desktop.

Mobile user agents typically include "Mobile" tokens. Tablets may identify as mobile or desktop. Detection via user agent is 85-90% accurate—combine with screen size checks for critical decisions. Mobile detection enables serving optimized assets and simplified interfaces.

ExampleisMobile: true, device: {type: "mobile", vendor: "Apple", model: "iPhone"}

Device Type

The category of device making a request: desktop, mobile, tablet, or bot.

User agent parsing extracts device type from various signals. Mobile phones include "Mobile" tokens. Tablets may include "Tablet" or report as desktop. Bots are identified by crawler signatures. Device type determines UI/UX optimizations.

Exampledevice: {type: "mobile"}, device: {type: "desktop"}, device: {type: "bot"}

Operating System

The platform software running on the client device, identified via user agent parsing.

User agents reveal OS name and version: Windows (NT 10.0), macOS (Macintosh), Linux, Android, iOS. OS detection helps with compatibility decisions, analytics segmentation, and serving platform-specific downloads.

Exampleos: {name: "Windows", version: "10"}, os: {name: "iOS", version: "17"}

Rendering Engine

The browser component that parses HTML/CSS and displays web pages, identified in user agent strings.

Common engines include Blink (Chrome, Edge, Opera), WebKit (Safari), and Gecko (Firefox). User agents include engine names for compatibility signaling. Engine information helps identify browser capabilities and behavior.

Exampleengine: {name: "Blink", version: "120"}, engine: {name: "WebKit"}

Traffic Analysis2

Bot Detection

isBotbotTypebotName

Identifying automated traffic from bots, crawlers, and scrapers versus human users.

Legitimate bots (Googlebot, Bingbot) identify themselves clearly. Malicious bots spoof user agents to appear human. Effective detection combines user agent analysis, behavioral signals, IP reputation, and JavaScript challenges. Bot traffic should be segmented in analytics.

{ isBot: true, botType: "crawler", botName: "Googlebot" }

Crawler

crawlerpurpose

An automated program that systematically browses websites, typically for search engine indexing or data collection.

Search engine crawlers (Googlebot, Bingbot) index content for search results. Social crawlers (facebookexternalhit) generate link previews. SEO crawlers audit sites. Crawlers should identify themselves via user agent and respect robots.txt directives.

{ crawler: "Googlebot/2.1", purpose: "search engine indexing" }
Modern Standards1

Client Hints

A modern HTTP header-based mechanism for sending client device information, replacing traditional user agent strings.

Client Hints (Sec-CH-UA headers) provide structured device data with privacy controls. Browsers send basic info by default; servers request detailed info as needed. This reduces passive fingerprinting while enabling device-specific optimization. Adoption is growing but incomplete.

ExampleSec-CH-UA: "Chrome"; v="120", Sec-CH-UA-Platform: "Windows"

Best Practices1

Feature Detection

Testing for specific browser capabilities rather than identifying the browser itself.

Feature detection checks if APIs exist (e.g., if ("geolocation" in navigator)). This is preferred over browser detection when possible because it directly tests capability rather than assuming based on browser name. Combine with user agent data for comprehensive compatibility handling.

Exampleif (typeof localStorage !== "undefined") { /* use localStorage */ }

See these fields live. Run the User Agent Parser API free — no card, no signup wall.

Scaling up?

Volume pricing, custom SLAs, and dedicated support for high-traffic teams.

Contact sales