User Agent Parser - Decode Browser, OS & Device Info Online
Parse and analyze user agent strings to extract browser, operating system, device type, rendering engine, and CPU architecture. Batch parsing with distribution stats — 100% client-side, no data sent to server.
Sample User Agents
Enter a user agent string to see parsed results
Frequently Asked Questions
What is a user agent string and what does it contain?
A user agent string is a text identifier that web browsers and other HTTP clients send to servers with every request via the User-Agent HTTP header. It typically contains encoded information about the browser name and version, the operating system, the device type, and the rendering engine. For example, Chrome on Windows might send: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36. Despite appearing complex, each part conveys specific information about the client software and hardware.
How do I use this user agent parser?
Open the tool and click Detect My User Agent to see your current browser's user agent parsed instantly. Alternatively, paste any user agent string into the input field for real-time parsing. View results as structured cards showing browser, OS, device type, rendering engine, and CPU architecture, or switch to JSON view for raw data. Use the Batch tab to parse multiple user agent strings at once (one per line) and see distribution statistics. Click Copy to copy parsed results to your clipboard.
Is my user agent data sent to a server?
No. This tool is 100% client-side and uses the ua-parser-js JavaScript library running entirely in your browser. All parsing happens on your device. No user agent strings, parsed results, or any other data is ever transmitted to a server. This is especially important when analyzing access logs that may contain internal or sensitive traffic data. The tool works fully offline after the initial page load.
What is the difference between user agent strings and Client Hints?
Traditional user agent strings are a single long text field that encodes all client information in a semi-structured format. User-Agent Client Hints are a modern replacement proposed by the W3C, where client information is sent via structured HTTP headers (Sec-CH-UA, Sec-CH-UA-Platform, etc.) and a JavaScript API (navigator.userAgentData). Client Hints provide cleaner, more structured data and give users more control over what information is shared. Chrome and Edge support Client Hints, while Firefox and Safari have limited support. This tool shows both traditional UA parsing and Client Hints data when available.
Can I parse multiple user agent strings at once?
Yes. Switch to the Batch tab and paste multiple user agent strings, one per line. Click Parse All to process them simultaneously. The tool displays results for each UA string and generates a summary showing the distribution of browsers, operating systems, and device types. You can export the results as JSON or CSV for further analysis. This is particularly useful for analyzing server access logs or analytics data.
Why does my user agent string say Mozilla when I am using Chrome?
This is a historical artifact of browser compatibility. In the early web, servers would send different content to different browsers. When new browsers launched, they included Mozilla (and often like Gecko, Safari, etc.) in their user agent strings so that servers would not block them or send degraded content. Today, nearly every browser's user agent string starts with Mozilla/5.0 regardless of the actual browser. The ua-parser-js library used by this tool correctly identifies the actual browser despite these misleading prefixes.
What device types can be detected from a user agent string?
This tool can identify the following device types: desktop (standard computers), mobile (smartphones), tablet (iPad, Android tablets), smart TV (web-connected televisions), console (gaming consoles like PlayStation, Xbox), wearable (smartwatches), and embedded (IoT devices). It also detects bots and crawlers (Googlebot, Bingbot, GPTBot, etc.). Note that desktop browsers typically do not include device type in their user agent string, so desktop is inferred when no mobile/tablet/other indicator is present.
Code Examples
// User agent parsing in the browser using ua-parser-js
import UAParser from 'ua-parser-js';
function parseUserAgent(uaString) {
const parser = new UAParser(uaString);
return {
browser: parser.getBrowser(),
engine: parser.getEngine(),
os: parser.getOS(),
device: parser.getDevice(),
cpu: parser.getCPU(),
};
}
// Parse current browser's user agent
const result = parseUserAgent(navigator.userAgent);
console.log('Browser:', result.browser.name, result.browser.version);
console.log('OS:', result.os.name, result.os.version);
console.log('Device:', result.device.type || 'desktop');
// Client Hints API (Chromium browsers)
if (navigator.userAgentData) {
const hints = await navigator.userAgentData.getHighEntropyValues(
['platformVersion', 'architecture', 'model']
);
console.log('Platform:', hints.platform, hints.platformVersion);
}