User-Agent Parser
Parse User-Agent strings into browser, OS, device, and bot verdicts. Identify crawlers vs customers in logs — local parsing, free, no signup.
How to Use the User-Agent Parser
Similar Tools You Might Need
See allCron Expression Parser
Parse cron expressions into human-readable descriptions. Includes common presets for quick reference. Presets plus plain-English schedules prevent 3am surprises — local parsing, free, no signup.
Code to cURL Parser
Parse curl commands into method, URL, headers, and body parts for debugging. Dissect a failing Stripe call field by field — local parsing, free, no signup.
URL Parser
Parse any URL into its components — protocol, hostname, path, query parameters, hash, and more with copy-to-clipboard. Host, path, query, and fragment split with decoding — debug redirect chains precisely. Runs locally, free, no signup.
SQL to CSV Converter
Parse SQL INSERT statements back into CSV rows — quoted strings unescaped, NULLs emptied, multi-statement appends. Round-trip database dumps back to spreadsheets — local parsing, free, no signup.
Video Transcript Formatter
Restructure raw video transcript logs into scripts, articles, or outlines with AI — paste the dump, pick a format. YouTubers convert a 20-minute video log into a blog post in one pass — 1 credit per cleanup.
Frequently Asked Questions
Bot or human?
Known crawler tokens (Googlebot, bingbot) plus headless markers flag automation; mainstream Chrome/Safari strings suggest humans. Spoofable — treat as hint, not proof.
What parses out?
Browser family and version, OS and version, device class (desktop/mobile/tablet), and engine. Each field lists separately for log pipelines.
Mobile detection?
Mobile/tablet tokens plus Android/iOS versions identify handhelds. Serve responsive variants on device class, never on exact versions.
Are strings uploaded?
No — parsing runs locally in your browser. Nothing leaves your device.
What exactly does the output contain?
Two lines only: Browser family plus version, and OS as the first parenthesized token. Detection order is Edge (Edg/) first, then Firefox, Chrome, Safari-only-if-not-Chrome, else Unknown; versions parse from Browser/x.y tokens. 4 presets ship (Chrome and Firefox desktop, Safari iOS, Chrome Android) defaulting to a Chrome 120 string on Mac OS X 10_15_7.
Related Developer Tools
Web Inspector & HTTP Tools
Browser device info, user-agent parser, HTTP status codes reference, MIME types lookup, Basic Auth header generator, Open Graph meta tags generator, and keycode inspector.
Random User-Agent Generator
Generate random browser user-agent strings from a curated list covering Chrome, Firefox, Safari, Edge, and mobile browsers. Free to start with no signup.
Last updated October 2026