User Agent Detector

Detect your browser, operating system, device, and user agent string.

User agent parsing tool

Inspect and parse a user agent string

Paste a user agent string or detect your current browser. Results are parsed locally and shown as helpful hints.

Paste a browser, crawler, app, or API client user agent string.

User agent strings can be spoofed, frozen, reduced, or incomplete.

Detection status

Detected

Chrome on Windows, detected with high confidence.

Parsed summary

Browser: Chrome 122.0.0.0

OS: Windows 10 / 11

Device: desktop

Engine: Blink

Bot hint: None detected

Primary status

Detected

Detection should be treated as a helpful hint.

Browser

Chrome

122.0.0.0

Operating system

Windows

10 / 11

Device type

desktop

Desktop, mobile, tablet, bot, or unknown.

Engine

Blink

Rendering engine estimate.

Bot hint

None detected

Heuristic bot detection.

Confidence

High

Based on matched UA fields.

User agent length

111

Characters in the raw user agent.

Copy raw user agent

Copy the original user agent string for logs, support tickets, or debugging.

Copy parsed summary

Copy readable browser, OS, device, engine, bot, and confidence details.

Privacy note

User agent parsing is designed to happen locally in your browser without external APIs.

Accuracy note

User agents can be spoofed, frozen, reduced, or incomplete. Detection is not perfect.

Debugging note

Useful for HTTP logs, support tickets, analytics, compatibility checks, and bot review.

Browser privacy note

Modern browsers may reduce user-agent detail to limit fingerprinting.

Parsed user agent details

Review browser, OS, device, engine, bot, and raw string details.

Browser details

Chrome 122.0.0.0

Operating system details

Windows 10 / 11

Device details

desktop

Engine details

Blink

Bot / crawler details

None detected

Architecture

64-bit

Platform hints

Windows architecture token present

Raw string details

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36

User agent examples

Click an example to populate the detector.

User agent quick reference

Browser

Application making the request.

Operating system

Platform reported by the UA string.

Device type

Desktop, mobile, tablet, bot, or unknown.

Engine

Rendering engine such as Blink, WebKit, Gecko, or Trident.

Bot detection

Heuristic and not guaranteed.

UA reduction

Modern browsers may limit detail.

Spoofing

User agents can be faked.

Client Hints

Modern alternative for some browser/device info.

Developer guide

Understand user agent strings and their limits

User agent detection helps interpret logs and support cases, but it should not be treated as guaranteed truth.

What is a User Agent Detector?

A User Agent Detector parses a user agent string to estimate the browser, operating system, device type, rendering engine, and crawler status.

What is a user agent string?

A user agent string is text sent by browsers, crawlers, apps, and clients to identify themselves to servers. It appears in HTTP request headers, analytics logs, support tickets, and debugging tools.

When should developers use one?

Use it for debugging browser compatibility issues, reading server logs, investigating support tickets, understanding analytics traffic, identifying bots, testing responsive behaviour, checking mobile versus desktop requests, and reviewing legacy browser traffic.

User agent detection limitations

User agents can be spoofed, reduced, frozen, incomplete, or shared across similar browsers. Bot detection is heuristic, and feature detection is often better for frontend code.

User agent detection vs feature detection

User agent detection guesses browser or device from a string. Feature detection checks whether a browser supports a capability. For frontend compatibility, feature detection is often safer.

Privacy and security

BlinkCalc is designed to parse locally in the browser. User agent strings can reveal browser and device details but are not reliable identity and should not be used as authentication or security controls.

Common user agent mistakes

Assuming user agent strings are always truthful.
Blocking users based only on user agent.
Treating bot detection as perfect.
Using browser detection instead of feature detection.
Failing to account for mobile and tablet edge cases.
Assuming all Chromium browsers are exactly the same.
Ignoring reduced user agent details in modern browsers.

How to use this User Agent Detector

  1. 1Paste a user agent string into the input box.
  2. 2Click Parse or use the current browser detection button.
  3. 3Review the detected browser, OS, device type, engine, and confidence.
  4. 4Copy the parsed summary if needed for debugging or support.
  5. 5Treat results as helpful hints, not guaranteed truth.

Why developers use a User Agent Detector

Debug browser-specific issues.
Interpret HTTP logs.
Identify mobile and desktop traffic.
Investigate crawler requests.
Support compatibility troubleshooting.
Understand analytics anomalies.
Share readable summaries with teams.
Avoid manually decoding long UA strings.

User Agent Detector FAQs

It parses a user agent string and estimates the browser, operating system, device type, rendering engine, and bot status.