Tool
User Agent
User Agent
Analyze any User-Agent string to identify device class, OS, browser, and engine in seconds. This tool is designed for QA, ops, and support teams who need quick, reliable device context from logs, tickets, or ad calls. Paste a UA and get a clean summary plus a structured JSON output you can copy or share. It runs fully in-browser for fast results and privacy-friendly inspection.
Paste a UA string to see device class, OS, browser, and engine at a glance.
User Agent Analyzer
Paste a UA to see device, OS, and browser.Detection runs locally in your browser using UAParser.js. No requests are sent.
Parsing notes
- No user agent provided.
- Browser not detected.
- OS not detected.
- Device type defaults to desktop.
Try a sample user agent:
Structured result (JSON)
{
"timestamp": "—",
"browser": {},
"engine": {},
"os": {},
"device": {},
"cpu": {},
"userAgent": ""
}How it works
This tool parses a User-Agent string into readable, structured components so you can quickly understand device class, OS, browser, and rendering engine.
Use it to decode user-agent strings from logs or SDKs and confirm device targeting quickly.
What you can do with it
- Useful for debugging UA-specific bugs in rendering or analytics.
- Highlights device class like CTV, tablet, phone, or desktop.
- Keeps a clean structured output for sharing.
Common tasks
- Identify device types during QA checks.
- Compare a few UA strings side-by-side.
- Confirm browser versions reported by clients.
Quick steps
- Paste a User-Agent string in the input box.
- Review the key facts for device class, OS, and browser.
- Copy the structured JSON if you need raw details.
Before you start
- Paste a UA string from logs, SDKs, or network calls.
- Load an example to see the format quickly.
What you get
- Key facts for device class, OS, browser, engine, and bot signal.
- Structured JSON output for deeper inspection.
Common pitfalls
- Some custom UA strings are incomplete.
- Bots or crawlers can mask device info.
Tips for best results
- Paste raw input so the tool can apply formatting consistently.
- If output looks wrong, validate the input for missing commas or tags.
- Use the example buttons above to sanity-check formatting and behavior.
Accuracy & limitations
- Outputs are deterministic and based only on the input you provide.
- When official specs exist, the tool favors strict parsing over guesses.
- URL-based tools can vary by region, cache, or upstream availability.
- Always validate critical outputs in your production systems before launch.
Trust & quality
- Local parsing with clear source attribution.
- Surfaces confidence gaps when data is missing.
Who it is for
- QA and support teams validating outputs before launch.
- Analysts and operators who need fast clarity on raw data.
- Engineers and technical writers documenting system behavior.
When to use this tool
- You need a quick answer without scripting or a full IDE.
- You want a repeatable, shareable output for teammates.
- You are troubleshooting inconsistent or malformed input.
Quick checklist
- Input is complete and copied in full.
- Output matches expectations and no errors are shown.
- Share or export the result if you need to keep a record.
Frequently asked questions
Is it free to use?
Yes. Core tools are free and accessible without signup.
Does it upload my data?
This tool runs locally in your browser. Data you paste or files you upload stay on your device and are not uploaded.
What if I spot a bug?
Please reach out via the Contact page with a reproduction example.
Why are device vendor or model missing?
Many UA strings do not include vendor/model details, especially on desktop.
Is the live browser UA shared?
No. Parsing happens locally in your browser.
Why does the UA look reduced?
Some browsers now reduce UA strings in favor of UA-CH.
Helpful links
Standards & references
Official specs that inform how this tool interprets data.