Random user agent generator
Real, current user agents for Chrome 154, Edge 154 and Firefox 156 on Windows, macOS, Linux and Android, each with the Client Hints the same browser sends alongside it.
How these are generated
Each entry is a browser, a platform and a version drawn at random, turned into the exact string that browser sends: Chrome's and Edge's frozen platform tokens and .0.0.0 version, Firefox's rv: and Gecko/20100101. For Chrome and Edge, the Sec-CH-UA brand list is computed with Chromium's own algorithm, the same one on the Chrome user agent page. Every combination this page can produce passes the consistency checks of the user agent checker; the site's tests generate a few hundred and verify each one.
The list is made in your browser and never sent anywhere. Versions: Chrome 154 (Chromium Dash), Edge 154 (Microsoft), Firefox 156 (Mozilla).
What a user agent cannot change
A User-Agent header describes a browser; it does not turn a client into one. Servers compare it with things it cannot touch: the TLS and HTTP/2 handshake, the header order, and, once a page runs JavaScript, the engine's own features and the values in workers. That is why the same string from an HTTP library and from a real Chrome gets different treatment, and why a browser that only rewrites the header keeps its real version everywhere else.
FAQ
What is a random user agent?
A User-Agent string picked at random from those real browsers send, typically to make automated requests look like they come from different people's browsers. The ones here are the exact strings current Chrome, Edge and Firefox send on each platform, not made-up combinations.
Why do the Chrome and Edge entries come with extra headers?
Because a real Chrome or Edge never sends its User-Agent alone: every request also carries Sec-CH-UA, Sec-CH-UA-Mobile and Sec-CH-UA-Platform, and their values follow from the version and the platform. A Chrome User-Agent with no Client Hints, or with the brand list of another version, is something a server can spot at once. Firefox sends no Client Hints.
Will rotating user agents stop my scraper from being blocked?
Rarely on its own. The User-Agent is one line of many: the TLS handshake of an HTTP library does not match any browser (see the JA4 fingerprint checker), and a real browser whose User-Agent was changed still reports its true version through Client Hints, workers and its engine (see what is my user agent). A different browser identity on every request is also unlike any real visitor.
Where do the versions come from?
From each vendor's own release feed, checked every six hours: Chromium Dash for Chrome, Microsoft's Edge update feed, and Mozilla's product details for Firefox. Older versions (if you choose them) are the current one minus one or two, because real browsers lag a little behind a release.
Why is Safari not included?
Safari's version follows Apple's operating system releases and has no public, machine-readable release feed, so any Safari string here would be a guess. The same goes for mobile Firefox, whose Android version token we have not verified.
Related free tools
Chrome user agent strings
The latest Chrome user agents and Sec-CH-UA headers, and a generator for any version.
What is my user agent?
Your User-Agent and Client Hints, and whether they agree with each other.
JA4 fingerprint checker
Your TLS and HTTP/2 fingerprints next to Chrome's and common HTTP clients'.
What browser am I using?
Your browser and version, and whether it is up to date.
Clearcote puts this into practice
An open-source Chromium with fingerprint control compiled into the engine. A drop-in for Playwright & Puppeteer.
Free for one browser with GitHub. No card.