Nintendo Switch browser user agent
The Nintendo Switch includes a limited built-in web browser based on WebKit, used mainly for captive-portal logins and embedded views. Its user-agent string carries a NintendoBrowser product token alongside WebKit tokens, which identifies console traffic so you can separate it from desktop and mobile browsers.
What this means
The Switch's built-in browser is intentionally limited; it surfaces mainly for network sign-in pages and certain in-app web views rather than as a general browsing tool. It is based on WebKit, so it shares some Safari-family behaviour, but it is not a full desktop browser.
The NintendoBrowser token is the reliable signal that a request came from the console rather than from a phone or computer.
How it appears
Look for a Mozilla/5.0 prefix, WebKit tokens, and a NintendoBrowser product token, often with a Nintendo Switch platform indicator. Because the browser is WebKit-based, naive detection can mistake it for Safari; the NintendoBrowser token disambiguates it.
Match on the NintendoBrowser token rather than a version. The string is a claim and can be copied, so treat it as device context, not proof.
- Product token: NintendoBrowser
- WebKit-based, so it shares some Safari-family behaviour
- Surfaces mainly for captive portals and embedded web views
How it appears in analytics and logs
A WebKit-based user agent carrying a NintendoBrowser token indicates the Nintendo Switch's built-in browser. It is real human traffic from a game console, with a constrained browser rather than a full desktop one.
Diagnostic use case
Recognise Nintendo Switch console web traffic in logs, separate it from desktop and mobile browsers, and account for its limited browser capabilities.
What WebmasterID can help detect
WebmasterID can classify the NintendoBrowser token as console traffic, keeping game-console visits distinct from desktop and mobile in form-factor reporting.
Common mistakes
- Labelling Switch traffic as Safari because the browser is WebKit-based.
- Expecting full desktop-browser capabilities from the Switch's limited browser.
- Bucketing console traffic as mobile or desktop instead of its own form factor.
Privacy and accuracy notes
The NintendoBrowser token reveals the device class (a console browser), not who is using it. WebmasterID treats it as coarse device context only.
Related pages
- Smart TV and game console user agents
Smart TVs and game consoles have built-in browsers and embedded webviews whose user agents include device-specific tokens — a SMART-TV marker, a platform name, or a console identifier. Recognising these connected-TV (CTV) and console tokens separates living-room devices from phones and desktops in your traffic.
- PlayStation browser user agent
PlayStation consoles include a WebKit-based web browser. Its user-agent string carries WebKit tokens together with a PlayStation platform token (such as a PlayStation 4 or PlayStation 5 indicator), which lets you recognise console web traffic and separate it from desktop and mobile browsers.
- Safari user agent on iOS and macOS
Safari's user agent is built around WebKit and a Version token, and differs between macOS and iOS. A notable quirk is that iPadOS can present a desktop-class Safari user agent, which can make an iPad look like a Mac in logs. This page covers the pattern and the platform-specific behaviour.
- Privacy-first analytics
See console form factor as coarse device context.
Sources and verification notes
- MDN — User-Agent header structureNintendoBrowser token observed for Switch's WebKit browser; exact version not pinned.
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.