EVERYDAY UTILITIES

User Agent Parser

Decode a user-agent string to see the browser, rendering engine, operating system and device type it claims, including bots.

Free, no signup

1 User agent

Processed in your browser. Nothing is uploaded.
THREE SMALL STEPS

How to read a user agent string

  1. 01

    Start with your browser

    Your own user agent is filled in automatically, so you can see what websites receive from you.

  2. 02

    Paste another one

    Paste a user agent from server logs, analytics or a bug report to decode it.

  3. 03

    Read the details

    Browser, engine, operating system and device type appear as you type, with a warning for bots.

BEFORE YOU START

Good to know

A declaration, not proof

Any browser, app or script can send any user agent, so use it for statistics and debugging rather than for security decisions.

Reduced details

Modern browsers share fewer details on purpose, for example by reporting Windows 10 on Windows 11 or an older macOS version.

Decoded locally

The string is decoded in your browser with the open-source Bowser library. Nothing is sent to a server.

QUESTIONS

Frequently asked questions

Can I parse a browser user-agent string from a server log?

Yes. Paste one user-agent string to read its reported browser, operating system and engine. Do not paste an entire log containing private data. User-agent strings can be modified or reduced, so the result is a description of the string, not verified device identity.

What is a user agent?

It is a line of text that browsers and apps send with each request to describe themselves, such as the browser name, its version and the operating system.

Why does Chrome mention Safari and Mozilla?

For historical compatibility, most browsers include the names of older browsers. The parser looks for the most specific name to identify the real one.

Can it detect the exact phone model?

Only when the user agent includes it. Many browsers now hide the device model, so the tool shows the device type instead.