Since Chrome 138 (May 2026) there's a full AI model in the browser — Gemini Nano, on-device. No API key, no per-call cost, no data sent to a server. For small business use cases that changes the math.
1. What's actually inside Chrome
Chrome's built-in AI offers four APIs via window.ai: summarizer, translator, writer and prompt. It runs locally on the visitor's GPU/CPU — no network traffic after the one-time model download (~2GB).
2. Where you should use it
- Form assist — user types a short note, AI writes the complete email or product description
- Live translation — product descriptions, FAQs, support chats multilingual without an agency
- Summaries — long documents/reviews reduced to one sentence for the visitor
- Search/filter — natural-language search over your product catalog, local and private
3. Where it doesn't (yet) work
Gemini Nano is ~3.5B parameters — powerful for light tasks, too small for complex reasoning. Concretely: fine for 'write an English version of this text', not for 'analyze my financials and give strategic advice'. For the latter you still use Claude/GPT via API.
4. Cost comparison for small business
A small-business webshop with 500 product descriptions you want translated into 4 languages via AI:
- OpenAI GPT-4o: ~€80–120 one-time (2,000 calls)
- Translation agency: ~€2,500–5,000
- Chrome Gemini Nano: €0 — visitor does it in the browser on first visit
5. Browser support and fallback
Chrome 138+ has it, Edge expected Q3-2026. Safari and Firefox: no timeline yet. So: detect with 'ai' in window, fall back to an API call (OpenAI/Claude) for browsers without support. Hybrid is the right setup for now.
6. Privacy is the real selling point
For sectors with sensitive data (healthcare, legal, finance) 'data never leaves the browser' is a GDPR dream. Concretely: a lawyer summarizing documents needs no data-processor agreement with OpenAI — Gemini Nano runs locally, nothing leaves.
7. What you can build today
Start small: add a 'write for me' button to your contact form or webshop review field. Takes 10 lines of JS. Visitors without support don't see the button — no breaking change. Then scale the approach to bigger flows once you see it working.