Local, CPU-Friendly, High-Quality TTS (Text-to-Speech) with Kokoro

21 hours ago (ariya.io)

I was kind of waiting for Apple to ship something like this and using speechify in the meantime, so I was pleasantly surprised to stumble across Kokoro in a thread on HN a few days ago. The voices are better than the cloud provider IMO.

I'm using it in an open source tool I built for listening to coding agents instead of watching them work, and it's been great. Local, private, free to run, and enough voices that I can actually use a different one for each agent.

Wrote a bit more about the project here: https://jonmagic.com/posts/i-stopped-watching-my-agents-work...

I have used Kokoro fairly extensively for an accessibility product. I have loved working with it (especially because I don't have an NVidia GPU like many TTS of similar quality require).

I particularly appreciate the fact that it lets you manually add IPA pronunciation guides. There have been some cases where an important word is a homograph and Kokoro assumed the wrong pronunciation.

The place where it falls a little short is in saying just a single word or two. Try having it say simply "six" and it almost always says something like "ah-six-ah". I found a way around that though. If you give it a longer sentence to say (eg "The word is: six") it will say it fine. The trick is that the Kokoro API gives you the timestamp of each word in the sentence. So you can have a Python script crop out just the word you care about. The intonation is a little flat this way, but is very reliable.

I asked about this on the discord, and was told that it is a limitation of the small parameter size. But in fairness to Kokoro, even eleven-labs' voices suffer from this occasionally.

  • Same trick with many others. I say "Knight" to Wispr or Google and see "night". I say "Knight to f3", and just backspace out "to f3".

  • It is indeed a common weakness of TTS models.

    Unfortunately it makes it unsuited for my use case, which is almost entirely single words, as I don't particularly want to deal with stitching/segmenting input/output.

Fun... This is something I actually care about...

I used to keep a version of whisperx around, because I think it's important to have not just transcription, but also timing and speaker identification (e.g. for subtitles)... It depends on pyannote, though, which has some wierd licensing (and is tougher to script the installs because of it), so I wanted to look at something that both had better transcription, and supported diarization (the speaker and timing). I decided on parakeet for the transcription with softformer (the diarization), but most of the available engines for it don't include softformer.

I coded up an OpenAI compatible server for parakeet-rs ( https://github.com/altunenes/parakeet-rs ) (which does support softformer) and I've been using it with OpenWhispr (a desktop app for transcription that handles all sorts of neat thing).

I'm doing CPU-only transcription (because I use my GPUs for other stuff and haven't gotten around to adding in the GPU-path), but it's incredibly empowering to be able to have local transcriptions at will.

  • This is TTS. Not STT.

    For what you are doing, Senko works really well for diarization along with parakeet.

    Faster and more accurate than Pyannote and whisper on my MacBook anyway.

    • You're right... I read the title too quickly... I'll have to look at Senko vs Softformer later...

Love this model. I’m GPU poor and have had FOMO that I haven’t played with local models at all. About a month ago I setup Kokoro on my GTX1650 to do TTS for an article reader. A simple WebUI lets me paste a URL or a chunk of copy pasted text. Python cleans it up and sends to Kokoro for TTS and it’s then served via RSS for Apple Podcasts. Then for my morning drive I’ll catch up on articles or blog posts I’ve gathered.

At some point I’d like to play with separate voices and see if I could build something like NotebookLM for kind of like a radio morning show of news items I’ve gathered.

TTS has come incredible long way, there are so many options. There is Kokoro of course, then there is Pocket TTS which is also a tiny 100M model that allows voice cloning. There is also Chatterbox Turbo, which is bit bigger but also allows for more emotional control of the voice. And then finally there is the Fish Audio S2, which is even bigger but allows even larger and essentially unbounded finegrained control of tone and emotion. And all of these can easily run on your Macbook.

  • Dunno why people still write about Kokoro, there are better alternatives. Pocket TTS has more natural intonation and voice cloning. Supertonic 3 is another great model in the same weight class, which is the only one that can autodetect language and make a mix of different languages sound good.

Super cool!!

I've been using my own solution since January. I'm on Linux, and can't use Aqua, Whipsrflow etc... So i made my own.

Recently cleaned it up and made it install friendly.

If anyone is interested, you can check it out here: https://github.com/Hugo0/voiceio

It's self-improving over time, runs on your local machine, and is generally decent software. 60% of my interaction with my PC nowadays is pure voice input.

  • This is text to speech, yours is speech to text. (But also thanks, your STT looks interesting)

    • Technically Voiceio also does TTS, but it's really crappy and just meant to read stuff loud / select a lot of text and listen to it podcast style whilst I'm e.g. washing the dishes.

      However you're totally right that it's focused on STT. I probably use it 95% for STT and only occasionally for TTS (which also reflects itself in the amount of polish I put into each)

      and thanks!

This is awesome. People are already talking about use of local models for heavy tasks like llm inference. TTS is very much possible on device without any high end gpu. That's why Ive been working integrating it into a free reader web app with some features more than just getting audio from a text.

https://desktop.with.audio/reader

I don't want to mess with port numbers and gpu cards; I just want an upgrade from the age-old:

    apt install festival

with the same installation simplicity.

I'm using Kokoro for a fun little side-project browser-based game I'm working on. It's legitimately super good for being only 85mb (for the wasm version) or 300mb (for the webgpu version).

I recently created a video and didn't want to use my voice on it.

Rather than TTS I did STS (speech to speech) through Eleven Labs (you upload the video it alters the audio track to voice of choosing with some parameters you can control).

I showed it to a bunch of people and they could not believe it was non-human. The bit that got most was all the pausing, broken sentences ...essentially elements you don't put into text if your doing T2S.

An LLM over the original text could perhaps inject these elements though if prompted correctly.

Cool I actually got it ported to iPhone’s ANE finally yesterday! So we can get both rt natural local TTS and 4x less battery drainage and thermals

I'm using exactly this TTS engine for my intercom door system I built. The quality of the TTS is very good.

Supertonic 3 is pretty amazing too. I’ve got time to first sound down to well under a second by streaming chunks and stitching together from CPU with goonx (non c-go onnx) - happy to upload model if any go devs interested.

kokoro is decent but pocket-tts is much better especially when you rip a good voice. https://github.com/kyutai-labs/pocket-tts

the onnx version of pocket-tts does perform better. https://huggingface.co/KevinAHM/pocket-tts-onnx

  • I agree, pocket-tts is quite good. It is also very easy to make new voices from small sample files with pocket-tts.

  • I've found that for CPU inference the PyTorch-based (non-quantized) version of Pocket TTS actually performs (both speed and quality-wise) better than the ONNX version, even after fiddling with all of the knobs that ONNX provides.

    • i found the exact opposite, the pytorch version on the cpu barely does over 2 times realtime while i can get the onnx int8 version to reach 5x.

I love Kokoro. I use it to read ebooks that don't have audiobooks and it works pretty good for that. I have a Python script that reads epub/html, runs the model and writes mp3s.

Kokoro supports a limited number of languages. I've had to resort to other models to support Dutch, and they just aren't as good. And usually a lot slower and bigger (too big for my 8GB VRAM). I've had to resort to the Windows built-in TTS. It doesn't sound natural at all, but at least it can pronounce most words and is very fast.

I built a pipeline through hermes using edge-tts to automate and listen to links that I provide to it just this morning, google notebooklm style. I replaced the TTS model with Kokoro after seeing this post, thank you. Here's the pipeline if anyone is interested. https://www.klaweht.com/2026-07-07-link-to-podcast-rss-pipel... By the way, it took hermes just around 10-15 minutes to build first iteration. I am impressed.

I am entirely sold on Qwen3-TTS's voice cloning. It runs locally and I can run it as many times as I want.

Saw it first on reddit, and later I created a small project to generate audio books from epub. So far I've listened to couple of books generated this way and am quite satisfied with the quality. There is just one particular word I remember that it pronounced wrongly - "Malay".

Both Text-to-Speech and Speech-to-Text now have local models that are good enough to get the job done. Kokoro for TTS, Parakeet for STT and Fluid-1 for text formatting (I use it with FluidVoice). I hope this is a trend that continues for other applications.

It's interesting that the male voices are all so much worse than the female voices (several are quite good). There is bias in machine learning, but I wonder whether there is also systematically more training data of female speech?

Naive question, but I once downloaded a particular voice file that I wanted to use with some other RVC TTS project, but ended up not being able to run it CPU only, so I only kept the voice I wanted. Thing is, the voice is in .pth format, and on Kokoro's huggingface page, their voices are all .pt.

Would I be able to use this voice I already have with Kokoro? If not, is there any way to convert it? I could always go looking if someone made this specific voice but in .pt format, but I barely mess with AI and don't know how I could search for this.

  • Not super familiar but it seems to be technically possible.

    https://github.com/Ashish-Patnaik/kokoclone

    Generate audio with the voice and your first tool and use this to clone it into kokoro.

    The pth/pt extension bit isn’t the problem. Those are PyTorch extensions and they’re synonymous like jpeg/jpg.

    • That's great, thank you :-)

      With something like this I can even try to make a more accurate voice than the one I already have, and tailor it to my liking!

I use kokoro with home assistant and its great. I find its the most natural sounding and small too.

I speak over sonos speakers when certain events happen. And use it as my voice assistant.

This is Amazing and a game changer. Millions were spent during NLP era to achieve even <50% what this model offers.

Now this on a CPU is next level. When algorithms perform well on commodity hardware, the scale tips.

This gives hope that CPULLM's are not far off that'll be just fine for majority of use cases.

  • Just ran on Podman on a older hardware with intel CPU processor and ubuntu linux.

    When given a large text, it nicely chunked them up (debug statements showed), generated the audio and played back nicely.

    Well done!

Who is going to hack together a mac widget that allows us to select text anywhere, press a shortcut key and finally get a non robotic voice outputted in a reasonable amount of time?

I am aware of the Option + Esc shortcut on osx for the onboard TTS but wow is it hard to listen to in 2026.

  • Have you tried /usr/bin/say ? Might already have something sufficient for you - there’s quite a few voices there.

  • In System Settings, if you go to Accessibility and click "Read & Speak" in the "Vision" section, you can select a different voice using the "System voice" section. Click the "(i)" to preview your various options and even download more. Some, like "Allison (Enhanced)," sound leagues better than the default voice.

    • Great point! these are better than Samantha and they're free. But still, if I could wait a few seconds to get a much richer TTS experience I'd pay for that.

      1 reply →

kokoro is surprisingly great at nuance but it's tough to improve that last ~2% or so. kokoro + rvc is really great too; i use that for ELEMENT47, the LLM-centric comedy podcast i do that i wish more people would listen to. (e47.net , feel free to subscribe!)

I've used Piper for local TTS before, and Kokoro looks like an interesting

Another endorsement - I used Kokoro pretty extensively with an app I was developing over the last year and it's been excellent, both on- and off- GPU. Even with Elevenlabs (long time subscriber) the comparative quality of Kokoro keeps up really well until you get to their larger models with their professional voices.

I do wish there were better support for SSML, as well as deeper documentation of how to influence inflection in-line, but the default does well with standard emphasis (e.g. putting asterisks around text elements). Both asks are getting outside the zone of reasonable asks for this sort of distribution, though, and I remain incredibly grateful for the quality of what hexgrad and nazdridoy have put out in the world.

I just hooked it up to my personal AI Japanese Teacher app, pretty good quality / natural sounding speech in mixed English / Japanese while running fast on CPU so I don't waste VRAM.

I don't want to just spew AI-hate, but is an LLM actually necessary for this? I haven't worked with, but came across loads of non-AI TTS tools. Are these now exceptionally better to justify the overhead? Genuinely asking.

> Apple M2 Pro: 4.5 seconds

> AMD Ryzen 7 8745HS: 1.5 seconds

These two can probably do it much faster on their iGPUs.

  • Yep, and Kokoro-FastAPI (which he already uses) makes it super easy with start-gpu_mac.sh

It crashes as soon as you put a little paragraph of text on Apple M2 Pro.

Hard pass.

Why do these half baked projects get all the attention and thousands of clicks when it just takes a simple thing to bring the whole castle down?