Test User-Agent Generator — Dummy UAs for Fixtures

Generate synthetic User-Agent strings for databases, log fixtures and parser tests. Generic browser templates are the default, and a bot and CLI preset and deliberately invalid strings are optional. Not a UA parser, not a “what's my UA” page, not a guide to evading bot detection.

Loading…
How the test User-Agent generator works
Synthetic User-Agent strings built from generic browser templates, for fixtures and parser tests. A bot and CLI preset and deliberately invalid strings are optional. This is not a UA parser or a tool to get past bot detection.

How generation works

Pick a quantity (1 to 100), the kind, the device class, valid or invalid rows, the format, the Client Hints export and the order. The list is rebuilt each time you change an option. Copy everything or download it as JSON, CSV, SQL or TXT.

Options

Quantity
How many User-Agent strings to generate, from 1 to 100 (10 by default).
Kind
Generic browser templates by default (Chrome 118 to 122, Firefox 120 to 122, Safari 17). The other kinds are common bots and command-line clients, the reduced strings that browser documentation describes, or a custom template of your own.
Device class
Desktop, mobile or tablet strings for the browser kinds. Reduced strings exist for desktop and mobile only. The option is hidden for the bots and CLI preset.
Validity
Valid rows come from the selected kind. Invalid mode writes broken strings on purpose, chosen in Invalid kind, for negative parser tests.
Format
The full User-Agent string, the product token alone (Chrome/121.0.0.0), or an older style with a long comment in parentheses.
Client Hints
When on, the JSON export adds synthetic low-entropy Sec-CH-UA headers that match each browser string. Bots get none. These are not hints read from your browser.
Order
Random draws can repeat, Unique never repeats, and Sequence walks the pool in order. The pools are small: 9 desktop templates, 6 mobile or tablet ones, 7 bots. Unique and Sequence show an error when the quantity is larger.

Examples

Generic desktop browser, the default

Settings

kind=syntheticGeneric, deviceClass=desktop, validity=valid

Sample output

Mozilla/5.0 (Windows NT 10.0; Win64; x64) … Chrome/120.0.0.0 …

Invalid row with an unclosed comment

Settings

validity=invalid, invalidKind=unterminatedComment

Sample output

Mozilla/5.0 (unclosed

Related tools

For IP or MAC fixtures, try the test IP address generator and the test MAC address generator. A JSON table comes from the JSON test data generator.

Test User-Agent FAQ

Fixtures, generic templates and what this tool does not do

Why generic templates by default?

Fixed templates spare you from chasing the latest Chrome release. They also keep the fingerprint of a real colleague's device out of your fixtures.

I searched for a random user agent generator. Is this it?

Yes, if you need dummy User-Agent strings for fixtures and parser tests. It has no advice on getting past anti-bot systems and no presets for in-app browsers of social networks.

I searched for a fake user agent generator. Is this it?

Yes for synthetic strings in fixtures. No for imitating a specific person's browser or getting around access controls.

Is this a user agent parser?

No. This tool writes strings for fixtures. Parsing a User-Agent you paste is a different job, which this page does not do.

Can I bypass bot detection with these strings?

No. Modern bot checks look at TLS, behavior and much more than the User-Agent header. This tool is for fixtures and negative parser tests.

Can I use a {RANDOM} suffix in a custom template?

Yes. Add the literal {RANDOM} token after a prefix, as in MyAgent/{RANDOM}. Each row then gets a different four-character hex suffix while your prefix stays the same.

Dummy names, emails, phone numbers, addresses, dates, IBANs, card numbers and JSON, CSV or SQL rows for fixtures and database seeds. Everything is generated in your browser.