Claude Design Fonts Wrong or Missing in the Export? Why It Happens and How to Fix It

Fonts go wrong in a Claude Design export when the exported file does not carry the font, so the app that opens it swaps in one it has. The most common case is the PowerPoint export: it rebuilds your text as editable PowerPoint text, and any font not installed on the viewer's computer falls back to a stand-in. To fix it, install the font on that computer and embed it when you save (File > Options > Save > Embed fonts in the file, on Windows), or set your design system to Google Fonts, which browsers and Google Slides load on their own and anyone can install free.

Which Claude Design export loses which fonts?

Each export stores text differently, and that decides where the font can get lost. Find the export you used:

The pattern: editable formats depend on the machine that opens them, fixed formats depend on the moment they were made. For export problems beyond fonts, see the export troubleshooting guide.

Why does PowerPoint change my fonts?

Claude Design's PowerPoint export keeps text and shapes editable, so PowerPoint draws your text itself, with the fonts installed on the computer that opens the file. Your design, though, was drawn in a browser with web fonts: a Google Font, a brand font from your design system, or a font your Mac has and Windows does not. Where the font is missing, PowerPoint substitutes another, and because every font has different letter widths, lines rewrap, headings break onto two lines and text spills out of its box. People testing the export report exactly this: shifted fonts and widths, and one or two formatting breaks per slide.

It also explains the classic complaint that a deck looks right on your laptop and broken on the client's: you have the font installed and they do not. To see which fonts a deck uses, open Replace Fonts (Home > Replace > Replace Fonts on Windows, Format > Replace Fonts on a Mac).

How do you embed fonts in a PowerPoint file?

Embedding stores the font inside the .pptx so it travels with the deck. You can only embed a font installed on your own computer, so install it first (from Google Fonts or your brand folder), open the deck, fix any lines that rewrapped, then:

1. On Windows, go to File > Options > Save and tick Embed fonts in the file.
2. On a Mac, go to PowerPoint > Preferences, choose Save under Output and Sharing, and tick Embed fonts in the file.
3. Choose Embed all characters if anyone else will edit the text. The smaller "only the characters used" option can break new typing.
4. Save, and send that file.

Two limits. A font whose licence forbids embedding will not travel, and PowerPoint may warn you or leave it out. And Google Slides ignores fonts embedded in a .pptx, so embedding fixes PowerPoint only. If the deck only needs to be presented, a picture-slide PowerPoint sidesteps all of this, at the cost of editable text; the PowerPoint export guide compares both routes.

Why do fonts change in Google Slides?

Google Slides can only display fonts from its own library, which is Google Fonts. That applies to the Export to Google Slides option (offered in the standalone Claude Design app at claude.ai/design) and to any .pptx you upload to Slides: a font outside the library is replaced, and fonts embedded in a .pptx are ignored.

If your font is a Google Font that is simply not in your menu yet, open the font menu in Slides, choose More fonts, search for it and add it; the text switches back. If it is a brand font that is not on Google Fonts, Slides cannot show it at all. Pick the closest Google Font for the deck, or present from images of the slides, where the brand font is already baked in.

Why do fonts look wrong when I open the HTML on another computer?

A standalone HTML file is a web page, and a web page uses a font only if it can load it: embedded in the file, bundled next to it, or fetched from a font service such as Google Fonts. Everything else falls back to the browser's default. Three traps catch most people:

• System fonts. A design set in SF Pro or Helvetica Neue looks right on a Mac, which includes them, and falls back on Windows and Android.
• Fonts that only live on your computer. If a font is installed on your machine but was never added to the design, your browser finds it and nobody else's does.
• Offline viewing. Google Fonts download from the internet, so a file opened without a connection shows the fallback.

The fix is to make every font part of the design: Google Fonts where you can, and brand font files added to the project so they can travel in the project .zip. Then test it the way your client will see it, by opening the export on a second device.

Why is the font wrong in a PNG or rendered image?

An image cannot change font after it is made, so a PNG with the wrong font means the font was not available at the moment of capture. There are two causes. The first is timing: web fonts arrive a moment after the page, and a capture taken too early freezes the fallback. Before screenshotting, reload and wait until the text stops shifting.

The second is a blocked font host. Renderers and sandboxes often refuse fonts from servers they do not trust. Renda, for example, loads fonts only when they are embedded in the file, included in the zip, or served from Google Fonts, so a font from Adobe Fonts or a company server will not load there. Switch to a Google Font, or upload the project zip with the font files inside. Once an image renders with the right font, it is fixed for good: PNGs and picture-slide decks look identical on every screen. If the font is right but the image looks soft, that is a different problem, covered in why exports look blurry.

Which fonts survive every Claude Design export?

Choose fonts for the export you will need, not only for the canvas. Google Fonts are the safest choice: they load in browsers and renderers, Google Slides has them, and anyone can install them free to fix a PowerPoint. Set your design system's heading and body fonts to Google Fonts, or name them in your prompt:

Use Google Fonts only: Playfair Display for headings and Inter for body text, loaded from Google Fonts in the HTML. Draw every icon as inline SVG, not with an icon font. Do not use system fonts such as SF Pro, Segoe UI or Helvetica Neue.

If you need a licensed brand font, keep the editable formats for people who have it installed, and send everyone else PNGs, a PDF or picture slides, where the font is already part of the image.

Frequently asked questions