> For the complete documentation index, see [llms.txt](https://docs.voveid.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voveid.com/docs/sdks/customization.md).

# Customization

Apply your brand to the VOVE ID welcome and summary experience.

Customization lets you align the hosted SDK experience with your product while keeping verification instructions clear and accessible.

## Configure a theme

1. Sign in to the correct VOVE ID dashboard environment.
2. Open **Settings → General → Customization**.
3. Upload the light-mode logo used on the welcome and summary screens.
4. If your application supports dark mode, upload a dark-mode logo as well.
5. Select accessible primary colors for light and dark mode.
6. Preview the experience in Sandbox.
7. Save the theme and reopen the SDK to load it.

If no custom logo is configured, the default VOVE ID logo is used.

<figure><img src="https://4173094968-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F83UoxmShmjD5iX8BJPn0%2Fuploads%2FZjFhc92jcrABrkUwUDso%2FScreenshot%202024-10-12%20at%2022.42.48.png?alt=media&amp;token=12e47c5e-ac41-4559-a89f-e43cf56a7331" alt="SDK theme customization controls in VOVE ID dashboard"><figcaption><p>Open Settings, General, then Customization.</p></figcaption></figure>

## Test before Production

Theme changes can affect all new SDK journeys in that environment. Validate in Sandbox before applying the same settings to Production.

Check:

* logo legibility on light and dark backgrounds;
* color contrast for text, controls, focus indicators, and disabled states;
* small phones, tablets, and desktop browser widths;
* right-to-left layouts for Arabic locales;
* welcome and summary screens when `showUI` is enabled;
* your own surrounding UI when `showUI` is disabled;
* screen readers, keyboard navigation, and device text scaling.

Branding must not obscure consent, camera guidance, error messages, or retry actions.

## Environment behavior

Sandbox and Production are separate configuration boundaries. A theme saved in Sandbox does not prove that Production is configured. Confirm the environment shown in the dashboard before changing assets or colors.

SDKs load the active theme when a journey opens. If a change does not appear, close the current journey, start a new Sandbox session, and rule out application or browser caching.

## Troubleshooting

| Symptom                                 | Check                                                                            |
| --------------------------------------- | -------------------------------------------------------------------------------- |
| Logo does not appear                    | Confirm it was saved in the same environment used by the public key and session. |
| Dark-mode logo is unreadable            | Verify the correct dark asset and transparent padding.                           |
| Colors fail accessibility checks        | Increase foreground/background contrast and retest every state.                  |
| Theme updates unexpectedly affect users | Make changes in Sandbox first and schedule Production changes like a release.    |

For SDK-specific UI controls, see the [compatibility matrix](/docs/sdks/compatibility.md) and the guide for your platform.