# Branding

Put your logo, colors and email wording on what signers see.

> [!NOTE]
> Available on Pro and Platform. Owners and admins can edit branding. On a plan without branding, your settings are kept but not shown; they come back when you upgrade.

## Where branding shows

Your branding applies to:

- Signing pages
- Emails to signers, including signing requests, reminders and completed copies
- Emails to senders about the envelope, such as completion and delivery-problem notices, and workspace invitations
- The verify page
- The certificate page of completed PDFs

Changes apply to signing pages and emails sent after you save. Completed PDFs that already exist aren't changed.

## Edit branding

Open **Settings → Branding**. The preview on the right has tabs for **Signing page**, **Email** and **Completed PDF**, and shows unsaved changes as you type.

| Setting | What it does |
| --- | --- |
| **Logo** | PNG, JPEG or WebP, up to 2 MB. A wide logo on a transparent background works best. |
| **Logo for dark backgrounds** | Optional. Shown when a signer uses dark mode. Without it, the main logo is used. |
| **Primary color** | Buttons, links and the progress bar. |
| **Accent color** | The sign-here flag and required fields. |
| **Corner radius** | Rounding for buttons, fields and cards. |
| **Font** | The typeface on signing pages. |
| **Email header text** | Shown above the message in every email signers get. |
| **Email footer text** | Shown at the bottom of emails. |
| **Support contact** | An email address or phone number for signers with questions. |

Leave a field empty to use the default. Select **Save branding** when you're done.

## Customer workspaces on Platform

A platform sets default branding for all its customer workspaces. Each workspace can override any field in **Settings → Branding**. Empty fields use the platform's defaults, and the page says so at the top.

Platforms can also hide **sent with eSignStack** in email footers and on signing pages.

Platforms set their default in the platform console or through the API. See the [platform guide](/docs/platform-integration-guide).