User Agent Generator

Realistic User-Agent strings on demand

A generator produces ready-to-use User-Agent strings for common browsers, operating systems, and known bots. The point is to grab a plausible, correctly formatted string for testing: checking how your site responds to different clients, seeding a request header in a script, or reproducing a device-specific bug.

Legitimate uses

Setting a User-Agent is normal and expected. Automated tests set one so analytics can distinguish them. API clients identify themselves so a server operator can contact them if something misbehaves. QA teams swap strings to verify responsive layouts and server-side device handling.

Example

Chrome on macOS:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)
AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/120.0 Safari/537.36

Googlebot:
Mozilla/5.0 (compatible; Googlebot/2.1;
+http://www.google.com/bot.html)

Keep them current and honest

Version numbers age quickly; a UA claiming a years-old Chrome build stands out and can get flagged. If you are identifying a bot you operate, name it honestly and include a contact URL, the way the major crawlers do, rather than impersonating a real browser. Spoofing a UA to evade blocks or scrape against a site's terms is a different matter and often against those terms. To inspect any string you receive, use the User-Agent parser.

FAQ

Will setting a UA make me look like a real user? Not on its own. Sites also look at behavior, TLS fingerprints, and Client Hints, so the string is only one signal.

Why avoid an outdated version string? It is inconsistent with other modern signals your client sends, which makes it an obvious tell and can trigger blocks.

What should my own bot's UA say? A clear product name, a version, and a URL or email so operators can reach you. Honesty keeps you unblocked.