THE WORLD IS NOT STANDING STILL.RSS
BIG CHANGE.
BIG CHANGE, one tap away
BIG CHANGE, one tap away

Make room for the big picture.

Add BIG CHANGE to your home screen or desktop. It opens in its own window, with the latest stories when you’re online.

iPhone & iPad
Open bigchange.ai in Safari. Tap Share, then Add to Home Screen. Turn on Open as Web App if shown, then tap Add.
Android
Open bigchange.ai in Chrome. In the browser menu, choose Install app or Add to Home screen.
Desktop
In Chrome or Edge, use the install icon in the address bar or the browser’s app menu. In Safari on Mac, choose File → Add to Dock.

Markdown edition

# Chrome brings local language detection to Android

> Web apps can identify text languages on-device as Chrome 157 rolls out.

By BIGCHANGE.AI Editorial

Published: 2026-11-04T04:56:38.607Z
Updated: 2026-11-04T04:56:38.607Z
Canonical: https://bigchange.ai/blog/chrome-157-android-language-detection-api

![Conceptual charcoal illustration of one person outdoors checking a blank, unbranded web page on a phone.](https://bigchange.ai/api/media/file/render-public-web-app-check-concept-hero-v1.png)
AI-generated conceptual illustration by BIG CHANGE.

Chrome 157 is rolling out to Android with a web API for detecting text language on the device. Google says the update will reach Google Play over the next few days.

## The big change

- Websites can use Chrome’s existing language detector on Android as the release rolls out.
- A local model ranks likely languages; detection does not translate the text.
- Google’s older guide cautions that short text can be unreliable.

## What changes on a phone

[Chrome’s release notes](https://chromestatus.com/release-notes/157) describe on-device, offline-capable detection for web apps. Sites must choose to use it; it does not add a translation button. [Chromium says](https://groups.google.com/a/chromium.org/g/blink-dev/c/-vl89pE1BRE) Android reuses the page-translation model, but Android WebView is excluded. The [Android release](https://chromereleases.googleblog.com/2026/11/) reaches Google Play over days.

## From text to an estimate

Google’s [earlier developer documentation](https://developer.chrome.com/docs/ai/language-detection) describes a ranked list of candidate languages and confidence values. An application can use an estimate to select a language-specific moderation model or determine the source language for translation. The result is an estimate, so the developer must decide how to handle uncertainty.

The older desktop-era manual says a model may need downloading on first use, although it may already be present. It documents availability checks and download progress.

Google cautions that single words and very short phrases can be unreliable, and the model does not cover every language. A low-confidence result may need a fallback. The manual predates the Android release and still says desktop only; the newer release notes describe Android support.

## A developing web interface

The [Web Machine Learning Community Group draft](https://webmachinelearning.github.io/translation-api/) describes an implementation-defined input quota that may be unlimited. It is a draft specification, not proof that Android Chrome implements every provision or has a finite quota.

## Sources

- [Chrome 157 release notes](https://chromestatus.com/release-notes/157) — Android detector and rollout.
- [Chrome language detector manual](https://developer.chrome.com/docs/ai/language-detection) — Earlier detector behavior and limitations.
- [Language detection API draft](https://webmachinelearning.github.io/translation-api/) — Community specification; not a support guarantee.