Parse one User-Agent string per line
- Paste one or more User-Agent strings into the input, using one string per line.
- Click Add my browser's UA to append the User-Agent string reported by your current browser.
- Inspect Parsed results, then use Expand details on a row to read its full raw string and extra fields.
- Choose Copy JSON, Copy JSONL, or Copy CSV, or download the same formats with Export JSON, Export JSONL, or Export CSV.
Fields User-Agent Parser can identify
Rows may contain Browser / Bot, Engine, OS, Device type, Model, Unknown, and Raw. Browser patterns include Chrome, Firefox, Safari, Edge, Opera, Samsung Internet, Internet Explorer, UC Browser, Vivaldi, Brave, DuckDuckGo Privacy Browser, and Yandex Browser. Engine values include Blink, WebKit, Gecko, Trident, EdgeHTML, and Presto.
Bot signatures are checked before browser patterns. Matches include Googlebot, GPTBot, curl, Wget, PostmanRuntime, and HeadlessChrome. A match fills Browser / Bot, sets Device type to Bot / Crawler, and skips browser detection. Device models can include Android models, iPhone, iPad, Mac, PlayStation, and Nintendo Switch when the string matches one of those patterns.
Input: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Output: Browser / Bot = Googlebot
Device type = Bot / CrawlerHow lines become parsed rows
The input is split at line breaks. Leading and trailing spaces are removed from each line, and empty lines are ignored. Every remaining line creates one row. Results update as you type. Clear empties the input, removes the current rows, and hides the results workspace.
Add my browser's UA appends the value from the current browser, adding a new line when the input already contains text. Copy JSON and Export JSON produce an array. Copy JSONL and Export JSONL write one JSON object per line. CSV contains columns for the raw string, bot flag and name, browser, engine, OS, device, model, and unknown tokens.
What Unknown shows
After the detectors remove the text they recognize, the parser checks the remainder for Name/Version-shaped tokens. Matches can appear in Unknown and in the expanded row details. The check is best-effort, so an unusual token can stay unlisted. A string with no recognized browser or OS is counted as an unrecognized string.
Keep the raw string beside parsed fields
The Raw column shows the source string, and expanded details show it in full with the detected fields. This keeps a Chrome Windows string, an iPhone Safari string, or a Googlebot string available while you review the parsed values or export the rows.
Use Add my browser's UA to add the current browser value to the input. The parser keeps that value as its own row, so it can be compared with another pasted string in the same results table.
Choose a parser by input type
Use User-Agent Parser for browser, device, OS, engine, and bot details inside User-Agent text. The Parser Extract Tools page groups related parser tools.
Choose Cookie Parser for Cookie or Set-Cookie headers with names, values, attributes, duplicate markers, or warnings. Choose Logfmt Parser for key=value log lines with quoted values, escaped characters, repeated keys, and per-line warnings. Choose HTML Table Extractor when the source is HTML and the job is to turn tables into structured rows.
Frequently asked questions
How do I parse multiple User-Agent strings?
Paste one User-Agent string per line. Each non-empty line becomes its own row, and the parsed rows are included in copy and export actions.
Does User-Agent Parser detect bots?
Yes. It checks the input against built-in bot and crawler signatures before checking browser patterns, so a matching bot name appears in the Browser / Bot column.
Does it inspect live network traffic?
No. User-Agent Parser reads the text entered in the input and does not inspect incoming requests, client hints headers, or traffic.
What happens to an unknown User-Agent token?
A remaining Name/Version-shaped token may appear in Unknown and the expanded row details. The detector does not promise to list every unclassified token.
Can I export parsed User-Agent data?
Yes. Use Export JSON for an array, Export JSONL for one object per line, or Export CSV for column-based data. The matching Copy controls place the same formats on the clipboard.