Random User-Agent
Pick a random User-Agent string from a small curated pool.
Overview
The Random User-Agent generator picks one User-Agent string from a small curated pool of recent browser, mobile and bot signatures. It is useful when you need a believable UA for a quick mock, a test fixture or a script exploring how a site responds to different clients — without scraping any live UA database.
The generator is aimed at developers building HTTP test fixtures, QA engineers replaying traffic with varied UAs, security researchers checking content-negotiation behaviour and educators teaching how UA sniffing works. Long-tail searches like "random user-agent string generator", "latest chrome user agent for testing" and "common mobile user agents list" all resolve here.
How it works
The pool is a hand-maintained list of representative UAs across the major segments: Chrome, Firefox and Safari on macOS and Windows; Chrome and Safari on iOS and Android; common bot UAs like Googlebot and Bingbot; and a few historical UAs for testing legacy code paths. Each entry is sourced from public documentation rather than scraping live traffic, so it is safe to publish and reuse.
On each click the tool draws a uniformly random entry using the OS cryptographic random source. You can filter by category (desktop, mobile, bot) to bias the draw. Because the pool is intentionally small (a few dozen entries), the values are easy to audit and predictable enough for test fixtures, while still covering the diversity needed for most use cases.
Examples
Desktop → Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36
Mobile → Mozilla/5.0 (iPhone; CPU iPhone OS 17_4 like Mac OS X) AppleWebKit/605.1.15 ...
Bot → Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)
Legacy → Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
FAQ
Will the UA pass anti-bot detection?
The strings are syntactically correct and look real, but modern anti-bot stacks fingerprint far more than the UA. Treat this as a starting point, not a bypass.
Are the UAs always up to date?
The pool is hand-maintained and refreshed periodically. It will lag the very latest Chrome major version by a few weeks at most.
Can I add my own UAs?
The pool is baked into the build for audit reasons. Use the output as a starting point and substitute in code if you need a specific custom string.
Why is the pool small?
A small curated pool is easier to audit and produces predictable test fixtures. Mega-pools of millions of UAs add little value for most testing tasks.
Is impersonating a UA legal?
UA strings are public client identification — modifying them is normal and legal for testing. Always respect a site's terms of service when scraping.