User Agent Parser
Read Any Browser String
This user agent parser reads any User-Agent string and names the browser, engine, system, device and bot. Paste one string or many. We upload nothing.
- FreePrice
- BulkInput
- NoneSign-up
- NoneUploads
User Agent Parser
Read any User-Agent string: browser, system, device and bot
| No. | Browser | Operating system | Device type |
|---|
Ready. Paste a User-Agent string.
What A User Agent Parser Does For You
A user agent is a line of text that your browser sends with every request. It names the browser, the system and often the device. But the line is messy, and it is hard to read by eye.
A user agent parser reads that line for you. First, it finds the browser and its version. Then it names the engine, the operating system, the device and the processor.
It also spots bots. So you can tell Googlebot, an AI crawler or a plain script from a real visitor. Also, it works on one string or on a whole log.
Everything runs in your browser. So your strings never leave your device.
How The User Agent Parser Works
The tool matches the string against rules for browsers, systems, devices and bots. Then it shows each result in a card. The rules run in your browser, so nothing is sent.
The parser reads the string in a set order, because many strings carry the name of more than one browser.
For more detail, see: MDN guide to the User-Agent header.
Parse One String
Paste a string, or press Use my browser to read your own. The result cards fill in as you type.
Each card shows one fact, such as the browser, the engine or the device type.
Browser And Version
The parser names the browser, such as Chrome, Firefox, Safari, Edge, Opera or Samsung Internet. It also reads the version number.
Edge, Opera and Samsung Internet all say Chrome in their strings. So the parser checks their own names first.
Engine
The engine draws the page. Chrome, Edge and Opera use Blink. Firefox uses Gecko, and Safari uses WebKit.
On an iPhone or an iPad, every browser has to use WebKit. So the parser says WebKit even for Chrome on iOS.
Operating System
The tool reads Windows, macOS, iOS, iPadOS, Android, ChromeOS and Linux. It also reads the system version. For example, 10_15_7 becomes 10.15.7.
Device Type And Model
The parser sorts devices into desktop, mobile, tablet, smart TV, game console and bot. For Android phones it also reads the maker and the model, such as a Pixel or a Galaxy.
CPU
When the string names a processor, the tool shows it, such as x64 or ARM64. Many strings leave it out, so an empty field is normal.
Spot Bots And Crawlers
The bot list covers search engines, AI crawlers, SEO tools, social media previews, testing tools, uptime monitors and code libraries.
So the result tells you what kind of bot sent the string.
A Word On Fake Bots
Any client can send any string. A script can call itself Googlebot. So treat the bot result as a hint, and check the IP address with a reverse DNS lookup when it matters.
Parse Many Strings At Once
Switch What to parse to Many strings and paste one string per line. The tool fills a table and counts the most common browsers, systems and devices.
Then you can copy the table as CSV.
Read A Log File
Paste the user agent column of your server log. So you can see which browsers visit your site, and how much traffic comes from bots.
Token By Token
The tool also splits the string into pieces and labels each piece. So you learn why a string starts with Mozilla/5.0, and why it says like Gecko.
Why Every String Starts With Mozilla
In the 1990s, sites sent the best pages to Netscape, whose code name was Mozilla. So other browsers added Mozilla to their strings. The habit never went away.
Reduced User Agent Strings
Chrome now sends a reduced string. The minor version shows as zeros, and the Windows and Mac versions stay frozen.
On Android, the model shows as the letter K. So the string tells you less than it did before.
Client Hints
Chrome and Edge offer Client Hints, which give the same facts in a cleaner way. The tool lists them for your own browser. Safari and Firefox do not offer them yet.
Windows 10 Or 11
Windows 11 still says NT 10.0 in the string. So no parser can tell Windows 10 from Windows 11 by the string alone. The tool says Windows 10 or 11.
iPad In Desktop Mode
Safari on an iPad can send a Mac string. So a Mac result with Safari could be an iPad.
Copy As JSON
Press Copy as JSON to get the result as a small object. You can paste it into a test, a ticket or a script.
Limits
The tool reads strings up to 2,000 characters, and up to 500 lines in bulk mode. The table shows the first 300 rows.
Safe By Design
First, the tool works in your browser. It sends nothing, and it stores nothing. So your strings stay yours.
On this page
- The tool
- What A User Agent Parser Does For You
- Using The User Agent Parser, Step By Step
- What This User Agent Parser Does Differently
- Habits For Working With User Agent Strings
- Common Mistakes With User Agent Strings
- User Agent Parser Questions People Ask
- Handy Companions For Technical Checks
Keep going
Using The User Agent Parser, Step By Step
Four steps take you from a long string to clear facts.
- 1
Paste a string
Paste one, or press Use my browser.
- 2
Read the cards
See the browser, engine, system and device.
- 3
Check the tokens
See what each piece of the string means.
- 4
Copy the result
Copy it as JSON, or as CSV for many strings.
What This User Agent Parser Does Differently
It reads one string or a whole log, and it keeps your data private.
One or many
Parse a single string, or paste a log with one string per line.
Bot detection
Spot search, AI, SEO and social crawlers, and plain scripts.
Token by token
Each piece of the string gets a short label.
Honest notes
It warns about reduced strings, Windows 11 and iPad in desktop mode.
Client Hints
See what your own browser reports in the newer format.
Nothing leaves your tab
Your browser does the work. We never see your strings.
Habits For Working With User Agent Strings
A few habits keep your results honest.
- Treat the string as a hint. Any client can send any string, so never trust it for security.
- Check bots by IP. Use a reverse DNS lookup to confirm a crawler that claims to be Googlebot.
- Prefer feature detection. Test what a browser can do, instead of guessing from its name.
- Expect reduced strings. Chrome hides the minor version and the device model.
- Read whole logs. Bulk mode shows the real browser and device mix of your visitors.
- Keep old browsers in view. A small share of visitors may still use a browser without support.
- Mind privacy. A user agent is part of a fingerprint, so store as little as you can.
- Update your test strings. Real strings change with every release, so refresh your samples.
Common Mistakes With User Agent Strings
Each of these quietly breaks a rule or a report.
Searching for Chrome only
Edge, Opera and Samsung Internet also say Chrome. Check their names first.
Blocking by string
A bad actor changes the string in a second. Block by behaviour instead.
Trusting a Googlebot name
Anyone can claim it. Confirm the IP address.
Calling every iPad a Mac
An iPad in desktop mode sends a Mac string.
Reading Windows 11 as 10
Both say NT 10.0, so a string cannot tell them apart.
Using an old regex list
New browsers and bots appear all the time. Test with fresh strings.
User Agent Parser Questions People Ask
Is this user agent parser free?
Yes. It costs nothing, needs no account and has no limits on use. It runs in your browser, so we have no server cost to pass on.
Does my string leave my device?
No. Your browser does all the work. So nothing reaches this site, and we keep nothing.
What is a user agent?
It is a line of text that a browser or app sends with each request. It names the software, and often the system and the device.
What is my user agent?
Press Use my browser. The tool fills the box with the string that your browser sends, then reads it.
How do I parse a user agent string?
Paste it into the box. Then read the cards for the browser, engine, system, device, CPU and bot.
Can I parse many strings at once?
Yes. Pick Many strings, and paste one string per line. Then the tool fills a table and counts the most common browsers, systems and devices.
How many lines can I paste?
Up to 500 lines. Also, each string can hold 2,000 characters.
Can it find out if a visitor is a bot?
Yes, when the string names a known crawler or script. However, a bot can lie, so treat the result as a hint.
Which bots does it know?
It knows search engine crawlers, AI crawlers, SEO tools, social media previews, testing tools, uptime monitors and code libraries such as curl and Python requests.
How do I tell a real Googlebot from a fake one?
Run a reverse DNS lookup on the IP address. A real Googlebot resolves to a Google domain. So the string alone is not proof.
Why does every string start with Mozilla?
It is a habit from the 1990s. Early sites sent the best pages to Mozilla, which was Netscape. So other browsers copied the word.
Why do Edge and Opera say Chrome?
They run on the Blink engine, like Chrome. So their strings carry the Chrome name too. The parser checks their own names first.
Why does Chrome on iOS say Safari?
Apple makes every iOS browser use WebKit. So the string looks like Safari, with a small mark for Chrome.
What is a reduced user agent?
It is a shorter string with less detail. Chrome shows zeros for the minor version, and it freezes the system and device details.
Why does my Android model show as K?
Chrome hides the model on purpose to protect privacy. So the string shows a single letter instead.
Can it tell Windows 10 from Windows 11?
No. Both say NT 10.0 in the string. So the tool says Windows 10 or 11.
Why does my iPad look like a Mac?
Safari on an iPad can ask for the desktop site. Then it sends a Mac string.
What are Client Hints?
They are a newer way to share browser facts. Chrome and Edge send short values for the brand, the platform and the device. The tool lists them for your own browser.
Why are there no Client Hints in my browser?
Safari and Firefox do not offer them yet. So only the User-Agent string is available there.
Does it show the device model?
It shows the model for many Android phones and tablets, such as a Pixel or a Galaxy. It shows iPhone and iPad for Apple devices.
What does the CPU field show?
It shows x64, ARM64 or similar when the string names a processor. Many strings do not, so the field can stay empty.
What are the tokens?
They are the pieces of the string. The tool labels each one as a legacy token, an engine, a browser, a system, a CPU or a device.
Can I copy the result?
Yes. Press Copy as JSON for one string, or Copy as CSV for many.
Can I use it on a server log?
Yes. Paste the user agent column, one string per line. Then read the table and the counts.
Can I block traffic by user agent?
You can, but it is weak. A bad actor changes the string in a second. So block by behaviour and IP when you can.
Should I rely on the user agent in my code?
Rarely. Feature detection is safer, because it tests what a browser can really do.
Does it work on a phone?
Yes. The panels stack and the cards fit a narrow screen. So you can check a string on the go.
Handy Companions For Technical Checks
Parsing is one step. These three tools help with the rest.
HTTP Header Checker
Read the headers that any page sends back.
Open tool →What Is My IP
See your public IP address in one click.
Open tool →Robots.txt Validator
Check the rules that tell crawlers where to go.
Open tool →
Ready To Parse A String?
Paste a string, or press Use my browser, and read the result. The user agent parser is free, needs no account, and keeps every string on your device.