Explore our collection of 150+ developer tools, PDF editors, and image converters. Everything runs locally in your browser.
Ubify Core Engineering Team
SOFTWARE ENGINEERS & SYSTEMS ARCHITECTS
About This Tool
Every HTTP web request transmits client information identifying the browser vendor, rendering engine, and host operating system. This inspection tool decodes raw User-Agent header strings and evaluates modern User-Agent Client Hints (`navigator.userAgentData`), presenting device architecture, browser rendering engine, and platform release details in a structured visual dashboard.
### Header Breakdown & Client Hints
Modern browsers are transitioning from bloated legacy User-Agent strings to structured Client Hints: - **Browser & Version:** Identifies the software family (Chrome, Firefox, Safari, Edge) and major release numbers. - **Rendering Engine:** Detects layout cores including Blink (Chromium), Gecko (Mozilla), and WebKit (Apple). - **Operating System & Architecture:** Parses Windows NT versions, macOS Darwin kernels, Linux distributions, Android, and iOS builds along with CPU architectures (x86_64, ARM64). - **User-Agent Client Hints (`Sec-CH-UA`):** Evaluates brand arrays, mobile flags, and platform strings provided by modern Chromium-based browsers.
### Worked Inspection Example
Analyzing a typical desktop browser session: - **Raw User-Agent String:** `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36` - **Parsed Browser:** Chrome 128.0.0.0 - **Engine:** Blink / WebKit 537.36 - **Operating System:** Windows 10 / 11 64-bit (`Win64; x64`) - **Device Category:** Desktop / Workstation - **Mobile Flag:** False
### In-Browser Privacy Protection
Header analysis and Client Hint extraction run entirely within your browser session via local JavaScript APIs. Your system identifiers, hardware specs, and IP headers are never logged or stored on remote servers.
How to Use
- 1
Load the page to automatically detect and parse your active browser User-Agent string.
- 2
Paste an alternative User-Agent string into the input box to inspect external client devices or web crawlers.
- 3
Review the structured breakdown cards showing Browser, Engine, OS Platform, and Architecture.
- 4
Copy individual parsed parameters or the formatted JSON summary for debugging.
Frequently Asked Questions
Why do modern Chrome User-Agent strings still contain Mozilla/5.0 and Safari/537.36?
Web browsers retain historical tokens (like Mozilla/5.0 and Safari/537.36) for backward compatibility with legacy web servers that gate content based on vintage User-Agent string patterns.
What are User-Agent Client Hints and how do they replace traditional User-Agents?
Client Hints (Sec-CH-UA) divide browser data into discrete HTTP request headers, sending minimal high-entropy details by default to reduce passive device fingerprinting across the web.
Does this tool transmit my browser details to external analytics trackers?
No. All User-Agent string parsing occurs 100% locally in your client browser runtime. No hardware profiles or tracking cookies are sent across the network.