Google Fonts for Confluence Update (2026): Runs on Atlassian, 1,942 Fonts, and What's Next

[#1]

A few weeks ago I wrote 3 Ways to Customize Fonts in Confluence and Which One Actually Works. The short version: native Confluence gives you a small set of system fonts, browser extensions don't work for your teammates, and a Marketplace app — full disclosure, the one I build — was the only way to get real Google Fonts inside Confluence Cloud without your pages reaching out to fonts.googleapis.com every time someone opens them.

Three things have changed since that post. Two of them matter for security teams. The third matters for anyone who looked at our font picker and thought "this could be better." (You're right. It's about to be.)

I'm Simon from NGPILOT, and here's what's new.

---

1. The app is now Runs on Atlassian certified

This is the one I'm proudest of.

Runs on Atlassian is the program Atlassian introduced for apps that run entirely inside Atlassian's infrastructure — no third-party SaaS dependencies, no data leaving Atlassian's perimeter, no surprise outbound calls when a page loads.

For a font app, this matters more than for most. Here's why:

Concern	Typical Google Fonts embed	Runs on Atlassian
Where font requests go	fonts.gstatic.com (Google CDN)	Atlassian's own CDN
Data residency	Depends on Google's POP location	Same region as the Confluence page
Compliance story	"We use Google Fonts, but trust us"	"Nothing leaves Atlassian"
Works behind strict corp firewalls	Often blocked	Yes
Network calls when a page renders	External	Internal only

For admins in regulated industries — finance, healthcare, government, EU customers post-Schrems II — "no outbound calls" is the line that gets an app through procurement. We tick that box now.

---

2. Font catalog: 1,785 → 1,942 families (157 new)

When I wrote the original article, the catalog was at 1,785 font families. After syncing against the Google Fonts catalog, we're now at 1,942 families — each shipped with four variants: regular, bold (700), italic, and bold italic. All woff2, all subsetted to Latin + Latin Extended, all served from Atlassian's CDN.

A few of the 157 new additions worth calling out:

• Google Sans / Google Sans Flex / Google Sans Code — finally self-hostable; previously required custom CSS or external embeds
• Atkinson Hyperlegible Next / Atkinson Hyperlegible Mono — designed for low-vision readers, a quiet win for accessibility
• TikTok Sans, BBH Sans, Zalando Sans, TASA Explorer — brand-type families that previously only existed in corporate design systems
• Cascadia Code, Intel One Mono, SUSE Mono, Lilex, Cascadia Mono — for code blocks and developer documentation
• Big Shoulders Display / Inline / Stencil — the full Chicago-style display family
• Libertinus Serif / Sans / Math / Mono — the open-source academic typography family, finally available as a single self-hosted bundle

None of these require an outbound call. That's the whole point.

We are the #1 font app in marketplace!

---

3. The font picker is getting rebuilt

Here's the honest part: the current config UI is a flat dropdown with 1,942 entries in alphabetical order. That worked at 200 fonts. It does not work at 1,942. Scrolling is not a design strategy.

We're rebuilding the picker in the style of fonts.google.com — searchable, with preview cards, category filters, and live type-at-real-size previews before you commit.

The 7-field contract that pages depend on stays frozen:

• selectedFont, selectedVariant, previewText, selectedFontURL, textSize, textColor, textAlign

So every existing macro keeps rendering identically. Only the choosing changes. Targeting late Q3 — I'll post the before/after here when it ships.

---

Key Takeaways

• Runs on Atlassian — no outbound calls to fonts.gstatic.com; data stays in-region on Atlassian's CDN
• 1,942 font families — up 157 from the original article, all woff2, four variants each
• UX refactor incoming — the flat dropdown becomes a searchable fonts.google.com-style picker in late Q3
• Backward compatible — existing macros will continue to render identically when the new picker ships

If you're evaluating font apps for a security review and the Runs on Atlassian angle matters to your team, I'd love to hear what your procurement team typically asks for. What's the checklist look like on your side?

— Simon from NGPILOT