User Agent String Generator

Pick a browser, OS, and version, get back the matching User-Agent string. Useful for testing how your application handles different clients (server-rendered logic, analytics tagging, conditional UI) and for setting curl / wget / Postman requests to look like a real browser. Always use real UAs ethically — don’t spoof to evade rate limits or terms of service.

Common bot User-Agents

How to use the User Agent String Generator

Pick a browser, OS, and version. The version dropdown updates based on the browser/OS combo. Generate gives you one string; Random rolls a plausible combination. The bot table below lists well-known crawler UAs (Googlebot, GPTBot, ClaudeBot, etc.) for reference — useful when configuring robots.txt rules or analytics filters.

About User Agent String Generator

The User-Agent string is set by your browser (or any HTTP client) and sent with every request. Servers use it to make decisions — serve a mobile-optimised page, log analytics, decide whether to apply a rate limit, identify scrapers. For most testing scenarios, you want a real-looking UA so the server treats your test request like a normal user. Hand-typing them is error-prone and gets stale (UAs include browser version, OS version, and engine version that update weekly).

This generator emits real UAs from recent stable browser releases. It’s useful for: (1) configuring scripts that need to look like a browser (curl, wget, Postman); (2) testing your analytics or server-side device detection; (3) populating test data when seeding a log analyzer.

Use responsibly. Sites have legitimate reasons to identify and rate-limit non-browser traffic. Spoofing to evade rate limits or scrape protected data violates most sites’ terms of service.

Common use cases

  • Testing server-side device detection — confirm your mobile rules trigger for mobile UAs.
  • curl / wget headers — add a realistic --user-agent when scripting against APIs that block bare requests.
  • Analytics seeding — populate your log analyzer with sample UAs across the browser distribution.
  • robots.txt and rate limit verification — confirm your bot policy treats known bots correctly.

Frequently asked questions

Are these the latest versions?
They're recent-stable versions at the time of update. Modern browsers do "evergreen" updates so the major versions go stale quickly \xE2\x80\x94 use these as a starting point, then bump the version numbers if needed.

Should I use these to scrape?
For low-volume, public-data scraping that respects the site's robots.txt and rate limits, a real UA is courteous. For high-volume or terms-of-service-violating scraping, no UA in the world makes that ethical.

What's the difference between Edge and Chrome UA?
Both include "Chrome/" because Edge is Chromium-based. Edge adds an "Edg/" token at the end so servers can distinguish.