# White Label

> Part of the NocoDB documentation (Self-hosting). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL.

URL: https://nocodb.com/docs/self-hosting/white-label
Last updated: 2026-10-03

Replace the NocoDB branding on your self-hosted instance with your own product name, logos, favicon, brand color, email branding and support contact.

White labeling replaces the NocoDB branding with your own across the **entire self-hosted instance**. This includes the app shell, the login screen, public forms, the browser tab, transactional emails and the in-app support contact. It is for resellers, OEM partners and enterprises that show NocoDB to their users under a different brand.

White labeling is **instance-wide**, and the **Super Admin** configures it. The deployment has one configuration, and it applies to all workspaces and users. Changes apply **live, without a restart**.

## Open the White Label settings

1. In the NocoDB UI, go to **Admin Panel** > **White Label**.

   <img alt="White Label admin page" src={__img0} placeholder="blur" />

The page has four sections: a master **Enable** toggle, **Branding**, **Email branding** and **Support**.

## Enable white labeling

The master toggle at the top controls if NocoDB applies the configuration.

* You can fill in and **save** all fields while the toggle is **off**. NocoDB applies nothing yet, so you can prepare your branding before it goes live.
* To apply the configuration across the instance, turn the toggle **on** and save.

## Branding

<img alt="White Label branding section" src={__img1} placeholder="blur" />

### Product name

The product name replaces the word "NocoDB" in these places: browser tab titles, the application sidebar, page titles, the login screen and public form titles. The maximum is 60 characters. To keep "NocoDB", leave the field empty.

### Logo

Upload different logos for light and dark backgrounds:

* **Logo · light mode**: shows on light surfaces.
* **Logo · dark mode**: shows on dark surfaces. If this field is empty, NocoDB uses the light logo (and the opposite). Thus one uploaded logo works in the two modes.

The logo shows in the application header and sidebar, the login screen, the workspace menu and public / shared views.

**Format:** PNG · about 240×60 · max 2 MB.

### Favicon

The favicon is the square icon in browser tabs. NocoDB also uses it for the iOS "Add to Home Screen" icon and as the square brand mark in the public form footer.

**Format:** PNG or ICO · 48×48 · max 2 MB.

### Default form banner

Public forms show this banner when the form author did not upload a banner. Use a wide image that fits the **4:1** banner ratio. The uploader has a cropper to help you.

**Format:** PNG or JPG · about 1200×300 · max 2 MB.

### Brand color

The brand color is one hex color (for example `#0D5A5A`). It changes the color of buttons, links and accents in the UI. From this one seed color, NocoDB makes a full color ramp (light and dark variants) and the matching component theme tokens. Thus all accented surfaces change color in the same way. The brand color also sets the color of the mobile browser chrome (`theme-color`).

* Type a hex value, or use the color picker. You can select a preset color, or type a hex value for an exact brand match.
* A **contrast indicator** warns you if white button text can be hard to read on your color.

<Callout type="info">
  Only solid colors are supported. Accepted formats are 

  `#RGB`

   or 

  `#RRGGBB`

  ; any transparency (alpha channel) is dropped.
</Callout>

### Uploading assets

For each image slot, **drag & drop** a file, or click to **browse** and upload a file.

<Callout type="warning">
  Only raster image files are accepted: 

  **PNG, JPG, ICO, GIF, WEBP, AVIF, and BMP**

  , with a maximum file size of 

  **2 MB**

   per asset. For security reasons, SVG and other non-image files are rejected.
</Callout>

NocoDB serves uploaded assets from a stable, permanent URL. Thus they load correctly in transactional emails and stay after instance restarts. When you replace or remove an asset, NocoDB automatically removes the old file from storage.

## Email branding

The email branding values replace the default "NocoDB Team" branding in transactional emails (invitations, password resets, notifications and others). To keep the NocoDB default, leave a field empty.

<img alt="White Label email branding and support settings" src={__img2} placeholder="blur" />

| Field               | What it does                                                                                                                                                                |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Sender name**     | The "From" display name on outgoing emails. If it is empty, NocoDB uses the product name, then "NocoDB". Thus the sender name is never empty. The maximum is 60 characters. |
| **Footer text**     | Replaces the default footer tagline / signature. The maximum is 240 characters.                                                                                             |
| **Footer link URL** | The brand link in the email footer. It must be an absolute `http(s)` URL, because same-origin paths do not resolve from an inbox.                                           |

