Which language should Inflect support next?

Help choose Inflect’s first language expansion. Only one required question, under 30 seconds.

Inflect v2 currently provides two extremely small English TTS models:

Inflect-Micro-v2: 9.36M parameters, best overall quality
Inflect-Nano-v2: 3.96M parameters, smallest footprint

The new adaptation toolkit makes additional fixed-voice languages possible. This vote will help determine which language should receive the first focused adaptation effort.

The final decision will also depend on legally usable speech data, frontend and phonemization readiness, compute requirements, and reliable evaluation by fluent speakers.

Voting closes Sunday, August 2, 2026 at 11:59 PM Pacific Time.

Does not require an account, email address, name, username, or contact information.

Which language should Inflect prioritize first?

How familiar are you with the language you selected?

Native speaker

Fluent non-native speaker

Intermediate or currently learning

I do not speak it

After language support, what should Inflect prioritize next?

Additional built-in voices

Better names, numbers, abbreviations, and pronunciation

Higher speech quality and naturalness

Faster CPU and browser inference

Mobile and C++ deployment

Native streaming and improved long-form speech

Easier voice fine-tuning

Continue reducing model size

Is there anything specific you would like Inflect to handle better?

Examples include a language, pronunciation problem, deployment target, voice type, or use case.