Skip to content

Branded share pages

On Pro and Team plans, every page your shares serve — folder listings, file requests, text shares and secrets — can carry your brand instead of the xPort look: your logo, your brand name and an accent color.

Dashboard (Branding) → OAuth introspection → relay register reply → CLI renders
  1. You upload logo, brand name and accent color in the dashboard (PNG/JPG/WebP up to 512 KB).
  2. When a signed-in CLI registers a share, the account server attaches your branding to the token introspection.
  3. The relay forwards it in the register reply.
  4. The CLI renders it into the share page header.

Values are re-validated on every hop (https logos only, hex or oklch accents, 40-character name cap) and HTML-escaped at render time — nobody can inject markup through a brand name.

Free shares always use the xPort look.

Self-hosters (and anyone who wants a per-machine brand) can set share.branding.* in config.yaml. Local values take priority over the account branding:

share:
branding:
name: "Acme"
logo: "https://cdn.acme.example/logo.png"
accent: "#2563eb"

The accent accepts #rrggbb hex or a plain oklch(...) value.