# Providing your own localization

**URL:** <https://community.cumulocity.com/t/providing-your-own-localization/12048>\
**Category:** Knowledge Base\
**Tags:** app-enablement\
**Created:** [March 20, 2025, 2:38pm UTC](https://community.cumulocity.com/t/providing-your-own-localization/12048 "2025-03-20T14:38:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tristan\_Bastian](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/tristan_bastian/32/18259_2.png) [@Tristan\_Bastian](https://community.cumulocity.com/u/Tristan_Bastian)\
**Post date:** [March 20, 2025, 2:38pm UTC](https://community.cumulocity.com/t/providing-your-own-localization/12048/1 "2025-03-20T14:38:18Z")

</div>

Cumulocity’s administration app offers the option to provide your own translations for certain texts. The process for doing so is described in the [documentation](https://cumulocity.com/docs/standard-tenant/changing-settings/#localization).

This user interface only allows to add further translations for already supported languages. At the time of writing this, the supported languages are: German, English, English (US), Spanish, French, Japanese, Korean, Dutch, Polish, Portuguese, Chinese and Chinese (Taiwan)

In case you would like to add support for a whole new language, you can also do so by utilizing the [`Advanced branding` tab of the Branding feature](https://cumulocity.com/docs/enterprise-tenant/customization/#advanced-branding-tab).

By adding the follwoing attribute to your JSON structure:

```auto
  "languages": {
    "de_CH": {
      "name": "German (CH)",
      "nativeName": "Deutsch (Schweiz)"
    }
  }

```

You could add for example swiss german to the supported languages.

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/cumulocity/original/3X/f/5/f532bd8761e923e6a0f0aa979ccd49c736e5dbbd.png)

After saving this change and applying this branding globally, you should be able to find the newly added language in the language settings and also in the localization user interface.

From there you can then go ahead and translate existing texts into your newly added language.

---

<div class="post-metadata">

**Author:** ![Harald\_Meyer](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/harald_meyer/32/1959_2.png) [@Harald\_Meyer](https://community.cumulocity.com/u/Harald_Meyer)\
**Post date:** [January 30, 2026, 2:42pm UTC](https://community.cumulocity.com/t/providing-your-own-localization/12048/2 "2026-01-30T14:42:46Z")

</div>

What are the requirements for the name of a new language?

We tried with “rg” and while this shows up in the localization dialog and as a language to select, translation actually fails with an error in the console about not being able to find “./rg.json” despite the translation.zip containing the file. If we use “en\_RG” instead it works.

---

<div class="post-metadata">

**Author:** ![Harald\_Meyer](https://dub1.discourse-cdn.com/flex005/user_avatar/community.cumulocity.com/harald_meyer/32/1959_2.png) [@Harald\_Meyer](https://community.cumulocity.com/u/Harald_Meyer)\
**Post date:** [February 3, 2026, 8:07am UTC](https://community.cumulocity.com/t/providing-your-own-localization/12048/3 "2026-02-03T08:07:24Z")

</div>

ok, confirmed internally. This does not support completely new languages.