Vivaldi browser user agent
Vivaldi is a Chromium-based browser from Vivaldi Technologies. Because it is built on Chromium, its user-agent string follows the Chrome pattern and may include a Vivaldi version token; on some platforms Vivaldi reports a Chrome-only string with no Vivaldi marker. Treat it as a real human browser, not automation.
What this means
Vivaldi is a desktop and Android browser built on the Chromium open-source project. Like Edge, Brave, and Opera, it shares Chrome's rendering engine, so its user agent inherits the Chrome structure: a Mozilla/5.0 prefix, a platform token, AppleWebKit and Chrome version markers, and Safari for compatibility.
Vivaldi may append its own product token with a version number after the Chrome marker. However, Vivaldi has at times shipped a user agent identical to plain Chrome to avoid breaking sites that sniff for specific browsers, so a missing Vivaldi token is not proof the visitor is not using Vivaldi.
How Vivaldi identifies itself
When present, the distinguishing signal is a Vivaldi product token plus version appended to an otherwise Chrome-shaped string. Match on the literal Vivaldi token rather than the version, which changes with each release.
For reliable browser detection, prefer Client Hints (the Sec-CH-UA header) where available, since the legacy user-agent string is increasingly frozen and reduced across Chromium browsers.
- Engine: Chromium (Chrome-pattern user agent)
- Distinguishing token when present: Vivaldi plus version
- May report a Chrome-only string on some platforms
Why it matters for analytics
Vivaldi is a real human browser, so it belongs in human traffic, not bot traffic. If your dashboards group all Chromium engines under Chrome, Vivaldi users may be undercounted as Chrome.
Do not block Vivaldi as automation merely because it resembles Chrome. The presence of a Vivaldi token, normal navigation timing, and Client Hints all indicate a genuine browser session.
How it appears in analytics and logs
A user agent following the Chrome pattern that also contains a Vivaldi token is the Vivaldi desktop or Android browser — a human visit on the Chromium engine. The absence of the token does not prove a request is not Vivaldi, because the browser does not always advertise itself.
Diagnostic use case
Recognise Vivaldi visitors when auditing browser-share, and understand why a fraction of real Chromium-engine traffic may not carry a distinct Vivaldi label.
What WebmasterID can help detect
WebmasterID classifies Vivaldi as a human Chromium-engine browser rather than a bot, so it is counted in human analytics. It surfaces the browser family as context without building a fingerprint from it.
Common mistakes
- Assuming every Chrome-pattern user agent without a Vivaldi token cannot be Vivaldi.
- Counting Vivaldi as a bot because it shares Chrome's engine.
- Matching on a Vivaldi version number instead of the stable Vivaldi token.
Privacy and accuracy notes
Vivaldi is identified only from the request user-agent token. No visitor identity, device fingerprint, or exact location is involved. WebmasterID records the browser family as coarse context, never as a personal identifier.
Related pages
- Brave browser user agent
Brave is a privacy-focused Chromium browser that, by design, does not advertise itself in the user-agent string. It mirrors Chrome's user agent so sites cannot single Brave users out and to avoid breaking UA-sniffing sites. This page explains why Brave is hard to detect from the UA and why that is intentional.
- Opera user agent
Opera switched to the Chromium engine, so its user agent resembles Chrome's but adds an OPR/ product token at the end. That OPR/ marker is how you tell Opera apart from Chrome and Edge in logs. This page covers the pattern and the historical Presto-era caveat.
- Chrome user agent and its quirks
Chrome's user-agent string is full of historical artefacts: it claims AppleWebKit and Safari for compatibility even though Chrome uses the Blink engine. Google has also reduced the detail Chrome exposes in the UA, moving fine-grained information into User-Agent Client Hints. This page explains the pattern and the quirks.
- Bot vs human
How WebmasterID separates real browser visits from automated traffic.
Sources and verification notes
- Vivaldi — official browser siteChromium-based browser; exact UA token presence varies by release.
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.