Key Takeaways
- Piper: originally from the Rhasspy/Home Assistant ecosystem, now maintained by the Open Home Foundation; ONNX Runtime-based; runs comfortably on a Raspberry Pi with no GPU.
- Kokoro: an 82-million-parameter model by hexgrad, StyleTTS2-and-ISTFTNet-derived, Apache-2.0 licensed; runs well on CPU or a modest GPU.
- Neither engine performs zero-shot voice cloning; both ship fixed sets of pretrained voices.
- Piper license: GPL-3.0-or-later (current repo); original archived repo was MIT. Kokoro license: Apache-2.0.
- Piper wins on raw speed and minimal resource use; Kokoro is widely reported as more natural-sounding in community listening comparisons.
- Use Piper for embedded/edge devices and voice assistants; use Kokoro when audio quality matters more than squeezing onto the smallest possible hardware.
π In One Sentence
Piper is the faster, lighter local text-to-speech engine that runs on a Raspberry Pi with no GPU (GPL-3.0-or-later license), while Kokoro is an 82-million-parameter open-weight model (Apache-2.0) that trades some speed for noticeably more natural-sounding audio; neither clones voices from a sample.
π¬ In Plain Terms
Both turn text into spoken audio entirely on your own computer, with no cloud API call. Piper is smaller and quicker, so it works on cheap hardware like a Raspberry Pi, but sounds a bit more robotic. Kokoro is a slightly bigger model that sounds noticeably more human, at the cost of needing a bit more computing power.
πNote: Neither Piper nor Kokoro clones a voice from a short reference clip. For that capability, see PromptQuorum's XTTS v2 review β note that XTTS v2's license is non-commercial, unlike Piper and Kokoro.
What Each Engine Actually Is
Piper and Kokoro solve the same basic problem β turning text into spoken audio on local hardware, with no data leaving the machine β but they come from different lineages and make different size-versus-quality trade-offs.
- Piper is a neural text-to-speech engine, originally created by Michael Hansen inside Rhasspy, an open-source toolkit for offline voice assistants. It converts text to phonemes with espeak-ng, then synthesizes a waveform from those phonemes using a VITS-style model exported to ONNX Runtime for fast inference, including on CPU-only hardware. It became the default local TTS engine in Home Assistant's voice pipeline and is now maintained by the Open Home Foundation at OHF-Voice/piper1-gpl. PromptQuorum covers it in full in a dedicated Piper review.
- Kokoro is an 82-million-parameter open-weight TTS model released on Hugging Face by the developer known as hexgrad. Its architecture is built on StyleTTS 2 with an ISTFTNet vocoder, using a decoder-only design without a diffusion step β a smaller, simpler pipeline than many higher-parameter-count TTS models. According to its Hugging Face model card, it was trained on a few hundred hours of permissively licensed or public-domain audio, and version 1.0 was released January 27, 2025.
- Neither model clones a voice from a short reference clip. Piper and Kokoro each ship a fixed, pretrained set of voices you select from β a fundamentally different capability from a voice-cloning model like XTTS v2, which synthesizes speech in a new voice from 6 seconds of sample audio, but under a non-commercial license.
- Both run fully offline, on your own hardware. No text or audio is sent to a cloud API by either engine β the entire synthesis pipeline runs locally, which matters for privacy-sensitive applications and for avoiding per-character cloud TTS costs.
Piper vs Kokoro: Side-by-Side
Piper wins on speed and minimal hardware footprint; Kokoro wins on perceived audio quality. The table below summarizes the real trade-offs β treat the "Voice quality" row as a qualitative, widely reported community impression rather than a specific benchmark score, since PromptQuorum could not locate a single authoritative head-to-head numeric benchmark comparing the two directly.
Origin / maintainer
- Piper:
- Rhasspy project β Open Home Foundation
- Kokoro:
- Independent developer (hexgrad)
Parameter count
- Piper:
- Not published as a single headline figure (VITS-style, per-voice models)
- Kokoro:
- 82 million parameters
Architecture
- Piper:
- VITS-style, ONNX Runtime
- Kokoro:
- StyleTTS 2 + ISTFTNet, decoder-only
License
- Piper:
- GPL-3.0-or-later (current repo)
- Kokoro:
- Apache-2.0
Hardware needs
- Piper:
- CPU-only, real time on a Raspberry Pi
- Kokoro:
- CPU or modest GPU
Voice quality (community reports)
- Piper:
- Fast, decent for its size, more robotic-adjacent
- Kokoro:
- Widely reported as more natural / expressive
Voice cloning
- Piper:
- No β fixed pretrained voices
- Kokoro:
- No β fixed pretrained voices
Install
- Piper:
pip install piper-tts- Kokoro:
pip install kokoro
Real Usage Examples
These commands use each project's own documented install and API pattern. Check each project's current GitHub/Hugging Face documentation before deploying, since CLI flags and package names can change between releases.
- Piper is the faster startup. Its per-voice ONNX models load quickly and synthesis is near-instant on CPU, which is why it is the common choice for interactive voice assistants on constrained hardware.
- Kokoro's pipeline groups synthesis into chunks (the
gs/ps/audiotuple above), which is worth knowing before assuming a single call returns one continuous audio buffer for long text.
# ββ Piper: install and synthesize βββββββββββββββββββββββββββββ
pip install piper-tts
python3 -m piper.download_voices en_US-lessac-medium
python3 -m piper -m en_US-lessac-medium -f test.wav -- "This is a test."
# Piper Python API
from piper import PiperVoice
voice = PiperVoice.load("en_US-lessac-medium.onnx")
with open("test.wav", "wb") as wav_file:
voice.synthesize_wav("Fast, local speech synthesis.", wav_file)
# ββ Kokoro: install and synthesize ββββββββββββββββββββββββββββ
pip install kokoro soundfile
# Kokoro Python API (per hexgrad/Kokoro-82M on Hugging Face)
from kokoro import KPipeline
import soundfile as sf
pipeline = KPipeline(lang_code="a") # "a" = American English
generator = pipeline(
"Kokoro produces noticeably natural-sounding speech from a small model.",
voice="af_heart",
)
for i, (gs, ps, audio) in enumerate(generator):
sf.write(f"output_{i}.wav", audio, 24000)License and Cost
Piper's actively maintained repository, OHF-Voice/piper1-gpl, is licensed under GPL-3.0-or-later. This is a change from the original rhasspy/piper repository, which was MIT-licensed before it was archived (made read-only) on October 6, 2025 and remains available under that MIT license, unmaintained. GPL-3.0 is a copyleft license: you can use Piper for free, including commercially, to generate speech, but if you distribute a modified version of Piper's own source code, you must release that modification under the same GPL-3.0 terms. Using Piper as an unmodified external tool (its CLI, Python package, or web server called as a separate process) generally does not place the rest of your application under GPL, but the exact boundary depends on how tightly your code is linked to Piper's β this is not legal advice, consult a lawyer for your specific deployment.
Kokoro is licensed Apache-2.0, confirmed on its Hugging Face model card. Apache-2.0 is a permissive license with no copyleft obligations β you can use, modify, and redistribute Kokoro, including in closed-source commercial products, without being required to release your own source code, subject to the license's standard attribution and patent-grant terms.
Neither engine has a paid tier, subscription, or license fee. The only costs are the hardware you run them on and your own development time. If you instead want a managed, paid cloud TTS API with commercial voice cloning, see PromptQuorum's ElevenLabs vs local TTS comparison.
Is Kokoro TTS free for commercial use?
Yes. Kokoro is licensed Apache-2.0, a permissive license with no copyleft obligations, so it can be used in closed-source commercial products without releasing your own source code, subject to the license's standard attribution and patent-grant terms. This is not legal advice β read the Apache-2.0 license yourself before a commercial deployment.
Is Piper free for commercial use?
Yes, generating speech with Piper is free for commercial use. Its current license, GPL-3.0-or-later, is a copyleft license that only imposes conditions if you distribute a modified version of Piper's own source code β using it as an external tool generally does not place your own application's other code under GPL. This is not legal advice β consult a lawyer for your specific deployment.
Who Should Use Which
Pick Piper for embedded devices, voice assistants, and any deployment where CPU cycles or memory are tightly constrained. Pick Kokoro when audio quality is the priority and you have at least a modest CPU or GPU budget to spend on it.
- Choose Piper if: you are running on a Raspberry Pi or similarly constrained device, need the lowest possible latency-to-first-audio, or are integrating with Home Assistant's voice pipeline, where Piper is the default local TTS engine.
- Choose Kokoro if: you are producing audiobooks, narration, or any content where listeners will notice robotic-sounding speech, and you have CPU or GPU headroom beyond the absolute minimum.
- Choose neither, and see XTTS v2 instead, if: you need to clone a specific person's voice from a short reference clip β both Piper and Kokoro use fixed pretrained voices only, and neither performs voice cloning. See PromptQuorum's XTTS v2 review (non-commercial license) or the local TTS licensing guide for cloning-capable alternatives and their licenses.
- Choose neither, and see the ElevenLabs comparison instead, if: you need commercial-grade voice cloning with a clear paid license and do not want to self-host. See PromptQuorum's ElevenLabs vs local TTS comparison.
What Neither Is Good For
Piper and Kokoro are both fixed-voice, non-cloning TTS engines. Neither is the right tool for the following situations:
- Cloning a specific person's voice from a sample clip. Both engines ship pretrained voices only β there is no mechanism in either to generate speech in a new, previously unheard voice from a short reference recording. See XTTS v2 instead, noting its non-commercial license.
- Emotionally expressive, non-speech audio (laughter, sighs, ambient sound). Both engines synthesize speech, not the broader expressive audio range that a model like Bark targets.
- Maximum possible audio fidelity regardless of resource cost. For readers who specifically want the highest-quality English narration and are not resource-constrained, PromptQuorum's StyleTTS 2 review covers a model with a comparable underlying architecture to Kokoro but a different size/quality trade-off.
- A GPL-3.0 codebase inside a closed-source product that modifies Piper's own source. If your deployment plan involves forking or statically linking modified Piper source code into a closed-source binary, Piper's current GPL-3.0-or-later license is a real constraint β Kokoro's Apache-2.0 license does not have this restriction.
Alternatives
XTTS v2
- Best fit:
- Voice cloning from 6 seconds of reference audio
- License:
- CPML (non-commercial)
Coqui TTS toolkit
- Best fit:
- The software that runs XTTS v2 and other models
- License:
- MPL-2.0 (toolkit only)
Bark
- Best fit:
- Expressive, non-speech audio β laughter, sighs, ambient sound
- License:
- MIT
StyleTTS 2
- Best fit:
- Highest natural-sounding English narration (no voice cloning)
- License:
- MIT
ElevenLabs
- Best fit:
- Managed cloud API with commercial voice cloning
- License:
- Proprietary (paid cloud API)
Frequently Asked Questions
What is the main difference between Piper and Kokoro TTS?
Piper is a lightweight, fully local neural TTS engine optimized for speed and minimal resource use β it runs in real time on CPU-only hardware including a Raspberry Pi. Kokoro is an 82-million-parameter open-weight model that produces noticeably more natural-sounding audio, at the cost of needing somewhat more computing power, though it still runs on CPU or a modest GPU.
Which sounds more natural, Piper or Kokoro?
Kokoro is widely reported as more natural-sounding than Piper in community listening comparisons. PromptQuorum could not locate a single authoritative, independently verified numeric benchmark comparing the two engines head-to-head, so treat this as a qualitative, widely reported community impression rather than a measured score.
Does Piper or Kokoro support voice cloning?
No. Both engines ship a fixed set of pretrained voices you select from β neither clones a new voice from a short reference audio sample. For voice cloning, see PromptQuorum's XTTS v2 review, noting its non-commercial license.
Can I run Kokoro without a GPU?
Yes. Kokoro, at 82 million parameters, runs on CPU, though a modest GPU speeds up synthesis. It does not require GPU hardware the way larger TTS or voice-cloning models often do.
Can Piper run on a Raspberry Pi?
Yes β real-time, CPU-only synthesis on a Raspberry Pi is one of Piper's primary design goals, and it is the default local text-to-speech engine in Home Assistant's voice pipeline, which frequently runs on Raspberry Pi hardware.
What license does Kokoro use?
Kokoro is licensed under Apache-2.0, a permissive license with no copyleft obligations, confirmed on its Hugging Face model card. It can be used in closed-source commercial products without releasing your own source code, subject to the license's standard attribution and patent-grant terms.
What license does Piper use?
Piper's actively maintained repository (OHF-Voice/piper1-gpl) is licensed under GPL-3.0-or-later. The original, now-archived rhasspy/piper repository was MIT-licensed. GPL-3.0 only imposes conditions if you distribute a modified version of Piper's own source code; using Piper as an external tool generally does not place your own application under GPL.
Who maintains Piper and Kokoro?
Piper was originally created by Michael Hansen inside the Rhasspy voice-assistant project; active development is now maintained by the Open Home Foundation, the nonprofit organization behind Home Assistant. Kokoro was released by the developer known as hexgrad and is distributed via Hugging Face.
How many languages do Piper and Kokoro support?
Kokoro's 54 built-in voices, per its Hugging Face model card, span 8 languages and accent groups including American and British English, Spanish, French, Hindi, Italian, Japanese, Brazilian Portuguese, and Mandarin Chinese. Piper's voice catalog is larger and more fragmented β dozens of languages and regional variants contributed by different community members, with quality varying by voice.
Verdict
Piper and Kokoro are not competing for the exact same job. Piper is the right choice when the constraint is hardware β a Raspberry Pi, an embedded device, a voice assistant that must respond instantly on CPU alone β and its GPL-3.0-or-later license is free to use commercially as long as you are not redistributing modified Piper source code. Kokoro is the right choice when the constraint is audio quality: at 82 million parameters it is still small and CPU-friendly, but community listening comparisons consistently describe it as more natural-sounding than Piper, and its Apache-2.0 license has no copyleft restrictions at all. Neither tool clones a voice from a sample clip β if that is the actual requirement, this comparison is not the answer; see PromptQuorum's XTTS v2 review instead, or the ElevenLabs comparison for a managed commercial option. If unsure, start with Piper for the lowest-friction install and fastest results, and move to Kokoro if the output quality does not meet your bar.
Sources
- Kokoro-82M on Hugging Face β the model card: parameters, architecture, license, voices, and release date.
- hexgrad/kokoro on GitHub β the Kokoro pipeline source and API documentation.
- OHF-Voice/piper1-gpl on GitHub β the actively maintained Piper repository, its license, and documentation.
- rhasspy/piper on GitHub β the original, now-archived MIT-licensed repository.
- Piper TTS Review β PromptQuorum's dedicated review of Piper, including its 2025 relicensing history.
