User-Agent Parser

Paste a UA string to instantly identify the browser, engine, OS, and device type

Report
Examples:
User-Agent
Paste a UA string in the field above and click Parse — results will appear here.
Browser
Engine
OS
Device type
Raw string
Paste the UA
Paste any User-Agent string into the input field, or click "Load my UA" to auto-fill the UA of your current browser.
Parse
Click Parse or paste into the field to trigger automatic parsing. All logic runs locally in your browser — nothing is sent to our servers.
Review and copy
Results show the browser, version, engine, OS, and device type. Click "Copy JSON" to export the parsed data as structured JSON.
When do I need to parse a User-Agent?
Common scenarios include front-end compatibility debugging, analyzing server access logs, determining visitor device types, and building features that behave differently based on the browser environment. Quickly parsing a UA string saves time compared to manually reading the raw string.
How accurate are the results?
UA string formats have historically been messy — browsers have mimicked each other's UA for compatibility reasons, making reliable parsing difficult. This tool uses rule-based parsing and results are for reference only; 100% accuracy cannot be guaranteed.
Is my UA string uploaded to your servers?
No. All parsing runs entirely in your browser. Your UA string is never sent over the network to our servers.
What is the difference between User-Agent and Client Hints?
User-Agent is a traditional single-string header — information-rich but messy and hard to parse. Client Hints (e.g. Sec-CH-UA) are a newer structured approach providing more precise browser information while helping protect user privacy. Starting with Chrome 113, parts of the UA string are frozen by default and replaced by Client Hints.
Why does Chrome on iOS look like Safari in its UA?
Apple requires all browsers on iOS to use the WebKit rendering engine. As a result, iOS Chrome includes Safari-related strings (such as AppleWebKit and Version/X.X) in its UA, making it hard to distinguish from native Safari. This is a platform restriction, not a parser limitation.
How does bot detection work?
This tool matches common crawler keywords in the UA string (bot, crawler, spider, etc.). However, UA strings can be spoofed. Server-side bot detection in production should combine IP reverse-DNS lookups with behavioral analysis rather than relying solely on the UA.
API REST HTTP
2026-06-22

API Resource State Management: From HTTP Semantics to Consistent Architecture

A deep dive into the philosophy of resource management behind HTTP status codes, exploring state consistency, idempotency, and common API design pitfalls in RESTful architectures.

encoding Unicode URL-encoding
2026-06-03

Encoding Standards and Network Transmission: A Complete Guide to Character and URL Encoding

Understand the mechanics of character encoding, Base64 applications, and the vital role of URL encoding in modern web communication to resolve encoding issues.

API HTTP Web Development
2026-06-02

Optimizing Network Communication: Advanced Practices for High-Performance API Construction

Deep dive into modern Web API communication architectures, from precise status code application to protocol fine-tuning, to improve system stability and developer experience.

ISO 8601 Date Format Timezone Handling
2026-05-26

ISO 8601 Date Standard: The Universal Language of Data Exchange

Dive deep into the ISO 8601 date format and learn how standardized time formats can solve challenges in cross-timezone and cross-system data transmission and parsing.

Encoding Standards UTF-8 URL Encoding
2026-05-24

Character Encoding and URL Safety: A Practical Guide from UTF-8 to Percent-Encoding

A deep dive into how computers process text encoding, exploring URL encoding rules and the critical impact of character conversion on system stability.

HTTP API Web Development
2026-05-23

HTTP Status Codes and API Design: The Art of Modern Web Communication

A deep dive into HTTP status code logic and REST API best practices to improve frontend-backend collaboration and system stability.