Random User Agent Generator

How to use

1. 1️⃣
   Choose your options above
2. 2️⃣
   Click Generate
3. 3️⃣
   Copy your result

Detailed instructions

1. Set the Count field to the number of UA strings you need — start with 10-20 for a varied test sample.
2. Choose a Device Type from the dropdown to filter results to desktop browsers, mobile, tablet, or bot crawlers.
3. Click Generate to produce the list of User-Agent strings matching your criteria.
4. Copy individual strings or the full list and paste them into your test fixtures, HTTP client config, or seed data file.
5. Re-generate as many times as needed — each run produces a fresh randomised set within the selected device category.

Use Cases

• •Seeding Jest or pytest fixtures for a ua-parser-js or ua-parser unit test suite covering 50+ device combinations
• •Rotating UA strings in a Playwright or Puppeteer scraper to test detection-avoidance logic before hitting production targets
• •Verifying that Express middleware returns the correct responsive layout when server-side rendering for mobile vs. desktop UA strings
• •Testing WAF rules in AWS or Cloudflare to confirm bot crawler signatures are flagged while real browser UAs pass through
• •Populating a staging analytics pipeline with mixed desktop, mobile, and bot traffic to validate session-classification logic

Tips

• →Generate separate batches per device type and combine them in a weighted ratio (e.g. 60/30/10 desktop/mobile/bot) to mirror realistic traffic.
• →When testing a UA parser, deliberately include bot strings alongside browser strings — many parsers misclassify obscure crawler UAs as desktop browsers.
• →Paste generated strings into https://developers.whatismybrowser.com to verify your parser's output matches the expected classification.
• →For scraper rotation testing, generate at least 50 unique strings — repeating the same handful of UAs too quickly is itself a detectable signal.
• →If you're testing Googlebot-specific server behaviour, filter to Bot type and verify your server returns the same content it would to a standard browser (cloaking violates Google's guidelines).
• →Freeze a generated set in your test fixtures rather than regenerating on every test run — stable fixtures make failures reproducible and diffs readable.

FAQ