Device-class comparison

Mobile vs desktop user agents

Mobile and desktop browsers often share the same brand family while exposing different device markers, operating system hints, and compatibility tails. Those differences matter for QA, analytics, and reproduction steps.

Typical comparison

Desktop Chrome

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

Mobile Chrome on Android

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

The obvious change is the Mobile marker, but platform and version details may also be reduced or normalized.

Markers that often suggest mobile

  • Mobile near the end of the string.
  • Android combined with mobile browser tokens.
  • iPhone, iPod, or iPhone OS patterns.
  • Safari examples on iPhone with Mobile/15E148-style markers.

Markers that often suggest desktop

  • Windows NT with Win64; x64.
  • Macintosh; Intel Mac OS X patterns.
  • Linux desktop patterns without obvious mobile markers.
  • Absence of Mobile in many desktop browser strings.

Why the distinction is useful

Responsive debugging

Support teams often need to know whether the reported issue came from a browser that presented itself as mobile or desktop.

Analytics normalization

Dashboards frequently split traffic by device class using user agent parsing rules.

Download and redirect logic

Some sites still switch store links, prompts, or support messaging based on broad mobile-vs-desktop inference.

Browser testing

QA fixtures often need representative strings for both phone and desktop scenarios even when the browser family is the same.

Why the distinction is still imperfect

  • Strings can be spoofed by browser extensions and automation tools.
  • Browsers can reduce detail, especially on mobile platforms.
  • Tablets often sit in the middle and may not look like a simple phone-vs-desktop split.
  • A site may rely on layout viewport, feature support, and Client Hints in addition to the raw string.

Check your current browser

Use the checker if you want to see whether your session currently looks mobile, desktop, or tablet-like.

Check my user agent

Generate both classes

Create desktop, mobile, and tablet samples in one pass with the bulk generator.

Generate bulk samples

See more examples

Compare browser-family examples first if you want the broader pattern library.

Open examples

Understand the basic model

Start with the overview if you want the plain-language explanation of what user agents are and are not.

Read the overview
What usually marks a mobile user agent?

Mobile user agents often include tokens such as Mobile, Android, iPhone, or iPod. Tablet patterns are often different and may omit the Mobile marker.

Can a site reliably detect mobile vs desktop from the user agent alone?

It can infer broad device class in many cases, but the result is not perfectly reliable because strings can be reduced, spoofed, or normalized.

Why do Android tablet strings sometimes look different from Android phone strings?

A common pattern is that Android tablets expose Android without the Mobile marker, while Android phone strings often include Mobile.