Ask ten SharePoint admins how to brand the site header and you will get ten frustrated answers. Out of the box the platform gives you very little, and the gap between “change the logo” and “make it look designed” is wider than most people expect.
What you get natively
Without any customisation, SharePoint Online lets you:
- Swap the site logo and set a thumbnail.
- Pick from a few preset header layouts (standard, compact, extended, minimal).
- Choose a header background from the theme-derived palette.
- Toggle whether the site title shows.
That is genuinely the whole list. You cannot set custom brand colours outside the theme, you cannot choose typography, you cannot build a real multi-level mega menu, and you cannot add a call-to-action button in the header.
Where people get stuck
The common mistake is trying to force branding through the theme alone. Themes drive colour across the whole site, so pushing a strong brand colour into the header also recolours buttons, links and accents in ways you did not intend. You end up trading a grey header for a site that looks loud and inconsistent.
The second trap is per-site effort. Even the limited native options have to be set site by site. On a tenant with dozens of sites, that is hours of repetitive clicking and no guarantee of consistency.
The supported way to go further
The supported route to a genuinely custom header is the SharePoint Framework (SPFx), specifically an Application Customizer that renders into the header placeholder. This is Microsoft’s own extensibility model, so it survives updates and does not rely on script injection or unsupported hacks.
An SPFx header extension can give you custom colours independent of the theme, real typography, a multi-level menu, search, and a header CTA, applied consistently across sites from a single deployment.
Build or buy
You can build this yourself if you have SPFx skills and time, or use a ready-made product. Our own SharePointKit Header web part does exactly this with no code, and the same craft sits inside our bespoke intranet builds when a project needs more than a product can offer.
Either way, the key point stands: the grey header is not a limit you have to accept. It is just the limit of the native settings.