Inspection • 100% Client-Side

User-Agent String Parser & Client Inspector

Parse and decode browser User-Agent strings to extract Browser Name & Version, Operating System, Device Model, CPU Architecture, and Engine metadata in real time.

Input Configuration

User-Agent Header String

Live Generated Result

Browser & VersionUnknownvUnknown

Operating SystemUnknownDesktop

Device ModelUnknown DeviceDesktop

Rendering EngineUnknown

Client & Bot ClassificationStandard Browser

RAW USER-AGENT STRING

No User-Agent string provided

Inspection Guide

About the User-Agent String Parser & Client Inspector

Every web browser, mobile application, crawler bot, and HTTP client sends a User-Agent request header to identify its software brand, version, operating system, device model, and rendering engine. However, User-Agent strings are famously messy and complex due to decades of historical browser compatibility hacks (e.g. modern Chrome still includes Mozilla/5.0, AppleWebKit, and Safari in its UA string). The User-Agent String Parser & Client Inspector analyzes any User-Agent string in real time. It extracts clean, structured device metadata, detects mobile vs. desktop clients, identifies crawler bots, and displays your own live browser User-Agent with one click.

In-Depth Technical Guide

How User-Agent String Parser & Client InspectorWorks & What the Results Mean

Deconstructing a Modern User-Agent String

A modern desktop Chrome User-Agent header illustrates the layered historical tokens:

$$\text{Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36}$$

Browser Name & Major/Minor Version: Identifies the true client (e.g. Chrome 128.0.0.0, Safari 17.4, Firefox 129.0, Edge 128.0).
Operating System & Version: Extracts the host OS platform (Windows 11 / 10, macOS Sonoma 14.5, iOS 17.5, Android 14, Linux x86_64).
Device Type & Model: Classifies the client form factor: Desktop, Mobile Phone, Tablet, Smart TV, Wearable, or Console.
Rendering Engine: Identifies the underlying layout engine (Blink, WebKit, Gecko, Trident).
Bot & Crawler Classification: Detects automated spiders such as Googlebot, Bingbot, GPTBot, Twitterbot, and curl/7.88.

Primary Everyday Applications

Web Analytics & Traffic Auditing: Categorizing device types and browser market share from web server access logs.
Responsive Design Debugging: Inspecting how mobile Safari or Android Chrome identify themselves during HTTP requests.
Bot & Security Filtering: Identifying automated scraping bots in backend security firewalls.

Step-by-Step Guide

How to Use User-Agent String Parser & Client Inspector

1Paste any User-Agent string into the editor workspace, or click 'Use My Current User-Agent' to detect your active browser.
2The parser decomposes the string into structured metadata in real time.
3Review the Primary Summary Card displaying Browser Name, Browser Version, OS Name, and Device Type.
4Inspect the Technical Details table showing Rendering Engine, CPU Architecture, and Bot Status.
5Click 'Copy JSON Metadata' to copy the extracted data as a structured JSON object.
6Test preloaded sample User-Agent strings (iPhone Safari, Android Chrome, Googlebot, Mac Firefox) for benchmarking.

Capabilities

Key Features & Highlights

Comprehensive User-Agent parser decoding Browser, OS, Device, Engine, and CPU architecture.
1-Click 'Detect My Current User-Agent' button for instant device diagnostics.
Bot and Search Crawler identifier detecting Googlebot, Bingbot, GPTBot, and social scrapers.
Form factor classification: Desktop, Mobile Phone, Tablet, Smart TV, and Embedded Bot.
Structured JSON export action for analytics and logging integrations.
Preloaded User-Agent library covering iOS, Android, macOS, Windows, Linux, and major search bots.
One-click copy actions with visual feedback.
100% in-browser parsing with complete privacy.

Practical Scenarios

Examples & Real-World Use Cases

Parsing an iPhone Mobile Safari User-Agent

Scenario: Extracting device model and iOS version from a mobile UA header.

Sample Input:

Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.5 Mobile/15E148 Safari/604.1

Expected Output:

Browser: Mobile Safari 17.5 | OS: iOS 17.5 | Device: Apple iPhone (Mobile) | Engine: WebKit

Extracts Apple hardware model, iOS version, and WebKit engine.

Detecting a Google Search Crawler Bot

Scenario: Identifying a search spider from server access logs.

Sample Input:

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

Expected Output:

Browser: Googlebot 2.1 | Device Type: Search Engine Spider (Bot) | Verified: Yes

Identifies automated Google crawler bot metadata.

Common Questions

Frequently Asked Questions

In the early days of the web, Netscape Navigator (code-named Mozilla) supported advanced features like frames. Other browsers added 'Mozilla/5.0' to their User-Agent strings so web servers would not block them or serve stripped-down legacy pages. The legacy prefix persists for backwards compatibility.

Explore More

Related Inspection Tools

Reference

HTTP Status Codes Reference

Explore standard HTTP response status codes.

Open Tool

Reference

MIME Types Lookup

Look up official Content-Type media types.

Open Tool

Security

JWT Debugger

Inspect authentication tokens.

Open Tool