User-Agent Parser
Instantly decode messy and confusing HTTP User-Agent strings. Extract the exact browser version, operating system, rendering engine, and device type.
How to Use
- If you want to test your own device, click Load My User-Agent into Parser to grab the HTTP header your browser is currently broadcasting.
- If you are analyzing server logs or web traffic, paste the mysterious User-Agent string into the text box and click Parse String.
- The parser will aggressively cross-reference the string against thousands of known hardware and software signatures to extract the exact Browser, OS, CPU Architecture, and Hardware Device type.
Features
Smart Extraction
Cuts through spoofed headers and fake 'Mozilla' tags to find the actual browser engine running underneath.
Hardware Detection
Detects if the user is on a standard Desktop, a Tablet, a Mobile Phone, a Smart TV, or a gaming console.
Instant Parsing
Uses the industry standard `UAParser` algorithm to decode the string in less than a millisecond.
Privacy First
Your server logs are parsed entirely inside your local browser. Nothing is uploaded to our servers.
Why are User-Agent Strings so messy?
If you look at a modern Chrome User-Agent string, it will likely start by saying it is Mozilla, then claim it is AppleWebKit, then pretend it is Safari, before finally admitting it is Chrome. Why do browsers lie?
In the early days of the internet, the Netscape browser (codenamed Mozilla) supported advanced features like HTML frames. Web servers would check the User-Agent, and if it didn't say "Mozilla", they would send back an ugly, text-only version of the website. When Microsoft released Internet Explorer, they wanted the advanced websites too, so they forcefully put "Mozilla" in their User-Agent string to trick the servers.
This started a decades-long war. Every time a new browser was created (Safari, Chrome, Edge), they had to include the names of their competitors in their User-Agent string just to ensure websites wouldn't block them. This historical baggage is why User-Agents are incredibly difficult for humans to read today, making dedicated parsing algorithms absolutely essential.
The Web Server Suite
If you are analyzing network packets and need to parse an IPv4 address, use our IPv4 Subnet Calculator. Need to decode a URL-encoded string from your server logs? Use the URL Encoder/Decoder. Need to format a massive block of unreadable XML data returned by an API? Use the XML Formatter.
Frequently Asked Questions
Why does the device type say 'Desktop / Unknown'?
Unlike mobile phones and tablets (which proudly announce their hardware models like 'iPhone' or 'Galaxy S22'), standard desktop computers (Windows/Mac/Linux) typically hide their specific hardware. If the parser detects a standard Desktop OS, the exact hardware manufacturer remains unknown for privacy reasons.
What is a Rendering Engine?
The Rendering Engine is the actual core software that draws the website on the screen. For example, Google Chrome and Microsoft Edge both use the exact same rendering engine (Blink), while Apple Safari uses WebKit, and Firefox uses Gecko.
Are my server logs sent to a database?
No. We respect your security. The parser utilizes a massive JavaScript dictionary loaded entirely into your web browser. The string evaluation happens securely on your local CPU.
Is it free?
Yes, 100% free with no limits.