Linux user agent tokens
Desktop browsers on Linux include an X11; Linux platform token, usually with an architecture marker such as x86_64. The token confirms a Linux desktop browser but rarely identifies the distribution, and Linux strings are also common among servers, headless tools, and bots, so context matters.
What this means
Desktop browsers on Linux include an X11; Linux platform token, commonly with an architecture marker such as x86_64. Unlike Windows or macOS, the token usually does not name the distribution (Ubuntu, Fedora, and so on), so you learn that it is Linux but not which flavour.
Linux desktop share is small relative to Windows and macOS, but it is a real human audience, often technical users and developers.
Overlap with non-human clients
Linux is the dominant OS for servers, cloud functions, CI runners, headless browsers, and many bots. As a result, a large share of Linux-flavoured user agents are not human desktop visits at all.
Distinguish a real Linux browser from automation by the full browser structure (engine and version markers), the presence of Client Hints, sub-resource requests, and normal navigation timing. A bare Linux string with a script token is automation, not a desktop user.
- Token: X11; Linux plus an architecture marker
- Distribution is usually not identified
- Servers, headless tools, and bots also produce Linux strings
Practical handling
For analytics, group Linux desktop browsers as a small but valid human segment, and rely on behavioural signals to keep Linux-based automation out of human counts.
Do not assume a Linux token implies a server, nor that it implies a human — the token is ambiguous, and the surrounding signals resolve it.
How it appears in analytics and logs
An X11; Linux token in a full browser user agent indicates a Linux desktop browser. But because servers, headless browsers, and scripts also run on Linux, a Linux token by itself is not proof of a human desktop visit.
Diagnostic use case
Interpret Linux platform tokens for desktop analytics while recognising that many non-browser clients and bots also run on Linux and produce Linux-like strings.
What WebmasterID can help detect
WebmasterID treats the Linux token as coarse OS context and weighs it against behaviour and other signals, so genuine Linux desktop users are counted as human while Linux-based bots and headless tools are classified as automation.
Common mistakes
- Assuming every Linux token is a bot or a server.
- Trying to read the specific distribution from the token.
- Counting Linux-based headless browsers as human desktop visits.
Privacy and accuracy notes
The Linux token is coarse OS context, not an identity. WebmasterID records the broad platform family only and never uses the token, alone or combined, to fingerprint a device.
Related pages
- Headless browser user agents
Headless browsers run a real browser engine without a visible window, and are widely used for testing and scraping. Headless Chrome historically exposed a HeadlessChrome token, though automation can also wear an ordinary browser string. This page explains the patterns and why headless traffic is automation.
- Windows user agent tokens
Browsers on Windows include a Windows NT platform token in the legacy user-agent string. The NT version number has been effectively frozen, so it identifies the Windows family but not the marketing version — Windows 10 and Windows 11 share the same NT 10.0 token. Use Client Hints for finer platform detail.
- Go-http-client user agent
Programs built with Go's standard net/http client send a default user agent of the form Go-http-client/x.y. Seeing it means a Go application made the request — common for backend services, CLIs, and integrations. It is honest automation, not a browser, and the default can be overridden. This page covers the pattern.
- Bot vs human
Separate Linux desktop users from the many Linux-based bots and tools.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.