Growth
$1,650/month
Billed monthly
- 2.2M translated words a month
- 5 languages, read aloud
Marketing sites · documentation · online stores · help centres
Start 3 days free- Today Full access, $0 today.
- Day 3 Your plan starts: $1,650/month.
Website text to speech
One website. Every language. Read it, or hear it read aloud.
One script tag adds text to speech to your website: every page is translated and read aloud in the visitor's language, in a voice that sounds like your brand.
30-minute call · We set your first pages up with you
eazytaxes.com/esTranslating live
EazyTaxesInicioServiciosPreciosNosotrosEmpezar ahora
Año fiscal 2026
Presentar tu declaración debería llevar minutos, no tardes enteras.
Revisamos cada deducción a la que tienes derecho y la presentamos por ti.
Reembolso estimado$2,480Federal$1,940Estatal$540Nuestra tarifa$0
Works with
- WordPress
- Webflow
- Shopify
- Next.js
- One script tagNo rebuild, no re-publish
- 150+ languagesText and audio in each one
- Cached per pagePriced by site size, not traffic
- SOC 2 Type IIIndependently audited security
Website text to speech demo
Hear a web page read aloud in another language
eazytaxes.comEN
EazyTaxesHomeServicesPricingAboutStart my return
Tax year 2026
Filing your return should take minutes, not evenings.
We check every credit you qualify for, and we file it for you.
Upload last year’s return and we carry everything over automatically.
Estimated refund$2,480Federal$1,940State$540Our fee$0
Listen to this page
Sample page · English · 9 seconds
Why now
Your visitors speak many languages. Many would rather listen.
76%
of online shoppers prefer to buy where the information is in their own language, and 40% will not buy from a website in another language at all.
CSA Research · 8,709 consumers, 29 countries (opens in a new tab)95.9%
of the top million home pages had detected WCAG 2 failures, averaging 56 errors a page. Audio and captions are among the cheapest of those to fix.
WebAIM Million, 2026 (opens in a new tab)2.2bn
people live with a near or distance vision impairment. For many of them, a page that can be listened to is the only version of your page they can use.
WHO · World report on vision (opens in a new tab)
One install, four jobs
Four ways one website reaches everyone
Read
Every page, in their language
Navigation, body copy, buttons and alt text are translated in place and keep your layout. Each language gets its own URL, so it can be linked, shared and indexed.
Listen
Any page, read aloud
A player sits at the top of the page and reads it in the language the visitor is already on, in your brand voice. Useful on a commute, and necessary for anyone who cannot read the screen.
Accessible
Accessibility built in, not bolted on
Audio, a readable DOM and per-language transcripts come out of the same install, so accessibility stops being a separate project with its own budget.
After publish
New pages keep up
Publish a page and it is translated and narrated on first request, then cached. Change a paragraph and only that paragraph is regenerated.
On mobile
The same page, in their pocket.
The player is built for how people actually read on a phone: they start it, lock the screen and keep listening. The same translated text and the same narration are served to your iOS and Android app through the SDK, so the app and the website never drift apart and you never pay to translate the same sentence twice.
- Keeps playing with the screen locked, with lock-screen controls
- The same cached audio the website serves, so nothing is generated twice
- Picks the language from the phone, not from a menu nobody opens
- One SDK for iOS and Android
Press play on the phone — it is the same audio the demo above plays.
eazytaxes.com
EazyTaxesHomeServicesPricingAboutStart my return
Tax year 2026
Filing your return should take minutes, not evenings.
We check every credit you qualify for, and we file it for you.
Upload last year’s return and we carry everything over automatically.
Estimated refund$2,480Federal$1,940State$540Our fee$0
Listen to this page
Tuned for the web
Built for the way a website really works.
A site is not a document. Pages change, navigation repeats on every screen, and prices, product names and legal terms have to survive translation untouched.
Voice
Your brand voice, every language
Clone one voice once and it reads Spanish, Korean and Portuguese without sounding like a different company in each one.
Vocabulary
Your names stay your names
Products, people, plans and legal terms go in a glossary and come out exactly as you wrote them.
Speed
Cached, then served from the edge
Generation happens once per page-language. After that a translated page is as fast as the original.
Control
Edit any line in place
Click the text on the live page and retype it. Pinned edits survive every later regeneration.
Search
hreflang and sitemaps included
Real URLs per language with the tags search engines expect, not a client-side swap they never see.
Reach
The same content in your app
The iOS and Android SDK reads the same translated and narrated content the website serves, so an app never pays to translate a sentence the site already did.
Make it pay for itself
Audio ads on every listen, from an ad break you already own.
Turn the player on and a sponsor read runs before the article, served from your own ad server over a standard VAST tag. You keep the inventory, you keep the relationship, and you keep the revenue — we take nothing of it.
Opt in
One attribute turns it on
Add data-ad-tag to the script with the tag from Google Ad Manager, Triton, AdsWizz or whoever already sells your inventory. Leave it off and the player never makes an ad request at all.
Your revenue
You keep 100% of it
The audio-article platforms that bundle ads typically take half. Your ad server bills your advertisers and pays you directly — the fee you pay us is the subscription, and nothing else.
Your numbers
Counted where you already look
Impression, start and every quartile fire as standard IAB pixels, so listens show up in the same reports as the rest of your inventory rather than in a dashboard nobody opens.
<script
src="https://website-translator.camb.ai/v1/camb.js"
data-api-key="pk_live_your_public_key"
data-languages="es,ko,pt"
data-audio="on"
data-ad-tag="https://pubads.g.doubleclick.net/gampad/ads?iu=/1234/audio&..."
defer
></script>Standard IAB VAST 4.2 audio
Works with Google Ad Manager, Triton, AdsWizz or any SSP that returns an audio creative.
Impression and quartile pixels fire from the player, so your existing reporting counts it like any other inventory.
Lifecycle
One page, end to end
What happens between a visitor asking for a page and hearing it.
Generated
First ask
A page nobody has opened yet
The page is read, translated and narrated once, then written to the cache.
+1 s
The audio is built
Each paragraph is narrated in the brand voice and stitched into one track with timings.
On publish
You change a paragraph
Only the changed block is retranslated and renarrated. The rest of the page is untouched.
Cached
0 ms
A visitor asks for /es
Already generated, so the translated page is served from the edge like any other page.
Always
Everyone after the first
Served from the cache, in every language, however much traffic arrives.
A few of the 150+ languages
- Español
- 한국어
- Português
- Tiếng Việt
- Tagalog
- Українська
- العربية
- Français
- 中文
- Русский
- हिन्दी
- فارسی
- Kiswahili
- አማርኛ
- اردو
- Polski
- 日本語
- Bahasa Indonesia
What you get, and from how many vendors
Translation and text to speech in one stack, not three invoices.
Translation vendors do not do audio. Audio vendors do not do translation. Doing both means two integrations, two caches and two bills that never quite line up.
| Capability | Translation pluginWeglot, Localize | Article-audio toolBeyondWords, Trinity | CAMB for Web |
|---|---|---|---|
| Translated pages with their own URLs | Included | Not offered | Included |
| Listen to the page as audio | Not offered | Included | Included |
| Audio in the translated language | Not offered | English mostly | Every language |
| Your own brand voice | Not offered | Higher tiers | Growth and up |
| Edit a translation on the live page | In a dashboard | Not offered | Click and retype |
| Glossary for product and legal terms | Higher tiers | Not offered | Every tier |
| Priced by | Words + views | Articles / month | Pages, once |
| Same content in a mobile app | Not offered | Not offered | iOS and Android SDK |
| One visitor, read and heard | Text onlyBring your own audio vendor | Audio onlyEnglish, or bring a translator | CompleteOne vendor, one cache, one bill |
Based on the publicly published feature lists and pricing pages of those products, October 2026.
How it works
Add text to speech to your website once. It keeps up on its own.
Add one tag to your template
Paste the script into your site template with your public key. Nothing else about your build changes, and your original pages keep serving exactly as they do today.
Pick languages and a voice
Choose the languages your visitors actually read, then either clone your brand voice or pick a reader per language from the library.
Publish and let it fill in
The first visitor in each language generates that page. Everyone after them gets the cached copy. You can also pre-generate your top pages before launch.
Read what people do with it
See which languages get used, which pages get listened to and how far through people get, so you can decide which languages are worth keeping.
<script
src="https://website-translator.camb.ai/v1/camb.js"
data-api-key="pk_live_your_public_key"
data-languages="es,ko,pt"
data-audio="on"
defer
></script>Pricing · 3 days free
Priced per page, not per visitor.
A page is translated and narrated once, then cached and served from the edge. You pay for the size of your site, never for the traffic it gets. A page that goes viral costs exactly the same as one nobody reads.
Monthly words10K25M+10M words
Scale
$2,400/month
Billed monthly
- 4M translated words a month
- 10 languages, read aloud
Publishers · SaaS products · agencies · multi-brand sites
Start 3 days free- Today Full access, $0 today.
- Day 3 Your plan starts: $2,400/month.
Business
Recommended$5,000/month
Billed monthly
- 10M translated words a month
- 25 languages, read aloud
Multi-region brands · marketplaces · large catalogues
Start 3 days free- Today Full access, $0 today.
- Day 3 Your plan starts: $5,000/month.
Advanced
$9,750/month
Billed monthly
- 25M translated words a month
- 75 languages, read aloud
Enterprise · global retail · regulated industries
Start 3 days free- Today Full access, $0 today.
- Day 3 Your plan starts: $9,750/month.
Global
Beyond 150,000 pages or 75 languages we size it with you, and run it where your data has to live.
- Enterprise
- marketplaces
- regulated industries
- mobile apps
Full access, every language, no page limit during the trial. You add a card when you subscribe and pay $0 today. Cancel any time before the trial ends and you pay nothing. Prices in US dollars; sales tax or VAT is added at checkout.
FAQ
Website text to speech: what teams ask us
One script tag, no plugin to maintain. You add it to your template, the same way you add an analytics tag, and nothing about your build changes. CAMB reads the page that is already rendered, so it works with WordPress, Webflow, Shopify, Next.js or anything else that serves HTML.
Yes. You clone one voice from a short sample and it reads every language, so a Spanish visitor hears the same voice an English visitor hears.
A page is translated and narrated once, then cached. The first listener in a new language waits while it is generated; everyone after that gets the cached audio from the edge, so it starts like any other audio on your site.
Add them to your glossary and they are passed through untouched, or translated exactly the way you specify. Numbers, currencies and code blocks are left alone by default.
Each language gets its own URL path, hreflang tags and a translated sitemap, which is what search engines expect from a multilingual site. The translated text is in the HTML, not injected after load. If you only need the text translated, see website translation.
A unique URL. A page translated into five languages counts as five page-languages, each counted once no matter how many people read or listen to it.
Because traffic is not what costs us anything. Generating a page-language is the real cost and it happens once; serving the cached copy to the millionth visitor is free. Charging by page views would mean billing you for the month your post did well.
Yes. A browser script cannot run inside a native app, so the iOS and Android SDK talks to the content API directly and gets back the same translated text and the same cached audio the website serves. Your app and your site never drift apart, and neither pays to translate a sentence the other already did.
Yes. The player reads the page in the language the visitor is browsing in, so a Spanish visitor hears the Spanish page, not the English one, in the same brand voice.
You do not need one. The script tag goes in your theme header, like an analytics tag, and works the same way on Webflow, Shopify, Next.js or anything else that serves HTML.
Growth includes reading and listening analytics: which pages are played, in which language and how far through people get, so you can decide which languages are worth keeping.
Every visitor, in their language, reading or listening.
Add the tag to one page and hear your own site back in Spanish in about a minute.