Create a reusable brand — colors, theme, font, and logo — and reference it from any badge or README header by URL. Edit once, update everywhere.
A brand is a named, reusable set of style tokens owned by your account. Reference it from any badge or header URL and it applies the brand's colors, theme, font, and logo. Edit the brand in the dashboard and every embed that references it re-renders on the next fetch.
Managed brands are a Plus feature — one brand per account.
Open the dashboard → Brands → Add brand. You can:
stripe.com and shieldcn pulls the logo,
color palette, and description automatically, then generates an editable
brand.md. Review everything before saving.The slug is what you reference in URLs. Pick something short — it becomes part
of every embed (?brand=acme).
Two equivalent forms:
<!-- Query param -->
<!-- Pretty path -->
The brand supplies theme, color, labelColor, valueColor, font,
variant, radius, logo, logoColor, gradient, and mode when you don't
set them explicitly.
Explicit query params always win, so you can reference a brand and still override one value per badge:
Precedence is explicit query param > brand value > default.
Once a brand has hosted assets, opt into them per badge:
<!-- Use the brand's hosted logo (mode-aware light/dark) -->
<!-- Render in the brand's uploaded font -->
font=brand-mono and font=brand-heading select the brand's other uploaded
typefaces. See Hosted assets for the full list.
README header banners accept ?brand= too, so your header logo, colors, and
font all follow the brand:
Because every embed references the brand by URL, editing the brand in the dashboard updates all of them. Propagation is bounded by a short cache TTL, so a rebrand shows up across GitHub's Camo proxy within minutes.
Brands belong to your account. Public visitors can consume your brand URLs (that's the point — they're on third-party READMEs) but cannot create or edit brands.