How to Fix PowerPoint Changing Custom Fonts to Calibri in Microsoft Teams
Question details
The user needs to prevent custom company fonts from automatically reverting to Calibri when sharing a presentation in Microsoft Teams.

- Product
- Microsoft PowerPoint and Teams
- Device & OS
- not provided
- Scenario
- Presenting a PowerPoint file containing custom fonts (such as Graphik) during a Microsoft Teams meeting.
- Observed behavior
- The presentation displays correctly in the local PowerPoint app but changes custom fonts to Calibri when shared in Teams, causing shifts in text weight, size, and overall slide layout.
Ensure that your custom fonts are properly installed on your local computer and check that both your PowerPoint and Microsoft Teams applications are updated to the latest versions.
Embed Custom Fonts in Your Presentation File
Embedding the custom font directly into your PowerPoint file ensures that the typography travels with the presentation, preventing Microsoft Teams from substituting it with a default font.
By default, PowerPoint links to the fonts installed on your computer. When you present via PowerPoint Live in Teams, it uses cloud rendering. If the cloud server doesn't have your company font, it defaults to Calibri. Embedding fonts solves this by packaging the font data inside the file.
In PowerPoint, click on the 'File' tab in the top-left corner, select 'Options' at the bottom of the menu, and then click on 'Save' in the left sidebar of the Options dialog.
Scroll down to the 'Preserve fidelity when sharing this presentation' section and check the box next to 'Embed fonts in the file'.
Choose 'Embed all characters (best for editing by other people)' to ensure the font renders fully during the presentation, then click 'OK' and save your document.

Share Your Local Window Instead of PowerPoint Live
Sharing your screen or window relies on your local computer's rendering engine and installed fonts, bypassing the cloud-rendering limitations of PowerPoint Live.
Export the Presentation to PDF
If your presentation does not rely on animations or media, exporting it to a PDF format will lock all visual elements, including custom fonts, into place.
Avoid Formatting Frustrations with WPS Presentation
If you frequently struggle with Office cloud-rendering issues or font substitutions, try WPS Office. It's a lightweight, free alternative that offers seamless compatibility with PowerPoint files and built-in features to preserve your original document formatting.
- 1. Download and Install: Get WPS Office for free from the official website and install it on your device.
- 2. Open Your Presentation: Launch WPS Presentation and seamlessly open your existing .pptx files with full formatting retained.
- 3. Export and Present: Use the one-click 'Export to PDF' feature to lock your custom fonts for flawless screen sharing in any meeting.

Frequently Asked Questions
Why does PowerPoint Live in Teams change my custom fonts?
PowerPoint Live relies on cloud rendering. If your specific custom or company font is not installed on Microsoft's cloud servers, Teams cannot render it and will substitute it with a web-safe default font like Calibri.
Does the number of attendees in a Teams meeting affect font rendering?
No. The attendee count has no impact on how fonts and formatting are rendered. The issue stems entirely from how the presentation is shared (cloud vs. local) and whether the custom fonts are embedded.
Can I install custom fonts directly into Microsoft Teams?
No, Microsoft Teams does not have a feature to accept custom font installations. To display them, you must embed the fonts in the original PowerPoint file or use standard screen sharing to leverage your computer's locally installed fonts.
How do I know if my custom font is allowed to be embedded?
When you try to save a file with embedded fonts in PowerPoint, the software checks the font's licensing. If the font creator has restricted embedding, PowerPoint will display a warning prompt detailing which specific fonts could not be embedded due to licensing restrictions.




