What Happens to Your Fonts When Converting Word to EPUB?

When you convert a Word document to EPUB, the font you chose almost never reaches the reader. Most conversion tools drop the font data, commercial font licences usually forbid embedding in an ebook, and every reading app lets the reader pick their own typeface anyway. The font a reader sees is normally the one their device supplies, not the one you set in Word.

Why Do Fonts Disappear During Word-to-EPUB Conversion?

Fonts vanish during conversion because of three compounding problems: technical stripping, licensing barriers, and the reader’s own settings. Even when everything else goes right, at least one of these layers will usually stand between your Word font and the reader.

Word documents store font information as references: a name and a style declaration rather than the actual font file. Even when you switch on Word’s “Embed fonts in the file” option, most EPUB conversion tools do not carry that embedded font data forward. The resulting EPUB contains a CSS font-family declaration pointing at a font name, but no font files are packaged inside the EPUB container. If the reader’s device does not have that font installed, and it almost certainly does not, the reading app substitutes its own default.

This is a different model from print, where your PDF locks in every glyph exactly as designed and the press has no choice in the matter. In a reflowable ebook, the reader controls the reading experience by design; the format was built that way so a reader can enlarge the type without losing the book off the edge of the screen. If you have worked with images breaking during Word-to-EPUB conversion, the font problem follows the same pattern: what works in Word’s rendering engine does not automatically transfer into the EPUB package.

The point worth holding on to is that this is not a fault to be fixed. An ebook that ignored the reader’s font preference would be a worse ebook, which is why every major platform is built to let that preference win.

Which Fonts Can You Legally Embed in an EPUB?

Only fonts whose licence permits redistribution can be embedded in an EPUB you sell. The two licences that clearly allow it are the SIL Open Font License (OFL) and the Apache License 2.0.

The fonts most authors reach for (Calibri, Cambria, Times New Roman, Arial, Garamond) are proprietary. They ship with Microsoft Office under a licence that permits use on your own computer but prohibits redistribution. Packaging a font file inside an EPUB counts as redistribution, so using a Microsoft Office font in a commercially distributed ebook is a licensing violation even though nobody is likely to chase you for it. Every platform pushes this responsibility onto you: Amazon states plainly in its reflowable text guidelines that securing the appropriate licence rights for fonts is the publisher’s job, and Kobo’s own guidance says the same.

All Google Fonts are released under the SIL Open Font License, which makes them safe to embed. Ebook-friendly options include Literata (designed for screen reading), Libre Baskerville, Lora, Merriweather, and Source Serif 4. Font Squirrel’s “100% Free” collection is another reliable source, since every font in that category has been checked for embedding permissions. Our guide to where to get fonts for your book covers which “free” fonts to be careful with, and if terms such as font subsetting or glyph outlines are unfamiliar, our typography glossary covers the essentials.

One thing we check on every file we are handed to fix: a font can be legal to install and still illegal to embed, and the two permissions live in separate fields of the font file. An author who bought a font legitimately can be entirely within their rights on their own machine and still be shipping an unlicensed ebook.

How Does Amazon Kindle Handle Fonts in Reflowable Ebooks?

Kindle does support embedded fonts, but its rules for body text mean the reader’s choice normally wins. This is the point most often stated too bluntly elsewhere, so it is worth separating what Amazon permits from what a reader actually sees.

On what is permitted: Amazon’s guidelines for creating reflowable books confirm that Kindle supports embedded OpenType (OTF) and TrueType (TTF) fonts, and that on KF8-enabled devices and apps readers can turn publisher-provided fonts on or off. Type 1 (PostScript) fonts are not recommended, and reflowable books that use them are rendered in Kindle’s own fonts by default.

On what is required: Amazon’s reflowable text guidelines state that body text in a reflowable Kindle book must be all defaults, and that creative styling belongs on headings, special paragraphs, footnotes, and tables of contents rather than on body paragraphs. The reason given is that styling body text overrides the reader’s preferred settings, which readers report as a poor experience. During upload, Amazon applies its own corrections: the font size used across most of the content is normalised to 1em, the main font-family is moved to the root tag, and forced font colours in body text are removed so the reader can change them.

The practical result is that readers see Kindle’s own typeface (usually Bookerly on current devices and apps) unless they deliberately switch to the publisher font in their settings. Very few do. Designing your ebook on the assumption that they will is not realistic, so for novels, memoirs, and most non-fiction the body typeface is effectively outside your control on Kindle.

There is one trap in Amazon’s rules that catches hand-coded files. If your HTML tags are not closed correctly and font declarations conflict, Amazon removes the font files from the book altogether rather than trying to resolve the conflict. A single stray tag can therefore strip every embedded font from a file that validated fine elsewhere, which is one reason a book that passes on one store can behave differently on another.

How Do Kobo, Apple Books, and Google Play Handle Embedded Fonts?

Kobo, Apple Books, and Google Play Books all give embedded fonts more room than Kindle does, though each works slightly differently. The table below sets out what each platform supports and what the reader has to do to see your typeface.

Kobo supports embedded fonts and exposes the choice to the reader directly. In the Kobo Web Reader’s advanced reading settings there is a “Publisher default” toggle described as displaying the book as the publisher intended, alongside the reader’s own font family, weight, and spacing controls. Kobo’s own advice to authors is blunt and sensible: if you do not mind what font your book is read in, you do not need to embed one, and the case for embedding is strongest for fixed-layout books and for languages whose characters sit outside the Roman alphabet.

Apple Books needs one extra step that catches people out. Embedded fonts have to be listed in the manifest of the OPF file, and, as the Apple Books Asset Guide sets out, the specified-fonts option must be set to true for a flowing or fixed-layout book to use them at all. Apple also recommends declaring a genuine bold face rather than letting the system synthesise one from the regular weight. Miss the metadata step and the fonts travel inside the file but never render.

