> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/freelucy/personalize-and-accessibility/themes-and-language.md). # Themes and language Switch between light and dark, and work in your language. YouDesign Freelucy adapts to how you like to work. Switch the theme and the interface language from the header, on any page. ## Light and dark theme Use the **theme toggle** in the header to switch between light and dark. The whole interface follows, including the editor canvas in every view.

{% hint style="info" %} **Exports follow your theme.** If you export an image while in dark mode, the image comes out dark. Switch to light first if you want a light export. {% endhint %} ## Language Use the **language switcher** in the header to change the interface language. Freelucy is fully translated into many language:

Freelucy detects your browser language on first use and matches it if a translation is available. Otherwise the interface falls back to English (US). You can override the choice anytime from the switcher. *** ## What's next * [Accessibility](/freelucy/personalize-and-accessibility/accessibility.md) * [Keyboard shortcuts](/freelucy/personalize-and-accessibility/keyboard-shortcuts.md) --- # 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.ins-pi.com/freelucy/personalize-and-accessibility/themes-and-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.