Collapse Launcher ships with 17 built-in UI languages. Locale files are JSON documents stored in theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/CollapseLauncher/Collapse/llms.txt
Use this file to discover all available pages before exploring further.
Lang/ directory alongside the launcher executable. On first startup, the launcher automatically downloads the English fallback file (en_US.json) from the main GitHub repository if it is not already present.
Supported languages
| Locale ID | Language | Locale file |
|---|---|---|
en-US | English | en_US.json |
de-DE | German | de_DE.json |
es-419 | Spanish (Latin America) | es_419.json |
fr-FR | French | fr_FR.json |
id-ID | Indonesian | id_ID.json |
it-IT | Italian | it_IT.json |
ja-JP | Japanese | ja_JP.json |
ko-KR | Korean | ko_KR.json |
pl-PL | Polish | pl_PL.json |
pt-BR | Portuguese (Brazil) | pt_BR.json |
pt-PT | Portuguese (Portugal) | pt_PT.json |
ru-RU | Russian | ru_RU.json |
th-TH | Thai | th_TH.json |
uk-UA | Ukrainian | uk_UA.json |
vi-VN | Vietnamese | vi_VN.json |
zh-CN | Chinese (Simplified) | zh_CN.json |
zh-TW | Chinese (Traditional) | zh_TW.json |
If the launcher detects a Windows system locale that does not exactly match a supported locale ID, it falls back to the closest match. For example,
zh-HK and zh-MO fall back to Traditional Chinese (zh-TW), and most Portuguese variants fall back to pt-BR.Changing the UI language
Select your language
Choose your preferred language from the list. The selection is saved immediately to the
AppLanguage key in the config file.The launcher stores your language selection as a locale ID (for example,
ja-jp) in %USERPROFILE%\AppData\LocalLow\CollapseLauncher\config.ini under the AppLanguage key.Language fallback behavior
The locale system resolves language IDs with the following priority:- Exact match on the full locale ID (e.g.,
zh-TW). - Partial match on the language subtag only (e.g.,
zh→zh-CN). - Special-cased fallbacks for Traditional Chinese variants (
zh-HK,zh-MO,zh-TW→zh-TW) and Portuguese Portugal (pt-PT). - If all else fails, English (
en-US) is used.
Locale JSON file format
Each locale file is a UTF-8 JSON document. The top-level object contains a header and a set of section objects, each holding translated string keys.| Field | Description |
|---|---|
LanguageName | Human-readable name shown in the language selector. |
LanguageID | BCP 47 locale tag used to match Windows system locale. |
Author | Credit string shown in the launcher logs when the locale loads. |
| Section objects | Each section (e.g., _SettingsPage, _MainPage) holds the strings for that part of the UI. |
Size prefixes
The special_Misc.SizePrefixes1000U field defines the localized size suffixes used throughout the UI (download sizes, file sizes, etc.). It must contain exactly 9 entries separated by |, \, /, #, $, or ! characters. Example:
Contributing translations
Collapse Launcher translations are managed on Transifex: https://explore.transifex.com/collapse-launcher/collapse-launcher/ If you prefer to contribute directly, you can open a pull request against theHi3Helper.Core/Lang/ directory in the Collapse GitHub repository. Follow the existing JSON structure exactly, including section names and key names.
Adding a custom locale file
You can drop an additional.json file into the Lang/ directory next to the executable and it will appear in the language selector on the next launch. The file must include at minimum the LanguageName, LanguageID, and Author fields to be loaded correctly. Missing string keys fall back to their English equivalents from en_US.json.