Skip to content
New · the open voice benchmark is liveRead it
cantari
For teams making content readable aloud

Turn written content into a clear read-aloud.

Articles, documentation, and help content are not always easy to read. Generate a clean spoken version so the same content reaches people who prefer or need to listen.

No credit card · Real engines · The audio is yours

Painted armchair by a sunlit window with headphones resting on an open book
Generated voice
MP3 + WAV · yours to export
The moment

Your help center is four hundred articles deep, and every one of them assumes the reader can comfortably read. Support keeps hearing from people who would rather listen. Recording a human read of a knowledge base that changes weekly was never going to happen.

Why this is hard

What Accessibility actually needs.

We would rather name the friction plainly than pretend it away. Here is the problem this page is about.
The honest problem

A lot of written content stays written, which leaves out anyone who reads with difficulty or simply prefers to listen. Recording a human read of every article and doc page is not realistic at the volume content moves. Generating a clear spoken version means the same material can be offered as audio without a recording session for each update.

How Cantari helps

Real features, mapped to the job.

Every item here works today, or says plainly where it is still in progress.

Clear, neutral read

Kokoro gives a clean, plain read that suits articles and documentation, where clarity matters more than drama.

Keeps pace with updates

When the content changes, regenerate the audio. The flat allowance means keeping audio current does not run up a per-character bill.

Long-form in one pass

Up to 30,000 characters per generation, so a full article or doc page goes through without chopping it up.

Own and host it

Export MP3 or WAV with commercial rights and no watermark, yours to host alongside the written version.

Worked example

Read-aloud: a help-center article

Script fragmentKokoro

This article is also available as audio. Press play to listen.

To export your data, open Settings and choose Download archive. The file arrives by email within a few minutes.

If the download does not arrive, check your spam folder first, then contact support from the same page.

Line 2, real Kokoro output, unedited.

Kokoro, voice Michael: a steady, plain read. An audio alternative serves the spirit of accessible content, but it is not a screen reader and does not make a page WCAG-conformant on its own. We will not claim otherwise.

The honest arithmetic · about 1,000 characters is a minute of speech
~12,000
characters in a 2,000-word article
~12 min
of listening from that same article
30,000
characters per pass, no chopping a long page
The workflow

How it goes, step by step.

Step 1: Paste the content

Drop the article or doc text into Text to Speech, up to 30,000 characters per pass.

Step 2: Pick a clear voice

Choose a clean, neutral voice that reads plainly for the spoken version.

Step 3: Generate and publish

Generate the audio, export it, and host it next to the written content.

Honest scope

What an audio version adds to accessibility, and what it does not.

It complements assistive tech, never replaces it

People who rely on screen readers already have one, tuned to their own speed and habits. An audio edition serves a different group: readers with fatigue or dyslexia, people newer to your language, anyone listening on the move. Treat generated audio as one more accessibility option on the page, not as the page's accessibility strategy.

Conformance lives in the markup

Publishing an audio edition does not make a page meet WCAG, and a vendor claiming otherwise should make you suspicious. Conformance is structure: headings, alt text, contrast, keyboard paths. The audio file is a courtesy on top, valuable precisely because nobody is pretending it is more.

Stale audio is its own failure

An outdated spoken version hands the listener yesterday's instructions for today's interface, which is worse than no audio at all. Regenerating the read when an article changes takes minutes on a flat allowance, so the spoken edition can carry the same revision date as the written one.

Recommended engine

Start with Kokoro.

Kokoro reads cleanly and plainly and drafts fastest, which fits read-aloud of articles and documentation where clarity is the priority.

KokoroLightweight - plain read

Cheapest. Clean, plain read. Ignores cues.

Quality Elo
1060
Latency
973 ms (measured 2026-06-10)
Languages
8
Rights
Apache-2.0 model; commercial OK
CheapestFast
Hear a line for this use case

This article is also available as audio. Press play to listen instead of reading.

Real Kokoro output, recorded unedited.

The honest answers.

What Cantari can and cannot do for accessibility today, in plain language.

Is this a full assistive-technology replacement?
No, and we will not overclaim. This generates a clear spoken version of written content you control. It is not a screen reader or a certified accessibility solution; it is one honest way to offer your content as audio.
Which voice is best for read-aloud?
A clean, neutral voice that reads plainly. Kokoro suits this well and drafts fastest. Clarity usually matters more than expression for articles and docs.
Can I update the audio when the article changes?
Yes. Regenerate the section that changed. The flat allowance means keeping the audio current does not bill you per character each time.
Keep exploring

Try Cantari for accessibility.

Free to start, no credit meter. Open the studio and hear it for yourself.