How to Suggest Changes to Minecraft Bedrock Translation Files (.lang)
Quick Answer: Translation contributions for vanilla Minecraft go through Crowdin. For addon-specific .lang files in bedrock-samples, submit a Pull Request to the Mojang/bedrock-samples repository on GitHub.
Details
Issue #77 asks how to contribute corrections or improvements to translation files, specifically referencing paths like /resource_pack/texts/uk_UA.lang in the bedrock-samples repository.
Two Different Translation Systems
1. Vanilla Minecraft Translations (Crowdin)
All official game text — item names, block names, UI strings, tutorial text — is managed on Crowdin. This is a community translation platform where anyone can suggest improvements, vote on translations, and discuss context. Changes accepted here eventually ship in official game updates.
2. Bedrock Samples Repository Translations (GitHub)
The Mojang/bedrock-samples repository contains example resource packs with their own texts/ folders containing .lang files. These are sample translations for demonstration purposes only — they don’t affect the actual game. To suggest changes here:
- Fork the
Mojang/bedrock-samplesrepository - Navigate to the relevant
resource_pack/texts/file.lang - Make your corrections (fix typos, improve phrasing, add missing keys)
- Submit a Pull Request with a clear description of what you changed and why
.lang File Format
Language files use a simple key=value format:
# Comments start with #
item.diamond_sword.name=Diamond Sword
block.diamond_block.name=Diamond Block
death.attack.lava=died in lavaImportant: Language codes follow ISO 639-1 (two-letter language) + ISO 3166-1 (two-letter country), e.g., en_US, uk_UA, zh_CN.
For Your Own Addons
If you’re developing an addon and want to support multiple languages, create a texts/ folder in your resource pack with .lang files for each language. The game will automatically load the correct file based on the player’s language setting.
Last updated: 2026-07-17
