Why do brand fonts look wrong in Microsoft 365 for the web?
The browser versions of Word and PowerPoint cannot see fonts installed on your computer. They render only fonts from Microsoft's Cloud Fonts list plus any font an administrator has uploaded for the tenant. A corporate typeface installed locally is invisible to the browser app, so Office substitutes a fallback, and the substitution changes line lengths and breaks layouts.
Why can the desktop app see the font when the browser cannot?
The desktop app reads font files installed in the operating system. The browser app runs inside a sandbox with no access to the local font directory, because a web page should never be able to enumerate what is installed on your machine. Microsoft 365 for the web therefore serves typefaces from its own hosted set.
This catches out brand teams who have deployed a corporate font to every managed device. The deployment is working. The browser app simply has no route to it.
What is the Cloud Fonts list?
Cloud Fonts is the set of typefaces Microsoft hosts and streams to Office apps on demand. It runs to a few hundred families and covers the faces that ship with Office plus a large licensed collection. When a document uses a Cloud Font, the browser app downloads it and renders correctly. When it uses anything outside that list, Office substitutes.
Substitution falls back to the theme font and then to a generic default, which in practice usually means Aptos or Calibri. A condensed corporate sans replaced by Calibri can gain 8 to 12% in line length, which is enough to push a headline onto a second line and shunt every element below it out of position.
Can an administrator add a corporate font?
Yes, within limits. A Microsoft 365 global administrator can upload licensed font files in the admin centre under Settings > Org settings > Organisation profile > Custom fonts, after which the fonts become available to users in that organisation in supported apps.
Two conditions catch people out. The font licence has to permit this kind of hosting and redistribution, and many foundry licences do not. The upload also covers your own tenant only, so an external reviewer opening the same document in their browser still sees a substitute.
Does uploading the font to SharePoint fix it?
No. Placing a font file in a SharePoint asset library, a Teams files tab or a OneDrive folder makes the file downloadable and has no effect on rendering. Word and PowerPoint for the web do not read fonts from document libraries. The font has to sit in the Cloud Fonts list, in the tenant custom font store, or installed locally for the desktop app.
What happens when one person is in the desktop app and another is in the browser?
Both people edit the same file and see different layouts. The desktop user sees the correct typeface. The browser user sees a substitute, watches text overflow a box or a heading wrap awkwardly, and starts fixing it by resizing text boxes and reducing font sizes.
Those edits save into the file and travel with it. The desktop user then reopens a document that has been manually broken to solve a problem that only ever existed in the browser. This is the most damaging version of the issue, and it shows up most often on a shared pitch deck or a board paper being co-authored under time pressure.
Does embedding the font help?
Only on the desktop. File > Options > Save > Embed fonts in the file will carry a permitted typeface inside a .pptx or .docx so a desktop recipient without the font still sees it correctly. Embedded fonts inflate file size and are stripped from the rendering path in the browser apps, so embedding solves external sharing on desktop and leaves the browser problem untouched.
What is the practical answer?
Choose a theme font pairing that degrades gracefully. Set the template's heading and body fonts in Design > Fonts > Customise Fonts in PowerPoint, or Design > Fonts in Word, and select a brand typeface whose metrics sit close to a widely available fallback. A brand sans with an x-height and character width similar to Arial or Segoe UI substitutes almost invisibly. A condensed or display face does not.
Where the brand font is non negotiable, use it in fixed graphic assets and cover pages, and set a metric-compatible Cloud Font for body copy that everyone can render. At Ideaseed, every template we build specifies both the brand typeface and its tested fallback, so a document opened in a browser holds its layout whatever the viewer has installed.
Brand fonts look wrong in Microsoft 365 for the web because the browser apps can only render Cloud Fonts and tenant uploaded fonts, never fonts installed on a local machine. Substitution then changes line lengths and breaks carefully built layouts, and any fixes a browser user makes are saved permanently into the file. Choosing a metric-compatible fallback in the theme font pairing is what stops the damage.
To find out how your templates behave in the browser apps, book a free template health check.
Need a branded template? We can turn it around overnight.
Australia's Microsoft Office template specialists with a South Africa team that delivers while you sleep.
RAVE REVIEWS
who we work with
.svg)
.svg)
.svg)
.svg)
