Branding
Configure deployment display name, favicon, and logo.
The branding fields control how your installation identifies itself across the admin UI, storefront pages, and outgoing emails.
Accessing branding settings
Go to Settings → Branding.
Fields
Display name
The name field sets the human-readable label for your installation. It appears in:
- The admin UI top-left header
- Transactional email subjects and footers
- Any Puck component that references the store name token
This field is plain text. Leave it empty and the system falls back to the raw deployment identifier.
Favicon
The favicon field stores a URL pointing to your favicon image. This URL is written into <link rel="icon"> in the HTML <head> of every storefront page.
Upload requirements:
- Accepted formats: PNG, SVG, JPEG, ICO
- Recommended minimum size: 32×32 pixels
- For multi-resolution favicon support (retina, browser tabs, PWA), upload a 180×180 PNG — most modern browsers down-scale it automatically
The favicon upload dialog in Settings sends the file to S3 and saves the resulting object URL back to the favicon field. If S3 is not yet configured, the upload button is disabled and a banner directs you to Settings → Storage first.
Logo
The logo field stores a URL pointing to your logo image. It appears in:
- Admin UI top-left, alongside the display name
- Transactional email headers (order confirmation, shipping notification, refund notice)
- Storefront pages that use the
StoreNavBarorCheckoutHeroSectionPuck components when those components are set to pull from global branding
Upload requirements:
- Accepted formats: PNG, SVG, JPEG
- Maximum recommended height: 240 px — taller images are displayed at full size and may break layouts
- Use SVG or a 2× PNG for sharp rendering on high-DPI displays
How uploads work
When you use the upload control in Settings → Branding, the file is sent to your configured S3 bucket and the returned object key is combined with your static domain (Settings → Domains) to produce the full URL, which is then saved to the favicon or logo setting.
If you re-upload a new image, a new UUID-named object is created in S3 and the field is updated to the new URL. The old file is not automatically deleted.
Caveats
- Autonnel does not manage image lifecycle — if you delete an object from your S3 bucket, the URL goes dead.
- URL changes on re-upload are immediate in the admin UI but cached browsers may serve the old favicon for the duration of their cache TTL.
- If you paste a third-party image URL directly instead of uploading, that URL is used as-is. There is no proxy or re-host step.