Central Asia · Latin · oʻzbekcha
Uzbek subtitle generator
Use this Uzbek subtitle generator to transcribe oʻzbekcha audio locally in your browser, review the Latin cues and wording, then export SRT, VTT or TXT. The draft needs a fluent human review, and no account, upload or paid API is required.
By Abdul Samad · Last updated
Generate subtitles
Runs Whisper in your browser. No upload, no account, no credit card.
Choose a video or audio file
Drop it here, or click to browse. MP4, MOV, WEBM, MP3, WAV, M4A and similar formats.
Your file never leaves your device
Up to 500 MB. Files over 100 MB can be slow on phones.
Only transcribe media you own or have permission to use. VoiceToTextFree does not download media from other sites.
Auto-detect works for clear speech; choosing the language is faster and safer for accents.
Limits: 500 MB per file; speech must be audible; Whisper can struggle with music, overlapping voices and very noisy recordings. VoiceToTextFree does not upload files or send audio to a paid API.
Key facts
| Item | Detail |
|---|---|
| Language code | uz |
| Native name | oʻzbekcha |
| Script | Latin |
| Direction | Left to right |
| Region | Central Asia |
| Output | SRT, VTT and TXT |
What Uzbek transcription looks like
Uzbek is a Turkic language of Uzbekistan and neighbouring regions, written in Latin today with Cyrillic still in use. VoiceToTextFree runs Whisper in the browser, drafts Latin-script Uzbek and lets you edit cues before exporting SRT or VTT. The model may mix Russian or English insertions and does not promise romanized output for mixed speech or a consistent script when the source is bilingual.
Script and punctuation in Uzbek
Uzbek Latin uses the letter oʻ and the digraph gʻ, often typed with an apostrophe or a turned comma, plus sh and ch. Cyrillic Uzbek remains common in older texts and some media. Unlike many Turkic languages, standard Uzbek has largely lost vowel harmony, so suffixes are more predictable but still need checking.
Common Uzbek transcription pitfalls
The okina in oʻ and gʻ is typed inconsistently as an apostrophe or omitted, and the error is easy to miss in a long file. Cyrillic and Latin Uzbek may be mixed when the source or speaker switches, especially in older media and official contexts. Russian loanwords and code-switching may appear in Russian spelling, and the model may not mark the switch. Names and places have both Latin and Cyrillic forms, sometimes with different spellings that the model cannot reconcile. Fast speech can drop suffixes, and the model may not restore them even when the surrounding sentence implies them.
Tips for cleaner Uzbek subtitles
- Pick one okina character and use it for every oʻ and gʻ in the file, then check it in the player.
- Decide whether the file is Latin or Cyrillic before editing, then avoid mixing scripts within a cue.
- Keep a glossary of names and official terms in the chosen script, with one form per entry.
- Check Russian insertions against the audience's convention and apply the same rule throughout.
- Review numbers, dates and prices in a separate cue, since digit and word forms can look inconsistent.
- Ask an Uzbek reviewer to check a passage with oʻ and gʻ, where a missing okina changes the reading.
Line length and timing for Uzbek
Latin Uzbek fits about 32 to 40 characters per line. The okina adds width, and Russian insertions can make a line look dense, so keep to two lines and break at phrase boundaries. Confirm that the player renders the okina rather than a question mark or a blank box. Test a cue with oʻ and gʻ.
Who this Uzbek workflow helps
Useful for Uzbek interviews, vlogs, news clips, classroom recordings and family videos. It also helps translators who need a rough Latin or Cyrillic draft before a native editor checks names, script choice and Russian mixing, and it keeps the recording local during the draft stage.
A Uzbek cue with its English meaning
A short line transcribed as native script. Whisper generally returns the language's normal script, not a romanized version.
1
00:00:01,000 --> 00:00:04,000
Ertaga ertalab uchrashamiz.
2
00:00:04,200 --> 00:00:08,000
402-xona toʻrtinchi qavatda.Frequently asked questions
Does VoiceToTextFree support Uzbek?
Uzbek is in the multilingual Whisper tokenizer used by this site, so it can be selected and transcribed in the browser. This page has no reviewed sample, so accuracy is not claimed and the draft still needs a human review.
Does Whisper output Uzbek in Latin or Cyrillic?
Whisper normally returns Latin-script Uzbek, but it may produce Cyrillic when the audio or context points that way. It does not promise a transliteration between the two, so decide which script you need and check the whole file.
What is the correct character for oʻ and gʻ?
Uzbek Latin uses a modifier letter, often called an okina, rather than a plain apostrophe. Typing conventions vary, so choose one Unicode character and use it consistently. Check that the player and font display it correctly.
Does Uzbek have vowel harmony?
Standard Uzbek has largely lost the vowel harmony found in many other Turkic languages, so suffixes are less variable. That does not make every ending predictable, and the model can still drop or mix a suffix in fast speech.
Can I export Uzbek subtitles as SRT?
Yes. Edit the cues and download SRT, VTT or TXT as UTF-8. Test the okina and any Cyrillic insertions in the target player, because an encoding or font problem can turn the character into a box.
How accurate is Uzbek transcription?
No reviewed Uzbek sample has been recorded, so this page makes no tested accuracy claim. Okina handling, script mixing, Russian code-switching, audio quality and model size affect the result, so treat the draft as a first pass.
Sources and further reading
Abdul Samad — Creator and maintainer. About Abdul Samad.
Last updated · Published
Related guides
- How to improve Whisper accuracy for cleaner subtitlesHow to improve Whisper accuracy with better audio capture, explicit language selection, measured model sizes, overlap handling and a practical human review workflow.
- Right to left subtitles and non-Latin scripts: a practical guideRight to left subtitles need UTF-8, bidirectional text, correct punctuation, suitable fonts and player testing. A practical guide to RTL SRT and WebVTT.
- Subtitle best practices: a practical guide to cleaner captionsSubtitle best practices for real playback: clause-level segmentation, two-line limits, reading speed, punctuation, speaker IDs, SDH and a clean review pass.
Other languages
Languages in the picker: 99. The list is checked against the Whisper tokenizer by a unit test.