> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/consent-management-platform-cmp/consent-notices/customize-consent-notice-language.md). # Customize consent notice language Didomi SDK supports multiple languages out-of-the-box, with translations for all standard messages. The language in which the consent notice will be displayed is the language used by the browser, if enabled. Enabling a language allows the user to see the consent notice in that language. Users on browsers using language that is not enabled will see the notice in English by default. You can change enabled languages in the Didomi Console. * Go to the **Consent Notices** section and find your consent notice. * Go to the "**Customization**" step. * The default language is the language seen by default if the user browser is using a language not enabled by your notice. * Enabled languages are the languages you have chosen to make available.
🔎 Our consent management platform is available [in 65 languages.](https://developers.didomi.io/api/introduction/translations#languages-supported) If you would like to display your consent banner in a language that is not currently supported, please contact . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.didomi.io/consent-management-platform-cmp/consent-notices/customize-consent-notice-language.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.