When white labeling is on, transactional emails also:

* Use your **product name** in headings and body text, not "NocoDB".
* Show your **logo** at the top of the email.
* Remove the standard NocoDB social and legal footer links. The footer then shows only your brand line.

## Support

### Support email

You can set your own support contact for the in-app help menu. When white labeling is on, this email replaces `support@nocodb.com` in the help menu. To use NocoDB support, leave the field empty.

<Callout type="info">
  The support email is the help-menu entry intended for white-label customization. Other links in the help menu (documentation, API reference, community, changelog) and the optional NocoDB support chat are governed separately — for example, the support chat widget is controlled by the 

  `NC_DISABLE_SUPPORT_CHAT`

   

  [environment variable](/docs/self-hosting/environment-variables)

  .
</Callout>

## What gets branded

| Area                                         | Branded by                                          |
| -------------------------------------------- | --------------------------------------------------- |
| Browser tab title                            | Product name                                        |
| Browser tab icon, iOS home-screen icon       | Favicon                                             |
| App header & sidebar logo                    | Logo (light / dark)                                 |
| Login screen                                 | Logo + brand color                                  |
| Workspace menu                               | Logo                                                |
| Public & shared views                        | Logo + product name                                 |
| Public form default banner                   | Default form banner                                 |
| Public form footer                           | Favicon + product name (and footer link, if set)    |
| Buttons, links, accents, mobile chrome color | Brand color                                         |
| Transactional emails                         | Sender name, logo, product name, footer text & link |
| In-app help menu support contact             | Support email                                       |

### Examples

The login screen shows your logo. Its buttons and links use the brand color:

<img alt="Branded sign-in screen" src={__img3} placeholder="blur" />

Your logo replaces the NocoDB mark in the app sidebar and the workspace menu:

<img alt="Branded workspace" src={__img4} placeholder="blur" />

Buttons, links and accents in the app use the brand color:

<img alt="Branded application" src={__img5} placeholder="blur" />

Public forms use your default banner when the form author did not set a banner:

<img alt="Branded public form banner" src={__img6} placeholder="blur" />

## How licensing affects white labeling

If your license **expires** or is **downgraded**, or if the add-on is removed, the instance automatically goes back to the NocoDB defaults. NocoDB keeps your saved configuration. When you restore the entitlement, your branding comes back.

## Availability

* **Enterprise add-on.** White labeling is available on self-hosted instances as an **add-on** to the **Enterprise** plan. It is not included in the base Enterprise license. It is **not** available on NocoDB Cloud on any plan. For pricing and to add it to your plan, contact [NocoDB support](mailto:support@nocodb.com). Then refer to [License Activation](/docs/self-hosting/license-activation) to activate your license.

---

## Related pages

- [Self-Hosting](https://nocodb.com/docs/self-hosting.md): Self-host NocoDB on your own infrastructure and keep full control of your data.
- [Environment Variables](https://nocodb.com/docs/self-hosting/environment-variables.md): Set environment variables to configure a self-hosted NocoDB instance: database, storage, authentication, cache, rate limits and more.
- [Purchasing a License](https://nocodb.com/docs/self-hosting/purchase-license.md): Purchase a Business or Scale plan license for your self-hosted NocoDB instance through NocoDB Cloud.
- [Activating a License](https://nocodb.com/docs/self-hosting/license-activation.md): Activate a self-hosted NocoDB license with the standard, airgapped or fully offline method.
- [Troubleshooting](https://nocodb.com/docs/self-hosting/troubleshooting.md): Find and fix common problems with self-hosted NocoDB: startup, network, SSL, database, attachments and login.
- [Migration Guide](https://nocodb.com/docs/self-hosting/migration-guide.md): Migrate a self-hosted NocoDB instance from a non-Postgres database to PostgreSQL so you can activate a paid license without losing data.
- [License](https://nocodb.com/docs/self-hosting/license.md): The NocoDB Sustainable Use License (SUL), its Fair-Code principles, and when you need a commercial license.
- [FAQs](https://nocodb.com/docs/self-hosting/FAQs.md): Answers to common questions about self-hosted NocoDB: what the Community Edition includes, upgrades, shifted timestamps and instance details.