Runs locally in your browser. Nothing you enter is uploaded to our servers.
Result will appear here
Tips for User-Agent parsing
Parsing is heuristic — spoofed UAs are common.
Do not rely on UA alone for security or feature detection.
Prefer modern Client Hints when available in your own apps.
Bots often embed keywords like bot, crawler, or spider.
Clear the field before sharing screenshots with sensitive context.
What a User-Agent string is claiming
Processing stays in your browser — your input is not uploaded to our servers.
The header is a free-form token that browsers and bots send. This parser splits it into browser, engine, and OS guesses — not a fingerprinting service.
Spoofed UAs are common. Treat the parse as what the string says, not who is definitely on the other end.
Parse a User-Agent
Paste a UA string
Copy from DevTools, logs, or the My IP page. Empty input will not invent a client.
Read the guessed family
Engine versus browser names are easy to mix up; check both fields.
Do not block solely on UA
Feature detection and auth beat UA allowlists that break every Chrome update.
User-Agent parser FAQ
Does this identify a person?
No. Many users share the same UA. It is a coarse client hint.
Will it parse the current browser automatically?
Paste navigator.userAgent yourself or copy it from My IP. The parser does not silently profile you beyond what you paste.
Is the string uploaded?
No. Parsing is local.