Examples and patterns

User agent string examples

These examples show the shape of common desktop and mobile user agents. They are useful for QA, parser tests, documentation, and explaining why two browsers can look similar at first glance.

Common examples

Chrome on Windows

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36

This is a classic Chromium-style desktop pattern with AppleWebKit and Safari compatibility tokens.

Safari on iPhone

Mozilla/5.0 (iPhone; CPU iPhone OS 18_4 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.4 Mobile/15E148 Safari/604.1

Safari on iPhone usually includes Version/x.y, a Mobile/ token, and a Safari marker.

Firefox on desktop

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:147.0) Gecko/20100101 Firefox/147.0

Firefox examples usually pair Gecko/20100101 with a browser-specific Firefox/ token.

Microsoft Edge on Windows

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Safari/537.36 Edg/145.0.0.0

Edge usually looks very close to Chrome until the trailing Edg/ token appears.

Chrome on Android with reduced tokens

Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/145.0.0.0 Mobile Safari/537.36

Chromium-based Android examples often expose reduced platform detail. That is expected browser behavior, not necessarily a generator error.

What to compare in examples

  • Browser-specific tokens such as Chrome/, Firefox/, Version/, or Edg/.
  • Engine-family markers such as AppleWebKit or Gecko.
  • Platform hints such as Windows NT, Android, or iPhone OS.
  • Device markers such as Mobile and tablet-friendly Android patterns without Mobile.

What to watch out for

  • Many browsers deliberately look similar for compatibility reasons.
  • Patch versions and platform details may be frozen or reduced.
  • An extension can alter the presented string without changing the real engine.
  • Server-side detection may still combine user agents with Client Hints or other request signals.

Generate a larger sample set

Use the bulk generator if you need fixtures, demos, CSV exports, or broader browser coverage.

Generate examples

Understand each token

Read the main parsing guide to see why examples contain so many compatibility markers.

Read the guide

See mobile and desktop differences

Compare how device-class markers change between desktop browsers, phones, and tablets.

Compare mobile vs desktop

Understand the broader context

Read the overview if you want the definition, the common use cases, and the limits of user agents first.

Open the overview
Why do so many examples still start with Mozilla/5.0?

Because that compatibility token is still preserved by modern browsers even though it no longer means the browser is Mozilla in the old historical sense.

Why does a Chrome example still include Safari tokens?

Because Chromium browsers keep WebKit and Safari compatibility markers for legacy browser sniffing logic.

Can I generate more examples automatically?

Yes. The bulk generator on this site can create representative sample strings for multiple browser and device combinations.