User-Agent Parser
The user-agent parser breaks a browser user-agent string into the parts that matter: browser and version, rendering engine, operating system and device type. Paste any string from a log, or parse your own with one click.
Your result will appear here.
Not sure where to start? Use Load example.
Results update automatically and are calculated on your device. Nothing you type is sent to a server.
Runs in your browser. Processing happens entirely in your browser. Nothing you enter is sent to Delimiter.live.
How to use the User-Agent Parser
- Paste a user-agent string from a log file, or press the button to load your own.
- Read the parsed browser, engine, operating system and device type.
- Paste several strings, one per line, to parse a batch.
Example
Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) … Safari/604.1
Browser: Safari 17.5 Engine: WebKit OS: iOS 17.5 Device: Mobile
Common use cases
- Working out which browser a bug report came from.
- Summarising the platforms present in a server log.
- Checking what your own browser reports before debugging a compatibility issue.
Limitations and things to watch for
- User-agent strings are historically messy — almost every browser still begins with "Mozilla/5.0" for compatibility reasons dating back to the 1990s. Parsing is therefore pattern-based and can misidentify rare or deliberately disguised browsers.
- Browsers are actively reducing the detail in user-agent strings for privacy, so modern versions report less than older ones. Feature detection is a better basis for decisions than user-agent parsing.
- A user-agent string is supplied by the client and can be set to anything. Never rely on it for security.