How to Convert PowerPoint to Google Slides (and What Breaks)

Almost every guide to this question gives you one instruction — upload the file, open it in Slides — and stops. That instruction is correct and it is also the reason people end up confused three weeks later, wondering why their “Google Slides deck” still has a .pptx badge on it and why a colleague on a Chromebook can't use the version history.

Opening a PowerPoint in Slides and converting it into Slides are two different operations. Here is what each one does, what the conversion costs you, and how to check the result before you present it to anyone.

The three routes, and what each one actually produces

1. Open with Google Slides — fastest, but it stays a PowerPoint

Google's own switching guide documents the flow: open Drive, double-click the PowerPoint file to preview it, then click Open with Google Slides at the top. You get the full Slides editor and can start working straight away.

The part worth internalising is what Google says happens next: “All changes are auto-saved to the file in its original Office format.” This is Office editing mode. Your file is still a .pptx living in Drive; Slides is acting as an editor for it. That is genuinely useful when you are collaborating with people who need the PowerPoint back at the end — and quietly wrong if what you wanted was a Slides-native deck. (Source: Google Docs Editors Help, “Work with Microsoft Office files”, as of August 2026.)

2. Convert it — a real Slides file, and a second copy

Converting produces a native Google Slides presentation. Google is explicit about the trade: “When you convert, you make a copy of your Office file.” The original .pptx stays in Drive exactly as it was, and you now have two files that will drift apart the moment you edit either one.

That is a feature, not a bug — the original is your rollback. But decide which file is authoritative on day one and delete or archive the other, because “which of these two decks is current?” is a genuinely miserable question to answer in a hurry.

3. File > Import slides — when you only want some of it

If you have an existing Slides deck and want to pull slides from a PowerPoint into it, use File > Import slides, then pick the presentation from Drive or upload it. Google's Workspace Learning Center documents a Keep original theme checkbox: leave it ticked to import the slides unmodified, untick it to restyle them into the deck they are landing in. (Source: Google Workspace Learning Center, “Tips for great presentations”, as of August 2026.)

This is the right route for merging a few slides into a deck that already exists, and the wrong one for moving a whole presentation across.

The 100 MB ceiling

Google documents a hard limit: up to 100 MB for presentations converted to Google Slides (Google Drive Help, “Files you can store in Google Drive”, as of August 2026).

Decks bump into this more often than people expect, and it is nearly always images — a handful of full-bleed photographs straight off a camera will do it on their own. If a conversion fails on size, compress the images in PowerPoint first (Picture Format > Compress Pictures) rather than deleting slides. A deck that is 100 MB because of genuinely necessary content is usually a deck that should have been a video anyway.

What actually changes in the handover

Here is where most articles on this topic start inventing. Google does not publish a compatibility matrix for PowerPoint-to-Slides conversion — the switching guide covers feature differences between the two products, not a list of what survives transcoding. So treat any exhaustive-looking “what gets lost” table you find elsewhere as someone's inference, including where it happens to be right.

What we can tell you first-hand is what we see, because PowerPresent's own Google Slides export runs through exactly this conversion — we build the .pptx and hand it to Drive to transcode, which is the same path your manual upload takes. Two things change reliably enough that we warn people about them in the product before they click:

• Gradients arrive as solid colours. A gradient fill flattens to a single colour. On a title slide built around a gradient wash, this is the difference between “designed” and “fine”.
• Fonts fall back. A typeface with no Google Fonts equivalent is replaced with the closest available match. Because the substitute rarely has identical metrics, text that was set to fit its box can reflow — and a headline that was two lines becomes three.

Everything else in our experience holds up well: text stays editable text, native charts stay native charts, and slide structure survives. The failure mode is cosmetic drift, not a wrecked deck.

A five-minute check before you present it

Conversion problems are visual, so the only reliable check is to look. In order of how often they actually catch something:

1. Open the slide sorter and scan for text overflow. Font substitution shows up as text spilling past its box or a heading that has grown a line. This finds the majority of real problems in about ninety seconds.
2. Check your title slide and any gradient backgrounds. These are where flattening is most visible.
3. Click into one chart. Confirm it is still an editable chart rather than a picture of one.
4. Check speaker notes on two or three slides, especially if you present from them.
5. Present it once, start to finish, on the machine you'll actually use. Nothing else catches a missing font the way the projector does.

Skip the round trip entirely

If the deck does not exist yet, the conversion problem is one you can decline to have. PowerPresent generates a designed presentation from a prompt or an uploaded document, you edit it in the browser, and then you export it — either as a real .pptx with editable text and native charts, or straight to your Drive as a Google Slides presentation, without downloading and re-uploading anything.

The Google Slides export asks only for permission to the files it creates, so the rest of your Drive stays private. It carries the same two caveats as any other route into Slides, for the same reason: gradients flatten and fonts without a Google equivalent fall back. We would rather say that on the button than have you find it on stage.

Creating, editing and presenting are free and unlimited. Watermark-free export is a paid output, and one credit unlocks a presentation for both .pptx and Google Slides — it is one unlock, not two charges. One-time credit bundles start at $5 with no subscription.

You can open a template in the editor without an account, or read the AI Google Slides maker guide for the full picture of making slides with AI, including what Gemini inside Slides can and cannot do.

When to just stay in PowerPoint

Honest answer: often.

• The deck is heavily animated. Complex build orders and transitions are the least portable thing in any presentation format. If the animation is the point, converting it is a downgrade.
• It is brand-critical and typographically exact. If a licensed corporate typeface with no Google equivalent is non-negotiable, Slides will substitute it. Use Office editing mode instead and keep the .pptx.
• You are presenting from it tomorrow. Do not convert a deck the night before. There is no upside that outweighs discovering a reflowed headline at 8am.
• Nobody needs to collaborate on it. Conversion buys you real-time collaboration, version history and a link instead of an attachment. If you need none of those, you are paying fidelity for nothing.

Convert when you want the collaboration. Stay put when you want the pixels. The mistake is doing it by accident — which, given that the fastest route leaves you with a PowerPoint file wearing a Slides interface, is easier than it sounds.

Working from source material rather than an existing deck? See converting a PDF into a presentation, or turning Markdown into PowerPoint slides.