developer validator

User-Agent Parser

Parse browser, OS, device, and CPU info from user-agent strings locally.

Results

Paste input and validate locally.
Status
Ready when you validate.
Details
Ready when you validate.
Browser
Ready when you validate.
OS
Ready when you validate.
Device
Ready when you validate.
CPU
Ready when you validate.

Rules & checks

Uses ua-parser-js client-side.

No network calls; nothing is uploaded.

Returns parsed browser/OS/device/CPU fields when available.

When to use it

  • Debug UA-related bugs or feature flags
  • Analyze logs quickly without external services
  • QA device targeting or A/B tests

Tips

  • Differentiate bot UAs (they often include 'bot' or specific vendor strings)
  • Treat UA parsing as best-effort; use feature detection when possible

Examples

Desktop Chrome

  • Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36 -> Chrome, macOS

Mobile Safari

  • Mozilla/5.0 (iPhone; CPU iPhone OS 16_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.2 Mobile/15E148 Safari/604.1 -> Safari, iOS, iPhone

FAQs

Is anything uploaded?
No. Parsing is local and clears on refresh.
Are results authoritative?
UA strings can be spoofed; treat outputs as hints, not proof.

Related validators

Best-effort parsing; user-agents can be spoofed or malformed.