Skip to content
Kordu Tools Kordu Tools

User Agent Parser

Runs in browser

Parse any user agent string to detect browser, OS, device type, and rendering engine.

Last updated 08 Apr 2026

Paste any user agent string — or use your own browser's UA automatically — to instantly detect browser name and version, operating system, device type (desktop, mobile, tablet, bot), and rendering engine. Runs entirely in your browser — nothing is uploaded.

User agent string

BrowserUnknown
Operating systemUnknown
Device typeDesktop
Rendering engineUnknown
Bot / crawlerNo
Loading rating…

How to use

  1. 1

    Paste a user agent string

    Paste any user agent string from server logs, analytics, or browser dev tools into the input. Alternatively, click 'Use my browser' to analyse your own browser's UA.

  2. 2

    Read the parsed results

    Browser name and version, OS, device type (desktop/mobile/tablet/bot), and rendering engine are shown instantly.

Frequently asked questions

What is a user agent string?
A user agent string is a text identifier sent by browsers and HTTP clients in the User-Agent header with every request. It describes the software making the request — browser, version, OS, and device type. Example: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36'.
Where do I find a user agent string in server logs?
In Apache and Nginx access logs, the user agent appears as the last quoted string. In Chrome DevTools, go to Network, click any request, and look for the User-Agent request header. In code, it's available as navigator.userAgent in JavaScript or the User-Agent header in HTTP requests.
How does bot detection work?
Bots and crawlers typically identify themselves in their user agent string with keywords like 'bot', 'crawler', 'spider', or tool names like 'Scrapy', 'Selenium', or 'Headless'. Some bots spoof browser UAs — this tool only detects bots that self-identify.
Why does Chrome on iOS show as 'Chrome (iOS)'?
Apple requires all iOS browsers to use the WebKit rendering engine. Chrome on iOS uses the CriOS token in its UA string rather than the standard Chrome token, and renders with WebKit rather than Blink.
Is my user agent data sent anywhere?
No. All parsing happens in your browser using JavaScript. Your user agent string is never transmitted to any server.

The Kordu User Agent Parser decodes the User-Agent HTTP header string into

human-readable components. It identifies browser name and version (Chrome,

Firefox, Safari, Edge, Opera, Samsung Browser, and more), operating system

and version (Windows, macOS, Linux, iOS, Android, ChromeOS), device type

(desktop, mobile, tablet, or bot), and rendering engine (Blink, WebKit,

Gecko, Trident).

Click "Use my browser" to populate the input with your own browser's user

agent string, or paste any UA string from server logs, analytics, or

debugging sessions.

Common uses: debugging browser-specific issues, analysing user agent strings

from server logs, testing responsive design for specific device types, and

identifying bot traffic in access logs.

All parsing runs client-side in your browser. Nothing is uploaded or stored.

Related tools