Google Play Books is the least fussy of the three. Its EPUB feature support table lists embedded fonts as supported, and its default reading font, Literata, is itself released under the SIL Open Font License. Properly embedded fonts display without the reader doing anything.

The practical takeaway: if you are publishing wide rather than exclusively on Amazon, a permissively licensed embedded font will give your ebook a consistent look everywhere except Kindle, where the reader’s setting rules.

When Does Fixed-Layout EPUB Preserve Your Fonts?

Fixed-layout EPUB is the one ebook format where your fonts, positioning, and visual design are fully preserved. A fixed-layout ebook works as a digital replica of the printed page: each page renders at a fixed size with elements placed at exact coordinates, in the way a PDF does.

That makes fixed-layout the right choice for books where the design is inseparable from the content: children’s picture books, cookbooks with stepped layouts, art and photography books, graphic novels, and comics. In those books the typeface is part of the design, and substituting it would break the page. Our guide to reflowable versus fixed-layout EPUB covers the technical differences in detail.

Fixed-layout is the wrong choice for novels and text-heavy non-fiction, and the reason is accessibility rather than taste. Readers cannot resize the text, adjust line spacing, or change fonts, which excludes readers who need larger type. Amazon’s own format comparison chart is explicit about the cost: its fixed-layout formats have no user font settings and no screen reader support, and Print Replica is described as a format to use only when the content absolutely requires the exact print layout. Fixed-layout files are also considerably larger, because every page is rendered as its own canvas.

What Fonts Should You Use for Your Ebook?

For a reflowable ebook, the most useful approach is to stop trying to control the body typeface and put that effort into what you can control: a clean heading hierarchy, consistent paragraph indentation, sensible line spacing, and a well-structured stylesheet. Those survive conversion intact and shape the reading experience far more than typeface choice does.

If you want typographic personality in headings and chapter titles, choose from Google Fonts or Font Squirrel’s free collection. Playfair Display, Raleway, Lora, and Oswald are all reasonable heading choices with licences that permit embedding. There is an accessibility caveat worth heeding: Amazon specifically recommends avoiding thin fonts for body text, because thin strokes are harder to read and reduce the apparent contrast against the background. That advice holds well beyond Kindle.

For body text, the device defaults are a genuinely good outcome rather than a compromise. Bookerly on Kindle, Kobo’s system fonts, Literata on Google Play Books, and Apple’s built-in typefaces were each designed for screen reading and tuned for the display hardware they run on. If you are choosing a typeface for the printed edition, where your choice does stick, our guide to choosing the right font for your book is the place to spend that decision.

When preparing your Word document for conversion, set body text in a standard serif or sans-serif face (Times New Roman or Calibri are perfectly good working fonts) and accept that the reader will see something else. What matters is that your headings are real Word heading styles rather than large bold text, because that structure is what carries across into the EPUB and what a screen reader uses to navigate.

The short version: treat the body typeface as the reader’s decision and the structure as yours. Get the heading levels, spacing, and stylesheet right, keep any embedded font to headings and display text, and check the licence before you package anything.

Frequently Asked Questions

Can I embed any font I want in my EPUB file?

No. You can only embed fonts whose licence explicitly permits redistribution. Most commercial fonts, including those bundled with Microsoft Office and Adobe Creative Cloud, prohibit it. Stick to fonts released under the SIL Open Font License or Apache 2.0; all Google Fonts and everything in Font Squirrel’s free collection qualify.

Will my Kindle ebook show the font I chose in Word?

Almost certainly not for body text. Kindle supports embedded OTF and TTF fonts, but Amazon requires body text in a reflowable book to use defaults and normalises the file on upload, so the reader sees their own chosen font unless they switch to the publisher font in their settings. Embedded fonts are best reserved for headings, drop caps, and display text.

What is the difference between reflowable and fixed-layout EPUB for fonts?

In a reflowable EPUB the text reflows to fit the screen and the reader controls the font, so your body typeface will not be preserved. In a fixed-layout EPUB each page renders at a fixed size with exact positioning, so fonts are fully preserved. Fixed-layout suits visually complex books such as picture books, cookbooks, and comics, and is not appropriate for novels.

Do Kobo and Apple Books support embedded fonts better than Kindle?

Yes, in the sense that neither restricts body text the way Kindle does. Kobo supports embedded fonts and gives readers a “Publisher default” toggle to return to them. Apple Books renders them reliably provided the fonts are listed in the OPF manifest and the specified-fonts property is set to true. Google Play Books supports them with no special reader action.

Why does my ebook look different from my Word document?

Because the two are rendered by different engines with different rules. Word draws a fixed page at a size you chose; an ebook reader redraws the text to fit an unknown screen using the reader’s font, size, and spacing settings. Anything you achieved in Word with manual spacing, tabs, or a particular typeface is likely to change. What carries across reliably is structure: heading levels, paragraph styles, lists, and page breaks between chapters.

Does font choice affect my ebook’s file size?

Only if you embed one. An embedded font adds its file to the EPUB package, typically tens to a few hundred kilobytes per weight, and a family with regular, italic, bold, and bold italic means four files. Subsetting (including only the characters the book actually uses) reduces that considerably. Referring to a font by name without embedding it adds nothing, because there is no font file to carry.

What should I focus on instead of fonts when formatting my ebook?

Focus on the structure you can control: proper heading hierarchy, consistent paragraph indentation, clean page breaks between chapters, correct line spacing, and alt text on images. These survive conversion intact, affect readability far more than typeface choice in a reflowable ebook, and are what a screen reader relies on.