How to Fix Embedded Google Fonts Looking Different in PowerPoint on Another PC
Question details
The user needs to fix an issue where an embedded Google font (Bitter) displays differently (blurry and wider) on another Windows PC, causing presentation text to reflow.

- Product
- Microsoft PowerPoint
- Device & OS
- Windows
- Scenario
- Sharing a PowerPoint presentation containing embedded Google fonts to a client's computer.
- Observed behavior
- The embedded font renders wider and blurrier on the recipient's computer, disrupting the slide layout and causing text to reflow, despite working correctly on the source computers.
Ensure that the custom font was downloaded and installed in TTF (TrueType) format, as PowerPoint has much better compatibility and rendering accuracy with TrueType fonts than OTF (OpenType) fonts when embedding.
Verify Office Version and Build Consistency
Differences in Microsoft 365 or Office builds between computers can cause the text rendering engine to behave differently. Matching versions ensures consistent font display.
Microsoft periodically updates how Office applications render text. If the client is using a different build or an older version of PowerPoint, the embedded font might be interpreted differently, causing text to appear wider and reflow.
On the computer where the presentation looks correct, open PowerPoint. Click on 'File' in the top-left corner, then select 'Account' at the bottom left.
Under 'Product Information', note the specific Version and Build number (e.g., Version 2308 Build 16.0.xxxxx.xxxxx).
Ask the client to perform the exact same steps on their Windows PC and compare the Version and Build numbers. If they differ, recommend updating Office via 'Update Options' > 'Update Now'.

Optimize Font Embedding Settings
Adjusting how the font is saved within the file can force PowerPoint to load all necessary character data, preventing substitution or rendering errors on the destination PC.
Install the Font Locally on the Recipient PC
Bypassing the embedded font entirely by installing the font directly into the Windows OS can resolve rendering bugs specific to PowerPoint's embedded font engine.
Use WPS Presentation for Seamless Font Compatibility
If Microsoft PowerPoint continues to distort embedded fonts across different computers, try opening your slides in WPS Office. WPS Presentation provides robust rendering capabilities and maintains strict layout fidelity, ensuring your slides look exactly as intended on any device.
- 1. Download and Install WPS Office: Get the free WPS Office suite from the official website and install it on your PC.
- 2. Open the Presentation: Launch WPS Presentation and open your .pptx file. WPS will automatically parse the embedded fonts.
- 3. Review Your Layout: Navigate through your slides to confirm that the text size, spacing, and font rendering remain perfectly intact.

Frequently Asked Questions
Why do embedded fonts look wider or blurry on a different PC?
This usually happens due to slight differences in the display scaling settings of the Windows OS, mismatches in Microsoft Office build versions, or conflicts between TrueType (TTF) and OpenType (OTF) font rendering engines in PowerPoint.
Does PowerPoint support embedding all Google fonts?
PowerPoint supports embedding TrueType (.ttf) fonts. OpenType (.otf) fonts or fonts with specific licensing restrictions (no embedding allowed) may fail to embed properly, leading to default font substitution and layout changes.
How can I tell if a font is properly embedded in my presentation?
Open the file on a computer that does not have the font installed natively. If the text displays correctly and the font name appears in the font dropdown without being substituted (you can check by going to File > Info > Check for Issues > Check Accessibility or Manage embedded fonts in newer versions), the embedding was successful.
Can different Windows user profiles affect PowerPoint font display?
Yes. If a font was previously installed on one Windows user profile but not for 'All Users', switching profiles can cause PowerPoint to lose access to the local font cache, forcing it to rely on the embedded version which might render differently.




