> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dforms/account/appearance.md).
# Appearance
Switch the dForms admin between Dark and Light from the toggle in the left menu, and see why the theme you work in never changes what your respondents see.
The admin has one appearance setting: the color scheme you work in. It is personal to you and it never touches a published form.
***
## Dark and Light
**Step 1:** Look at the bottom of the left menu, just above your name. The single icon button there is the theme toggle. A moon means you are in **Dark**, and its tooltip reads **Theme: Dark: Switch to light**.
The theme toggle sits in the footer of the left menu, under the separator.
***
**Step 2:** Click it. The whole admin repaints, the icon becomes a sun, and the tooltip now reads **Theme: Light: Switch to dark**. Click again to go back.
The same screen in Light. One button flips between the two.
***
**Step 3:** Nothing else to save. Your choice is remembered in the browser you made it in and applies to every admin screen, including the form editor, where the left menu collapses to icons but the toggle stays in the same place at the bottom. In the editor, hover the collapsed menu or move the keyboard focus into it, and it widens to show its labels without moving the canvas.
> **💡 Tip:** There are exactly two states, **Dark** and **Light**. There is no "follow my system" option: Dark is the default and Light is something you opt into.
***
## The theme does not change your forms
Switching the admin to Light does not change what respondents see. A public form takes its colors from that form's **Design** panel and from your **Brand kit**, never from the theme you happen to be working in.
* A form where you picked a background renders with your colors for everybody, in every browser.
* A form where you picked nothing renders dark for everybody, whichever theme you are in.
That is also why the builder canvas and **Preview** keep showing the published look while you edit in Light: the preview shows the form, not your workspace.
***
## What's next
* [Design & Branding](/dforms/design.md): the colors, fonts and background respondents actually see.
* [Brand kit (workspace-wide)](/dforms/design/brand-kit.md): one look for every form in the workspace.
* [What respondents see](/dforms/respondent-experience.md): the full public experience, step by step.
* [Your public link](/dforms/share/public-link.md): the address respondents open.
---
# 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.dapta.ai/dforms/account/appearance.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.
