Proofreader API
Checks spelling and grammar on the device.
In one line
Can check spelling and grammar of text you typed, on your device, in Chrome testing
Checks spelling and grammar on the device.
Local proofreading of what the person typed.
What it can and can't do
What the user does: You type in a form or comment box on a site in the Chrome trial
It can
- Check spelling and grammar locally
- Suggest fixes for text you typed
- Keep your text on your device
It cannot
- Work for normal visitors yet, since it is a developer or origin trial
- Work in Edge, Firefox, Safari or on phones
- Check text you have not typed or pasted into the page
- Send your text to a server for this feature
How it differs between platforms: Only in a Chrome testing trial today. Not in Firefox, Safari or on phones.
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Behind a flag | Not available | Trial |
| Edge | Not supported | Not available | None |
| Firefox | Not supported | Not available | None |
| Safari | Not supported | Not available | None |
| Safari on iPhone | Not supported | Not available | None |
| Chrome on Android | Not supported | Not available | None |
| Samsung Internet | Not supported | Not available | None |
How a site asks for it
| API | Proofreader.create(); p.proofread(text) |
| Permissions policy | proofreader |
| How access is granted | origin-trial |
| What the user sees | Developer or origin trial |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | Yes |
| How long it lasts | Per origin |
| How to take it back | Site settings |
| Inside an iframe | Same as top level; cross-origin iframes need a permissions policy where listed |
Typical flow
- Call the API
- Browser applies its access rules
- Page receives the result
Data you get
What comes back: Checks spelling and grammar on the device.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
corrections[] | list | None | startIndex, endIndex, correction | Not listed |
Technical limits
- No BCD entry
- Hardware as Prompt API
The story
What it is
A page can check spelling and grammar for you using an AI model on your device.
For you
You type and see corrections, like red underlines. The checking happens on your computer, so your draft is not sent out. Not every site can use it yet.
For makers
Makers get grammar help with no external service or extra cost. It keeps private drafts private. It is still in testing, so it is not available to all users.
Where you see it
| Type | Example | Apps |
|---|---|---|
| messaging | A web email app checks tone and typos on device before you press send. | Gmail |
| education | A homework site flags grammar mistakes in a student's essay, without storing the essay. | None named |
| social | A post box on a web social site marks typos as you write. | None named |
| productivity | A web document editor fixes grammar offline on a plane. | Google Docs |
| shopping | A seller tool on a marketplace checks product descriptions for errors. | Etsy |
| accessibility | A page helps a reader with dyslexia fix spelling as they type. | None named |
| enterprise | A company wiki checks for mistakes in internal pages with no cloud call. | None named |
Risks
- Early testing only
- Can suggest wrong fixes
What the platform says
- Google Chrome: Built-in AI. Chrome's built in AI includes writing helpers that run on the device, so text stays private.
Good uses and abuse
Legitimate uses
- Forms and comments
Known abuse
- None
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 3 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2026, Chrome: Trial in 2026; status varies in docs
Sources
How well checked: Inferred from related behavior.