Use custom fonts and branding in Confluence
Default Confluence typography makes every page look the same. Learn how to apply your brand’s fonts and visual style across your wiki.
Why this matters in Confluence
A knowledge base that looks like a generic template erodes trust and makes important content harder to scan. Brand typography and visuals signal polish, reinforce identity, and quietly tell readers that what they are reading is maintained and authoritative. Confluence ships with a fixed, limited font set and no illustration library, so every page ends up in the same handful of system faces — which is fine for engineering notes but falls flat for an intranet homepage, an internal product launch, or a customer-facing help center. Teams that care about perception end up either fighting the editor or pasting in screenshots that break search and exports.
Typography is part of the brand
The font on a page says as much as the words do. Customers, employees, and stakeholders recognise a brand partly through its type and visual rhythm — a rounded humanist sans for an approachable consumer product, a precise grotesque for a fintech, a serif for an editorial tone. When the wiki defaults to the same generic sans every other company uses, that visual identity disappears at exactly the moment someone is looking for it.
Confluence ships a fixed font set
Out of the box you can only pick from a handful of system fonts, and there is no way to apply a house font, set a distinct face for headings, or vary typography by page type without editing storage format or CSS. That rigidity is the single biggest reason internal portals look interchangeable — and why marketing teams give up on Confluence and host landing pages elsewhere.
Readability changes with the face
A typeface is not just decoration; it changes how long someone will read. The right reading face makes long policy documents less fatiguing, while a clear display face makes headings and call-outs scannable. Picking two complementary families — one for body, one for headings — is a small decision with an outsized effect on how much of the wiki people actually consume.
On-brand visuals need a source
Hunting for illustrations, icons, and diagrams outside Confluence and then pasting them in is slow, inconsistent, and usually produces a mix of clipart, screenshots, and stolen stock art. A curated library of on-brand graphics removes the guesswork, keeps the visual language unified across hundreds of pages, and lets any author reach for the same set of approved imagery without a design review.
Screenshots rot, vector art does not
A pasted PNG illustration is frozen the moment it lands — change the brand colour and every page is suddenly out of date. Vector illustrations and font-based styling applied as native content update in one place and propagate everywhere, so a rebrand or a seasonal refresh does not become a page-by-page archaeology project.
The approach that works
Branding a wiki is a two-part exercise: pick the typefaces and visuals that express the brand, then apply them with macros that write native Confluence content rather than pasting images. The goal is consistency that survives a rebrand and works for every author, not just the one who knows CSS. The steps below walk through the decisions and the trade-offs.
- 1
Pick your brand font families
Choose the families for headings and body copy — typically one display face for titles and call-outs, and one readable text face for paragraphs. Google Fonts offers hundreds of free, well-tested families with multiple weights; pick two that contrast in weight or style rather than two that look similar. Limit yourself to those two so the wiki stays cohesive instead of becoming a font buffet.
- 2
Decide where typography varies
Not every page needs the same treatment. A policy document wants a calm body face with occasional styled headings; a landing-style portal wants a bold display face on hero sections. Map out a small set of roles — hero title, section heading, body, caption — and assign a family, size, and colour to each so authors have a clear rule to follow instead of guessing per page.
- 3
Apply them with a fonts macro
Use a fonts macro to apply a family to selected text or blocks, with size, colour, and alignment that match your style guide — no CSS or HTML editing required. Apply it inline where you need it and save page templates that already carry the right typography so new pages start on-brand instead of defaulting to the system font.
- 4
Add on-brand illustrations and icons
Insert consistent icons and illustrations from a browsable, searchable library instead of mixing clipart and screenshots. Group assets by category — people, objects, abstract — and standardise on a single palette and line weight, so a page assembled by three different authors still looks like it came from one team.
- 5
Prefer vectors and styled text over images
Reach for SVG illustrations and font-based styling rather than pasted PNGs whenever you can. Vectors scale without blurring on retina screens and PDF export, and they recolour instantly when the brand palette changes. Reserve raster images for photographs, where vectors cannot do the job.
- 6
Document and reuse the system
Write down the families, sizes, colours, and asset sources you chose, and save them into reusable page templates and a style-guide page. Consistency comes from making the right choice the easy choice: when an author can pull a branded template and a known illustration set, the whole space stays on-brand without a design review on every page.
This solution is for you if…
- Marketing and brand teams keeping the internal wiki on-brand
- Internal comms teams building polished intranet homepages and announcements
- HR and people-ops teams producing employee-facing portals and policy hubs
- Design teams that need a shared, approved illustration and icon library inside Confluence
- Any team that wants pages that look as good as they read
Our apps that solve this
Every app is free for up to 10 users on the Atlassian Marketplace. Pick the one that fits your workflow, or combine them.
ConfluenceGoogle Fonts for Confluence
Enhance your Confluence pages with Google Fonts
ConfluenceContent Craft for Confluence
Free SVG Illustration Library for Confluence: 1,300+ Notion-Style Graphics for Business, Tech & Lifestyle
Read the guides
Frequently asked questions
Not natively — Confluence ships with a fixed font set and no built-in way to load additional families. A fonts app adds a macro that applies any of 1,798+ Google Font families to page text with live preview and full control over size, colour, and alignment, all written as native Confluence content so it survives search, export, and permissions.
Why teams choose NGPILOT
Free for up to 10 users
Every app is free for small teams, with the full trial Atlassian provides for larger ones.
Native Forge apps
Built on Atlassian Forge, running entirely on Atlassian Cloud infrastructure.
Your data stays in your instance
No content is sent to our servers — processing happens inside your Confluence or Jira.
Verified Marketplace vendor
NGPILOT apps are listed, reviewed, and maintained on the Atlassian Marketplace.
Ready to try it?
Every app is free for up to 10 users. Install in a couple of clicks.