Canva Fonts Change in Google Slides: Why It Happens and Which Fonts Survive
August 2026 · Docslide
Docslide turns the document you already wrote into a finished PowerPoint or Google Slides deck.
Canva fonts change in Google Slides because the file goes through two separate font substitutions, not one. Canva has no Google Slides export, so the deck has to become a .pptx first, and Canva swaps any font it cannot embed for a near match at that point. Google Slides then reads that file and swaps again for anything outside the Google Fonts library. The only fonts that come through untouched are the ones that exist on both sides of the trip.
This is the failure people notice first, because it is visible. The deck opens, the type is wrong, and everything below the first heading has shifted down half a line. It is also the failure that is easiest to prevent, provided you make the decision before you export rather than after. Below is what happens at each stage, which fonts actually survive, and the one category that never will.
Why do Canva fonts change in Google Slides?
Because nobody owns the round trip. Canva does not offer a Google Slides download at all. Its export menu covers PDF, JPEG, PNG, GIF, PPTX, MP4 and CSV, so the standard advice is to download a PowerPoint file, upload it to Google Drive, and open it with Google Slides. That is two conversions with a file handoff in the middle, and the two converters know nothing about each other.
Hop one is Canva writing the .pptx. A PowerPoint file references fonts by name and expects the machine opening it to have them. Canva cannot guarantee that, so fonts it cannot rely on get mapped to something close. Hop two is Google Slides reading the result. Google Slides does not use the fonts installed on your computer at all. It renders from the Google Fonts library, so any font name in the file that Google does not host gets mapped again, usually to Arial.
Two guesses, made independently, by systems with different font catalogs. That is why the result often looks nothing like either the original or what you would have picked yourself.
Which fonts survive Canva to Google Slides?
The surviving set is the overlap between Canva's font library and Google Fonts. Canva's built-in library includes a large number of Google Fonts, and Google Slides can load anything in the Google Fonts catalog through the More fonts option in the font dropdown, which opens the full library of over a thousand typefaces. A font sitting in both places has a name both ends recognize, so neither hop needs to guess.
What matters is not the specific font so much as where it came from. This table is the part that decides the outcome:
| What you used in Canva | What the .pptx export does with it | What Google Slides does on import | Survives |
|---|---|---|---|
| A Canva font that is also a Google Font (Roboto, Open Sans, Lato, Montserrat, Poppins and similar) | Writes the font name straight through. Nothing to substitute. | Recognizes the name and loads it from Google Fonts. | Yes. This is the safe set. |
| A true system font (Arial, Times New Roman, Verdana, Georgia) | Passes through unchanged. | Has a direct equivalent already loaded. | Yes, though the deck will look generic. |
| A Canva exclusive or Canva Pro font that is not in Google Fonts | Substituted for a near match, or rasterized if it is inside a styled element. | Substituted again, commonly to Arial. | No. Two guesses, neither of them yours. |
| Your company font, uploaded to a Canva Brand Kit | Referenced by name, but the file itself does not travel. | Google cannot host a licensed font you uploaded elsewhere, so it falls back. | No, and there is no workaround inside Google Slides. |
| Text set inside a Canva graphic, sticker or styled element rather than a plain text box | Flattened into a bitmap along with the element. | Imports the bitmap. There is no text left to substitute. | The look survives. The text does not, and cannot be edited. |
| A weight or style variant (Light, Semibold, Condensed, Black) | Written as a variant name the file may not carry cleanly. | Collapses to the nearest available weight, often regular or bold. | Partly. Expect your careful weight hierarchy to flatten. |
Two rows there account for most complaints. The Brand Kit row surprises people the most, because uploading a licensed font into Canva genuinely works inside Canva, which makes it feel portable. It is not. Google Slides renders from Google's own library, and it has no mechanism for you to supply a font file. If your brand depends on a licensed typeface, a deck that has to live in Google Slides will never be fully on brand, and that is worth knowing before you promise it to anyone.
How do I convert Canva to Google Slides without losing fonts?
Make the font decision in Canva, before the export, not in Google Slides afterward. Fixing it on the far side means reselecting type on every slide by hand, and the text has already re-flowed by then.
The sequence that works: in Canva, open the font picker and switch the deck to a font you can confirm exists in Google Fonts. Check the name matches exactly, because Canva's library changes and a similarly named font is not the same font. Set the same font on the title, body and any text inside grouped elements, which are easy to miss. Then Share, Download, choose PPTX, and download. Upload that file to Google Drive, double click it, and choose Open with Google Slides.
Once it is open, set the font again from the Google Slides font dropdown even if it looks correct. This forces Slides to bind the text to its own copy of the font rather than to an inherited name, which is what keeps the deck stable when someone else opens it later on a different machine.
Why the text still moves when the font is right
Font matching solves the appearance. It does not fully solve the layout, because line breaks are computed from character widths, and even the same font renders at slightly different metrics across the two engines. A headline that fit on one line in Canva can wrap onto two in Slides, and everything under it shifts.
Canva documents part of this on its own side. Its support material notes that some line elements are not designed for consistent export and can change length or alignment on download, that text boxes can resize slightly during export, and that extra spaces inside a text box change how the text wraps in the downloaded file. Those small shifts are inherent to the route rather than a bug you can file.
The practical mitigation is to leave slack. Text boxes sized exactly to their content in Canva have nowhere to go when the metrics change, so give headlines room and avoid text that sits one character short of wrapping. Deleting trailing spaces genuinely helps, which sounds trivial until it is the reason a subtitle broke across two lines.
The case where none of this is worth doing
All of the above assumes the deck belongs in Canva and simply needs to move. Often it does not. If the content came out of a report, a proposal, a quarterly summary or a board memo, then somebody took a finished document, retyped it into a design tool, and is now translating that design back into a business file. The font problem is a symptom of running a document through a design detour it never needed.
Agencies and consultants hit this hardest, because the deck is built in Canva by a designer and handed to a client who lives in Google Workspace and expects to edit it. The handoff is where the losses become someone else's problem. It usually starts earlier than the design, in the intake: much of what ends up on those slides is scoped during the first call, and a process that structures what comes out of that discovery conversation tends to produce a deck outline before anyone opens a canvas.
Converting the source document directly avoids both hops. Headings become the slide breaks, tables are rebuilt as native chart objects with the numbers still behind them rather than as pictures of tables, and the file opens in Google Slides as a single clean import. That is what the Canva to Google Slides converter route page covers in detail, including what each hop costs you element by element. If PowerPoint rather than Slides is the destination, the same logic applies to going from Canva to PowerPoint, where the losses are similar but stop after one conversion instead of two.
The short version
Pick a font that exists in both Canva and Google Fonts before you export, and most of this problem disappears. Accept that a licensed brand font will not make the trip at all. Expect weights to flatten and text to re-flow slightly even when the font is correct. And if the deck came from a document, convert the document instead, because the cleanest fix for a two hop conversion is not doing it twice.
Your next deck is already written.
Docslide turns the documents you already wrote into finished, editable decks: layouts, charts from your data, and speaker notes, exported to PowerPoint and Google Slides.