Reference a curated brand — colors, theme, font, and logo — from any badge or README header by URL. Edit once, update everywhere.
A brand is a named, reusable set of style tokens. Reference it from any badge or header URL and it applies the brand's colors, theme, font, and logo. Brands are curated by the shieldcn maintainers; anyone can reference an existing brand by its slug.
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.
Any badge rendered with variant=branded looks for a managed brand whose slug
matches the provider and applies it automatically — no ?brand= needed. So
if you create a brand named github, every variant=branded GitHub badge on
your site (and in anyone's README) adopts that brand's color, logo, font,
radius, and gradient:
<!-- Uses the "github" brand if one exists, else the built-in GitHub color -->
Edit the github brand once and every branded GitHub badge restyles on the next
fetch. This only applies to variant=branded; other variants are unaffected.
An explicit ?brand= or ?color= still wins, and a provider with no matching
brand falls back to its built-in brand color.
When 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.
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 updates all of them. Propagation is bounded by a short cache TTL, so a rebrand shows up across GitHub's Camo proxy within minutes.