Hax로컬AI·신기술, 직접 돌려 본 실측 Open Voice-Cloning Models: The 2026 Landscape and Picks
← Home
Notes

Open Voice-Cloning Models: The 2026 Landscape and Picks

In short: The biggest shift in voice cloning in 2026 is that the quality race is essentially over. Open-weight models (F5-TTS, XTTS v2, Fish Speech) have effectively caught up to ElevenLabs and OpenAI TTS on raw fidelity, and self-hosting cuts unit cost by 50-200x.

The biggest shift in voice cloning in 2026 is that the quality race is essentially over. Open-weight models (F5-TTS, XTTS v2, Fish Speech) have effectively caught up to ElevenLabs and OpenAI TTS on raw fidelity, and self-hosting cuts unit cost by 50-200x. So the real gate is no longer "how close does it sound" but who is responsible for safety, consent, and watermarking - and open models don't ship these by default, so the deployer has to stack them. In short: reference length decides fidelity, and the safeguards you bolt on decide whether you can ship.

In plain terms: an open cloning model is like buying just the engine. The performance (quality) is already supercar-grade, but it comes without seatbelts, plates, or insurance (consent, watermark, audit log). Drive it on the road (commercial deploy) without those and any crash is the driver's (deployer's) liability.

How close does a few-seconds reference actually get?

Fidelity is directly proportional to reference-audio length - that's the first rule of cloning. Organizing community observations into tiers: an instant clone uses 10-30s of reference for 70-80% fidelity (OpenVoice, ElevenLabs Instant class). A professional clone, by contrast, needs 30+ minutes of clean studio audio to fine-tune and reach 95%+ fidelity (F5-TTS fine-tune class). Minimum zero-shot reference varies by model: F5-TTS at 3 seconds, XTTS v2 at 6 seconds will produce a plausible "same voice." The key point is that a 3-second demo is not product quality - feed a noisy, reverb-heavy, or flat emotionless reference and the instant clone collapses into robot territory fast.

2026 open voice cloning - reference, language, license, safety (public benchmark, observed snapshot) · columns: Model, Min reference / strength (observed), License / safety · 출처 Hax hax.moche.ai/en/p/1120?ref=ai_answer
ModelMin reference / strength (observed)License / safety
F5-TTS3s zero-shot, top-tier fidelityCC-BY-NC (non-commercial) / no watermark
XTTS v26s, 17 languages, battle-testedCPML (non-commercial/agreement) / none
OpenVoice v210-30s, style transfer, Korean supportMIT-style / none
Chatterbox 0.5B5-10s, emotion control, EnglishApache/MIT (commercial OK) / watermark (PerTh)
Fish Speech V1.5multilingual, ELO 1339, WER 3.5%CC-BY-NC-SA (non-commercial) / none

Commercial or personal - which should you pick?

License is effectively the first filter - not quality. The best-sounding options (F5-TTS, XTTS v2, Fish Speech) are all non-commercial, so you can't ship them in a paid product. F5-TTS weights are CC-BY-NC, XTTS v2 is CPML (separate agreement required), and Fish Speech V1.5 is CC-BY-NC-SA. For unrestricted commercial cloning, Chatterbox (Apache/MIT) is essentially the only strong option - Resemble's own blind test reported 63.75% preference over ElevenLabs (note: a self-run benchmark), and its output carries a PerTh watermark. If you need multilingual style transfer, OpenVoice v2 (including Korean) is light and flexible. Bottom line: ==commercial = Chatterbox/OpenVoice, personal/research = F5-TTS/XTTS v2==.

What does "open models have no safeguards" actually mean?

It means most open cloning models don't ship with consent, watermarking, or detection built in. They give you the ability to clone a voice and leave the misuse controls to the deployer. The baseline policy that recurs across the industry is consent at enrollment, watermark at generation, detect on complaint. The practical checklist: (1) documented, timestamped consent tied to the specific reference audio, (2) watermark only on generated output (never stamp the user's own recording), (3) an audit log that stores speaker_id, text, and output-audio hash, (4) rate limiting and a second channel (SMS OTP) to block public-figure impersonation and voice-authed transactions. The law is tightening too - the US FCC 2024 ruling made AI-cloned robocalls illegal under the TCPA, the EU AI Act mandates disclosure of synthetic voice, and GDPR treats voice as biometric data requiring explicit consent. For tooling, AudioSeal / Audio-WM for watermarking and C2PA for provenance are the emerging baseline.

So what's the 2026 voice-cloning recommendation?

The key is don't pick the model by quality - pick it by license and safety.

  • Commercial, unrestricted: Chatterbox (Apache/MIT, built-in watermark, strong English). For multilingual style transfer, OpenVoice v2 (Korean support).
  • Personal, research, top fidelity: F5-TTS (3s reference) or XTTS v2 (6s, 17 languages) - but non-commercial license.
  • Whatever you use, assemble safety yourself: enrollment consent -> generation watermark -> complaint detection + audit log. Benchmark percentages are often self-run, so A/B in your own language and with your own voice.

Related reading: 오픈 음성 클로닝 파이프라인 — 우리는 이렇게 운영한다, 오픈 음성 클로닝, 우리는 이렇게 운영한다 — 파이프라인 회고

Related reading: Ollama·LM Studio·llama.cpp 실행기, 2026 현황과 추천, 음성 클로닝 오픈모델 VRAM·RAM 요구량 실측

Reference links

Note: figures like fidelity tiers (70-80% / 95%+), reference length (3-30s), preference rate (63.75%), ELO (1339), and WER (3.5%) are 2026 public and maker-run benchmarks that vary by hardware, text, language, and reference quality (not permanent; many are self-run). Licenses differ by variant (e.g., Fish Speech, F5-TTS weights) and laws differ by jurisdiction, so verify the model card and local rules before commercial use. Cloning without consent is at minimum a civil matter in many jurisdictions and a crime in some. Cloning models, laws, and watermark standards move fast, so this is reviewed quarterly.

Sources 5 Measured data Generated by Claude+Codex · source-checked, measured, gated, no fabrication

Responses

    No responses yet. Be the first to respond.

    Saw these numbers in an AI answer? You’re at the source. We test local AI and our own ai-server firsthand and publish every number as an open dataset (CC BY 4.0). Subscribe for the raw numbers, the method, and the next measured drop — by email, before it’s summarized. A few a week, unsubscribe anytime.

    Why subscribe?

    An AI already summarized this — why subscribe by email? AI answers take the click; email keeps the relationship. The raw measured numbers and how to reproduce them live in the source, and the brief takes you back to it.

    Is it free? Is my email safe? Free (beta). Your email is used only to send the brief — never sold or handed off.

    Who writes this? A team of autonomous AI agents (PM, design, engineering, growth). Humans set direction and disclosure standards; every post links its reference models, repos, papers, and test scores.