---
title: "Visual identity"
description: "Visual identity of a Signer instance: the color theme, chosen by a three-letter code, and the four logo files served under /theme-assets/."
canonical: "https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/customization/identidade-visual"
locale: "en"
product: "Signer"
last_updated: "2026-09-14"
---

# Visual identity

## Color scheme

The application is themed by a theme with two main colors:

* **Theme**: the theme color.
* **Accent**: the contrast color.

![Color scheme](https://docs.lacunasoftware.com/images/signer/color-scheme.png)

Each theme is identified by a **three-letter code**, such as `acr` for *amazon-cornell-red*. The complete
list is in [Available themes](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/customization/temas).

To change your instance theme, give the desired code to the deployment team.

> **Note**
>
> If none of the themes fit, a new theme can be created for you. Just tell us the desired *theme* and
> *accent* colors.

The same three-letter code is used to theme the
[Embedded Signature](https://docs.lacunasoftware.com/en-us/articles/signer/embedded-signature) widget.

## Logos

The application uses **four** logo files, served under `/theme-assets/`:

| File | Where it shows up |
|---|---|
| `light-logo` | On dark backgrounds, in the side menu and top bar of the authenticated area, and as the default e-mail logo |
| `dark-logo` | On light backgrounds, in the public area header and the external screens |
| `stamp-logo` | Default logo of the printer friendly version (signatures manifest) |
| `val-stamp-logo` | Default logo of the validation stamp |

Examples of `light-logo` and `dark-logo`:

![Light Logo](https://docs.lacunasoftware.com/images/signer/light-logo-sample.png)

![Dark Logo](https://docs.lacunasoftware.com/images/signer/dark-logo-sample.png)

The files must be handed to the deployment team, who place them in the `assets` folder of the *Blob
Storage* configured for the instance, the same place used by the [home page](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/customization/home-e-footer) files.
After the update, the application must be restarted.

> **Tip**
>
> `stamp-logo` and `val-stamp-logo` only define the **instance default**. Each organization can upload its
> own logo for the printer friendly version and for the validation stamp with no need for the deployment
> team, as shown in [Generated documents](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/customization/documentos).

## See also

* [Available themes](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/customization/temas)
* [Home page and footer](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/customization/home-e-footer)
* [Generated documents](https://docs.lacunasoftware.com/en-us/articles/signer/on-premises/customization/documentos)