User-Agent String Builder
How it works
Not every browser/OS/device combination corresponds to a real browser — Safari is Apple's own WebKit bundled with its own operating systems, not something Apple ships for Windows, Android or Linux, and this tool's Edge only models Windows. Selecting one of those combinations shows an error naming exactly why, rather than a fabricated string.
Frequently asked questions
Are these real, currently-in-use User-Agent strings?
They are illustrative, current-as-of-writing example strings, not a live database. Real User-Agent strings change with every browser and OS release, so treat what this tool builds as a realistic TEMPLATE for testing — useful for simulating a given browser/OS/device shape — not a guarantee of matching any exact live version.
Why are some combinations rejected instead of just building something?
Safari doesn't ship on Windows, Android or Linux as a distinct real browser, and this tool's Edge only models Windows. Fabricating a string for a combination that doesn't exist in the real world would be actively misleading, so those combinations throw a clear error naming why instead.
How does this relate to the User-Agent Parser?
The User-Agent Parser reads a real UA string apart into browser, version, OS and device type. This tool runs the other direction — it builds a plausible one, useful for testing a client that needs to send a particular User-Agent, like simulating a mobile client in an API request.