Custom branding for status pages helps customers recognize immediately that the page is official. That matters most during incidents, when people are stressed and deciding whether they can trust what they are reading.
If you want the feature side, see Custom Branding and Create a public status page. This guide focuses on branding decisions.
Based on operational experience at StatusPage.me, the most common branding mistake is applying a primary brand color as the page background without checking whether status indicators — degraded, outage, and operational states — retain enough contrast against it. Industry surveys find that dark mode usage has grown consistently year-over-year and now represents a majority of device-level OS preference in many markets, which means a status page tested only in light mode is untested for a large share of your actual visitors.
What branding should improve
Branding should improve:
- recognition
- trust
- consistency with the main product
- clarity during incident communication
It should not make the page harder to read.
What should usually be branded
Common branding elements include:
- logo
- colors — both light and dark mode palettes
- page title and support references
- custom domain
StatusPage.me lets you define separate color palettes for light and dark mode visitors. That matters because a light-optimized palette (white background, dark text) will look wrong to visitors whose devices are in dark mode. Setting explicit dark mode colors gives everyone a consistent, intentional experience. See Branding Your Status Page for the setup steps.
For domain decisions, see Custom domains for status pages.
Branding should not reduce clarity
A status page is still an operational page.
Avoid branding choices that:
- weaken status contrast
- bury important incident states
- make component status hard to scan
- over-prioritize decoration over readability
The built-in WCAG contrast ratio checker (visible in the Live Preview section of the palette editor) shows whether your text and background colors meet accessibility thresholds before you save. Use it for both light and dark palettes.
Those principles overlap directly with Status page best practices, especially during active incidents.
Readability across themes
Light mode and dark mode need separate palette decisions, not just an inverted version of the same colors. A white background with dark text passes contrast requirements easily, but the same primary-color accent used for operational status badges may become unreadable against a dark background unless you explicitly check it. The WCAG AA standard requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text or UI components like status badges. In practice, status indicators — the colored labels that show “Operational,” “Degraded,” or “Outage” — are the most important elements to verify in both themes, because they carry the meaning customers came to read. If your brand palette uses a low-contrast color for positive states (common with muted greens), test it specifically against both your light and dark backgrounds before publishing. When in doubt, use higher contrast than you think you need: customers checking your status page during an incident are often on mobile, in poor lighting, or both.
Practical rule
If a new customer lands on the page during an outage, they should recognize the brand in seconds and understand the service state in seconds too.
How StatusPage.me handles this
Custom Branding on StatusPage.me lets you define separate color palettes for light and dark mode visitors, set your logo, and preview the result before publishing. The palette editor includes a built-in WCAG contrast ratio checker in the Live Preview section so you can verify that your chosen colors meet accessibility thresholds for both themes without needing external tooling. Changes to branding apply immediately to your live status page, so you can iterate quickly. The logo upload and color settings are independent of your incident history and component configuration, so rebranding at any point has no effect on existing incident records or subscriber preferences.
FAQ
Why brand a status page at all?
Because customers trust and recognize incident communication faster when the status page clearly belongs to the product they already use.
Should branding ever override readability?
No. Status pages are operational interfaces, so readability and scannability come first.
Is custom branding enough without a custom domain?
Branding helps, but the strongest trust signal usually comes from combining branding with a clear custom status domain.
Should dark mode use completely different colors?
Usually not. Most teams use lighter variants of the same primary and accent colors, paired with a dark background and light text. The goal is visual consistency across themes, not a different identity. The built-in contrast checker helps verify that each palette is readable on its own.
