Best use cases
Parser unit tests, import fixtures, allowlist demos, browser-specific screenshots, and synthetic QA scenarios.
Sample data for QA and parser tests
Build a filtered list of syntactically valid user agents from browser-specific templates. The goal here is practical test data that respects current UA reduction rules and real browser families.
Chromium-based mobile rows intentionally use reduced tokens such as Android 10; K, and Safari rows intentionally keep frozen OS tokens. That is expected browser behavior, not a bug in the generator.
| # | Browser | Profile | User agent |
|---|
Parser unit tests, import fixtures, allowlist demos, browser-specific screenshots, and synthetic QA scenarios.
Production security rules, fraud scoring, or anything that requires real user telemetry and high-confidence detection.
Use the checker page if you want to see what your current browser session exposes right now.
Open live checkerModern Chromium browsers reduce parts of the UA string for privacy, and Safari now freezes OS tokens on more platforms. So values like Android 10; K or Mac OS X 10_15_7 can still be correct for current browsers.
Yes. Keep several browser and device checkboxes enabled and the tool will balance the list across the compatible browser and device groups you selected.
Yes. Use Copy for newline-separated strings or export as CSV for spreadsheet-friendly results.