./prontouso.com

SEO & WEB TOOLS

User-Agent Parser

Paste a User-Agent string to see the browser, operating system, rendering engine, and device type it describes.

Tool statusRuns in your browser
Preview

Results

Browser
N/A
Browser version
N/A
Operating system
N/A
OS version
N/A
Rendering engine
N/A
Device type
N/A

Paste a User-Agent string.

How it works

  1. Enter your input

    Fill in the values, paste your text, or upload the file this tool works with.

  2. See results instantly

    Most tools update live as you type; a few use a single button. Either way, the result appears right on this page.

  3. Use your results

    Copy, download, or share what the tool produces — you're always in control of the output.

Privacy and processing — Runs locally in your browser. This tool does not upload your input.

What is User-Agent Parser?

Paste a User-Agent string to see the browser, operating system, rendering engine, and device type it describes.

UNDERSTAND THE TOOL

How to read a User-Agent string

How detection works

The string is matched against common patterns used by major browsers and operating systems. Because User-Agent strings can be spoofed or unusual, detection is a best-effort heuristic, not a guarantee.

Common uses

  • Debug a browser-specific issue from a support ticket or server log.
  • Check what your own browser sends by using the "Use my browser" button.

What gets detected

  • Browser name and version (Chrome, Firefox, Safari, Edge, Opera, Samsung Internet, Internet Explorer)
  • Operating system and version (Windows, macOS, iOS, Android, Chrome OS, Linux)
  • Rendering engine (Blink, Gecko, WebKit, Trident) and device type (mobile, tablet, desktop)

Calculation notes

All parsing runs in your browser; the string you paste is never sent anywhere.

Frequently Asked Questions

Can a User-Agent string be faked?

Yes — browsers and tools can freely set any User-Agent string, so this is informational rather than a security check.

Why does it say "Unknown" for some fields?

The string didn't match any of the common patterns this tool recognizes — this can happen for bots, unusual clients, or heavily modified strings.

Why might the detected browser be wrong?

Some browsers include other browsers' names in their User-Agent string for compatibility (e.g. Edge includes "Chrome"), so detection order matters and unusual builds can still be misread.

What happens with an unknown browser?

The parser returns Unknown for browser, OS, or engine parts it cannot match instead of guessing beyond its patterns.

Related Tools