# User-Agent parser — no upload

> Parse a User-Agent string into browser, engine, OS, and device in your browser. Nothing is uploaded — the string stays in the tab.

Paste a User-Agent string to break it into browser, rendering engine, operating system, and device type. Parsing happens in the browser, so nothing is sent anywhere.

User-Agent strings are notoriously convoluted, and reading one by eye to find the actual browser and OS is a chore. Parsing it into clean fields helps when debugging device-specific bugs or interpreting server logs.

For other request details, see the HTTP header reference; for network-level parsing, the IP converter and CIDR calculator.

## How to

1. **Paste a UA string.** Paste the User-Agent from a log or request.
2. **Parse.** See the browser, engine, OS, and device.
3. **Use it.** Interpret analytics or debug device-specific issues.

## FAQ

### Why are User-Agent strings so messy?

For historical compatibility reasons every browser pretends to be several others, so the raw string is cluttered. Parsing extracts the parts that actually matter.

### Can it identify mobile vs desktop?

Yes. It reports device type and OS, so you can tell a mobile request from a desktop one when debugging or reading logs.

### Is the string uploaded?

No. Parsing is local, so the UA string stays in the tab.


## Related tools

- [HTTP headers](https://www.safepaper.app/dev/http-headers)
- [IPv4 / IPv6](https://www.safepaper.app/dev/ip-convert)
- [CIDR calculator](https://www.safepaper.app/dev/cidr)
- [URL parser](https://www.safepaper.app/dev/url-parser)

---

Canonical HTML: https://www.safepaper.app/dev/user-agent
Markdown: https://www.safepaper.app/dev/user-agent.md

There is no upload endpoint — your files are processed in this browser tab. Open your network tab and check.