How to fix react-i18next missing translation keys from a malformed excel export
- Step 1Check your Excel translation spreadsheet — Confirm you have a key column (e.g. 'key') and a value column (e.g. 'en') with the correct translations.
- Step 2Upload and configure key/value columns — Enter the key and value column names. Enable nested mode for dot-notation key expansion.
- Step 3Download and replace your locale file — Save the output as en.json (or your locale code) and replace the broken file in your i18n directory.
Frequently asked questions
Why does i18next show the raw key instead of the translation?+
The key is not found in the loaded JSON. This happens when the JSON file has wrong nesting, missing keys, or a parse error. Regenerate from the Excel source using this tool.
Should I use flat or nested JSON for react-i18next?+
Both work. Nested JSON is more readable; flat JSON is simpler to generate. The tool supports both modes.
Does it validate that keys don't conflict (e.g. 'auth' as both a string and an object)?+
Conflicting keys (a key used as both a string value and a parent namespace) produce a warning in the output console.
Privacy first
Every JAD Excel tool runs entirely in your browser using SheetJS and ExcelJS. Your spreadsheets, formulas, and data never leave your device — verified by zero outbound network requests during processing.