User-Agent String Parser
Paste any browser User-Agent string — or use your own automatically — to extract the browser name and version, operating system, device type, and rendering engine.
- The text box is pre-filled with your own browser's User-Agent string, or paste in any other UA string to inspect.
- The parsed result updates instantly as you type or paste — no button click required.
- Read off the detected browser, operating system, device type, and rendering engine in the results table.
- Click "Use My Browser's UA" any time to reset the input back to your own User-Agent string.
All processing happens entirely in your browser. Your data never leaves your device.
Key Features
- Auto-fills with your own browser's live User-Agent string
- Paste any UA string to parse it instead — fully editable
- Detects Chrome, Firefox, Safari, Edge, Opera, and Samsung Internet with version numbers
- Detects Windows, macOS, Linux, Android, and iOS with version numbers where available
- Classifies device type as Desktop, Mobile, or Tablet
- Identifies the underlying rendering engine: Blink, Gecko, or WebKit
- Clean key-value results table with one-click copy
- 100% client-side regex parsing — no UA strings are sent to a server
About User-Agent String Parser
The User-Agent (UA) HTTP header is a string every browser sends with its requests, historically used by servers to detect which browser, operating system, and device a visitor is using. Because the format evolved organically over decades of browser competition, UA strings are notoriously messy — modern Chrome's UA string, for example, still contains the token "Mozilla/5.0" and "like Gecko" for historical compatibility reasons, even though it uses neither.
Parsing a UA string reliably means checking for specific tokens in a careful order, since many browsers include tokens belonging to other browsers for compatibility (Chromium-based Edge and Opera, for instance, both include "Chrome" in their UA string alongside their own distinguishing token). ForgeKit's User-Agent Parser hand-rolls this detection logic entirely with regular expressions, checking the most specific tokens first, to identify the browser, operating system, device type (desktop/mobile/tablet), and underlying rendering engine (Blink, Gecko, or WebKit).
This is useful for debugging analytics data, understanding what a support ticket's UA string reveals, or just satisfying curiosity about what your own browser reports. Everything is parsed locally with no server round-trip.
Frequently Asked Questions
It's inherently heuristic. Browsers can spoof their User-Agent string, some browsers deliberately freeze or reduce the detail in their UA string for privacy reasons (like Chrome's User-Agent Reduction initiative), and UA strings can be edited or omitted entirely by proxies and privacy tools. Treat results as a best-effort read, not a guaranteed identification.
For historical compatibility — early WebKit-based browsers included "Safari" in their UA string so websites that checked for it wouldn't break, and this tradition has stuck ever since across all WebKit- and Blink-based browsers, including Chrome, Edge, and Opera.
No. User-Agent strings generally identify the device family (iPhone, iPad, generic Android device) but not the specific model. Detecting exact hardware requires other signals that aren't reliably present in the UA string.
Windows 11 still reports "Windows NT 10.0" in its User-Agent string for backward compatibility — there's no reliable way to distinguish Windows 10 from Windows 11 from the UA string alone, so both are shown together.
No. It's read directly from your browser's navigator.userAgent property and parsed locally in JavaScript. Nothing about your browser or device is transmitted to a server by this tool.