Short answer
Aelano currently supports transcription in 100+ languages.
That matters because this is not only a UI translation list. It means the app can directly process source content in a broad set of languages and turn it into something learnable with subtitles, translation, and repeatable practice.
Current transcription languages
- Chinese (zh, 中文)
- Cantonese (yue, 粤语)
- English (en, 英语)
- Japanese (ja, 日语)
- Korean (ko, 韩语)
- German (de, 德语)
- French (fr, 法语)
- Russian (ru, 俄语)
- Spanish (es, 西班牙语)
- Italian (it, 意大利语)
- Vietnamese (vi, 越南语)
- Indonesian (id, 印尼语)
- Thai (th, 泰语)
- Malay (ms, 马来语)
- Filipino (fil, 菲律宾语)
- Arabic (ar, 阿拉伯语)
- Bengali (bn, 孟加拉语)
- Hindi (hi, 印地语)
- Bulgarian (bg, 保加利亚语)
- Croatian (hr, 克罗地亚语)
- Czech (cs, 捷克语)
- Danish (da, 丹麦语)
- Dutch (nl, 荷兰语)
- Estonian (et, 爱沙尼亚语)
- Finnish (fi, 芬兰语)
- Greek (el, 希腊语)
- Hungarian (hu, 匈牙利语)
- Irish (ga, 爱尔兰语)
- Latvian (lv, 拉脱维亚语)
- Lithuanian (lt, 立陶宛语)
- Maltese (mt, 马耳他语)
- Norwegian (no, 挪威语)
- Polish (pl, 波兰语)
- Portuguese (pt, 葡萄牙语)
- Romanian (ro, 罗马尼亚语)
- Nepali (ne, 尼泊尔语)
- Slovak (sk, 斯洛伐克语)
- Slovenian (sl, 斯洛文尼亚语)
- Swahili (sw, 斯瓦希里语)
- Swedish (sv, 瑞典语)
- Turkish (tr, 土耳其语)
- Ukrainian (uk, 乌克兰语)
- Afrikaans (af, 南非荷兰语)
- Amharic (am, 阿姆哈拉语)
- Armenian (hy, 亚美尼亚语)
- Assamese (as, 阿萨姆语)
- Asturian (ast, 阿斯图里亚斯语)
- Azerbaijani (az, 阿塞拜疆语)
- Belarusian (be, 白俄罗斯语)
- Bosnian (bs, 波斯尼亚语)
- Burmese (my, 缅甸语)
- Catalan (ca, 加泰罗尼亚语)
- Cebuano (ceb, 宿务语)
- Chichewa (ny, 齐切瓦语)
- Fulah (ff, 富拉语)
- Galician (gl, 加利西亚语)
- Ganda (lg, 卢干达语)
- Georgian (ka, 格鲁吉亚语)
- Gujarati (gu, 古吉拉特语)
- Hausa (ha, 豪萨语)
- Hebrew (he, 希伯来语)
- Icelandic (is, 冰岛语)
- Igbo (ig, 伊博语)
- Javanese (jv, 爪哇语)
- Kabuverdianu (kea, 佛得角克里奥尔语)
- Kannada (kn, 卡纳达语)
- Kazakh (kk, 哈萨克语)
- Khmer (km, 高棉语)
- Kurdish (ku, 库尔德语)
- Kyrgyz (ky, 吉尔吉斯语)
- Lao (lo, 老挝语)
- Lingala (ln, 林加拉语)
- Luo (luo, 卢奥语)
- Luxembourgish (lb, 卢森堡语)
- Macedonian (mk, 马其顿语)
- Malayalam (ml, 马拉雅拉姆语)
- Maori (mi, 毛利语)
- Marathi (mr, 马拉地语)
- Mongolian (mn, 蒙古语)
- Northern Sotho (nso, 北索托语)
- Occitan (oc, 奥克语)
- Odia (or, 奥里亚语)
- Pashto (ps, 普什图语)
- Persian (fa, 波斯语)
- Punjabi (pa, 旁遮普语)
- Serbian (sr, 塞尔维亚语)
- Shona (sn, 修纳语)
- Sindhi (sd, 信德语)
- Somali (so, 索马里语)
- Tamil (ta, 泰米尔语)
- Tajik (tg, 塔吉克语)
- Telugu (te, 泰卢固语)
- Umbundu (umb, 翁本杜语)
- Urdu (ur, 乌尔都语)
- Uzbek (uz, 乌兹别克语)
- Welsh (cy, 威尔士语)
- Wolof (wo, 沃洛夫语)
- Xhosa (xh, 科萨语)
- Yoruba (yo, 约鲁巴语)
- Zulu (zu, 祖鲁语)
What this means in practice
For most learners, the useful question is not "does the site have my interface language?" It is "can the app process the content I actually want to learn from?"
This coverage means you can work with much more than just English, Chinese, Japanese, or Korean content. It also gives you room to learn from podcasts, interviews, lectures, and videos in many commonly studied Asian and European languages.
Why this is different from basic subtitle tools
Basic subtitle tools may help you extract text. Aelano is designed to turn that text into a learning workflow:
- import content you already care about
- generate subtitles and translation
- study in segments instead of one long block
- review and repeat until difficult parts become familiar
So the language list matters because it expands the range of content that can become real study material.
If your target language is not obvious yet
The practical test is simple:
- Start from content you already want to understand.
- Import that content into Aelano.
- Check whether the transcription and segment-based practice fit your learning goal.
That is usually a better decision path than picking a language app first and forcing your study habits to match it.