Source: https://bscan.info/blog/chromium-version
Language: en

User-Agent strings are easy to fake, but supported web features reveal the real Chromium version underneath - and a version mismatch makes you look spoofed.

# Your User-Agent Lies. Your Chromium Version Doesn't.

Published May 22, 2026 · Updated June 11, 2026

Open your browser console and type `navigator.userAgent`. That string, the one that says you are “Chrome 137 on Windows,” is just text your browser hands out. You can change it with an extension in about two clicks, and anti-detect browsers rewrite it on every request. So to a tracker, your User-Agent is a claim, not a fact.

The thing is, there is a fact sitting right next to that claim. Every version of Chromium ships with a specific set of web features built into the engine. You can rename the label on the box, but you cannot easily change what is actually inside it.

**The short version:** your User-Agent is editable text, but the features your browser supports are not. Read those features and you get the real Chromium version. If it does not match the User-Agent, you look spoofed.

The widget on this page does exactly that. It ignores your User-Agent completely and works out your real Chromium version from the features your browser actually supports.

## How feature detection figures out your version

Every few weeks Google ships a new Chromium release, and each one switches on a handful of new web features. A CSS property here, a JavaScript API there. All of it is documented publicly on [Chrome Platform Status](https://chromestatus.com/features).

That gives us a timeline to work with, and we can simply walk up it until your browser stops keeping up:

Walking up the feature timeline

1.  ![supported](https://bscan.info/GoodIcon.svg)
    
    Chromium 144
    
    adds `Temporal API`
    
    your browser has this
    
2.  ![supported](https://bscan.info/GoodIcon.svg)
    
    Chromium 145
    
    adds `text-justify`
    
    your browser has this
    
3.  ![supported](https://bscan.info/GoodIcon.svg)
    
    Chromium 146
    
    adds `Iterator.concat()`
    
    your browser has this
    
4.  ![supported](https://bscan.info/GoodIcon.svg)
    
    Chromium 147 you are here
    
    adds `contrast-color()`
    
    your browser has this
    
5.  Chromium 148
    
    adds `revert-rule`
    
    your browser is missing this
    

This browser supports everything up to **Chromium 147** but not 148, so 147 is its real engine version, whatever its User-Agent claims.

The clever part is that none of this can be faked by editing a string. Either `'variants' in Intl.Locale.prototype` is true in your engine or it is not. To fake the features themselves, you would have to ship an entirely different browser build.

## Why any of this matters

On its own, knowing you are on Chromium 137 is not a big deal. So is most of the internet. What actually matters is whether your story holds together.

A normal, untouched browser is consistent with itself: a Chrome 137 User-Agent sits on top of a Chromium 137 feature set, because they both came from the same build. But the moment something spoofs only the User-Agent, say a privacy extension, a cheap proxy, or a misconfigured automation tool, the two stop matching up. Try flipping the switch below:

What it claims

Chrome 120

User-Agent string· edited

vs

What it really is

Chromium 137

feature-detected engine

![](https://bscan.info/BadIcon.svg)

Mismatch

The claim and the real engine disagree. This contradiction is the tell that fraud and anti-bot systems look for.

That contradiction is louder than the version number ever was. Spoofing one signal while leaving the engine untouched can actually make you easier to single out, not harder. We get into more of this in [how browsers compare on fingerprinting](https://bscan.info/blog/browserCompare) and [the Widevine DRM oddity](https://bscan.info/blog/widevine-drm).

## What to actually do about it

1.  **Keep your browser up to date.** An old engine is a fingerprint of its own, and a security risk on top of that. The widget will tell you if your real version is falling behind.
2.  **Do not half-spoof.** Flipping your User-Agent while leaving the engine alone is worse than doing nothing, because it manufactures the exact mismatch trackers hunt for.
3.  **Align the whole stack.** If you genuinely need to run multiple identities, for ad verification, market research, or managing a lot of accounts, the goal is a browser where the User-Agent, the engine features, and every other signal tell one consistent story.

That last one is really hard to pull off by hand, which is the entire reason anti-detect browsers exist. [Incogniton](https://www.incogniton.com/?utm_source=bscanInfo&utm_medium=Website&utm_campaign=ChromiumVersionBlog) builds each profile on a real, consistent Chromium base, so the engine your features expose actually matches the identity you are presenting instead of arguing with it.

[Run the full browser scan](https://bscan.info/)

## Keep reading

[

![Zen Browser and Widevine: Why Netflix Won't Play](https://bscan.info/widevineCover.svg)

Zen Browser and Widevine: Why Netflix Won't Play

](https://bscan.info/blog/widevine-drm)[

![Audio Fingerprinting: The Sound of Tracking](https://bscan.info/audioCover.svg)

Audio Fingerprinting: The Sound of Tracking

](https://bscan.info/blog/audioFingerprinting)[

![Camera Fingerprinting: Exposed by Your Webcam](https://bscan.info/cameraCover.svg)

Camera Fingerprinting: Exposed by Your Webcam

](https://bscan.info/blog/cameraFingerprinting)

---
This is the page's server-rendered documentation. Interactive browser tests, file processing and permission prompts require the HTML page; Markdown does not contain live measurements or process files.
