Skip to main content

Localization

ChurchCRM supports 46 languages. The application language is configured in Admin → General Settings → Localization.

Select the appropriate language from the dropdown and save the settings. The interface will switch to the selected language immediately.

Note: Translations are community-contributed and may be incomplete for some languages. If you encounter untranslated strings, the text will fall back to English.

Features​

Browser language auto-detection​

When an unauthenticated user visits ChurchCRM (e.g., the login page), the application detects the browser's preferred language and displays the UI in that language automatically — if a translation exists. No configuration is required. Once a user logs in, their saved locale preference takes effect.

Regional locale grouping​

The language chooser now groups locales by world region (Americas, Europe, Asia, Africa, etc.) and shows each language's native name alongside the English label. This makes it much easier to find the right locale in a long list.

Per-user locale override​

Each user can set their own preferred language in My Settings → Localization, overriding the system-wide default. This allows multilingual teams to work in their own language on the same installation.

How to translate ChurchCRM (brief)​

If you'd like to contribute translations or add a new language, follow this short workflow:

  1. Extract terms:
npm run locale:build
# produces: locale/terms/messages.po
  1. Translate:
  • Recommended: Upload locale/terms/messages.po to POEditor (project-managed translations) and translate there.
  • Alternative: Edit the .po file locally with Poedit or similar.
  1. Download & build translated assets:
npm run locale:download
npm run deploy   # or npm run build

  1. Restart webserver / containers so PHP picks up installed .mo files.

  2. Verify:

  • Use Admin → System → Debug and open the Locale Support card to confirm the OS locale is installed and translations are available.
  • Browse the UI to confirm translated strings render correctly.
  1. Commit & publish:
  • Commit locale/terms/messages.po (and generated frontend JSON if your workflow requires it) and open a PR, or sync via POEditor integration.

For a complete developer-oriented guide (commands, POEditor API examples, and troubleshooting), see the Localization management guide: https://github.com/ChurchCRM/CRM/wiki/Localization