To convert PowerPoint to Google Slides, upload your .pptx file to Google Drive, right-click it, and choose "Open with > Google Slides" — Drive keeps your original PowerPoint file untouched and produces a new editable Google Slides copy right away. The same result works the other way: in Google Slides, use File > Import slides and point it at an existing .pptx on your computer, and Slides will pull in every slide as a fresh deck. Both methods are officially supported by Google and leave the source .pptx in place rather than overwriting it. Conversions do not need a Microsoft 365 subscription, a paid Google Workspace plan, or any third-party service — a free personal Google account is enough. Most simple presentations survive the round trip cleanly: text boxes, tables, images, charts, and standard master layouts come across with their formatting intact, and you can keep editing the deck in Slides as if it had been built there. The catch is that some PowerPoint-specific features, like complex animations, motion paths, and certain font effects, do not have equivalents in Slides and are simplified or dropped during the import.
Why move a deck from PowerPoint to Google Slides?
The case for switching comes down to three things: collaboration, cost, and access. Google Slides is free for any Google account, so a team that has been paying per-seat for Microsoft 365 just to share a single deck can move to Slides without giving up collaborative editing. Slides lives in the browser, so anyone with the link can comment, suggest edits, or take over a slide in real time, and there is no "save and email the latest version" loop. Version history is automatic, so rolling back to last Tuesday's slide order is a click rather than an archaeology project. Slides also handles concurrent edits without locking a slide the way desktop PowerPoint can, which matters when two people are editing the same chart.
There are real trade-offs. Google Slides has a smaller library of slide transitions than PowerPoint, fewer built-in chart types, and a thinner set of animation options. Heavy design work, complex morph transitions, and custom-branded masters are easier in PowerPoint or a dedicated design tool. The right move is usually to keep the original .pptx as the master and use the converted Google Slides file for sharing, presenting on the web, and collecting feedback.
If the underlying deck is a technical one — say, a slide full of motor specs, cooling loads, or HVAC ratings — moving it to Slides is only half the job. The numbers on the slides still need to be in the right units for the audience, and that is where a power conversion calculator earns its place beside the deck.
Four working methods to convert the file
All four of these work today, on a free Google account, without installing anything. Pick the one that matches how the .pptx is currently stored.
- Upload to Google Drive, then open with Slides. Go to drive.google.com, click "+ New", choose "File upload", pick your .pptx, then right-click the uploaded file and choose "Open with > Google Slides". Slides creates a fresh Google Slides file alongside the unchanged .pptx. This is the most common path, and the one Google itself recommends.
- Drag and drop into Drive. Open drive.google.com in a browser tab, then drag the .pptx from your desktop straight into the browser window. Drive uploads it, then right-click the file and open it with Google Slides the same way as method one. On modern browsers this is identical to method one; on slow connections it tends to be slightly faster because there is no menu navigation in the middle.
- Import from inside Google Slides. Open slides.google.com, click "Blank presentation", then choose File > Import slides. Pick the .pptx from your computer and Slides will copy every slide in. Use this when the .pptx is still local and you don't want a separate Drive upload step. The original .pptx on your computer is not modified.
- Use a third-party converter. Services like CloudConvert, Aspose, or Slidesgo converters take a .pptx and hand back a Slides-friendly version. Most need an account, free tiers cap file size, and the result still has to be opened in Slides to be editable. Reserve these for cases where the .pptx cannot leave your computer (use Aspose's local app) or when Drive is blocked at work.
Which method should I use?
The four methods overlap, but the right one depends on where the file lives and how big it is.
| Method | Best for | Needs internet? | Original .pptx preserved? | Typical limit |
|---|---|---|---|---|
| Upload to Drive, open with Slides | A single standard presentation | Yes | Yes | Standard Drive upload cap |
| Drag and drop into Drive | Quick ad-hoc imports from desktop | Yes | Yes | Same as above |
| File > Import slides in Slides | Pulling selected slides from a local .pptx | Yes | Yes (file is not modified) | Same Drive cap applies to resulting file |
| Third-party converter | Offline conversion, batch jobs, restricted networks | Sometimes | N/A | Free tiers usually cap near 50 MB |
For most decks under a few hundred megabytes, methods one and three give the same result, and method one is slightly easier to script with the Drive API. Reserve third-party tools for the cases the table calls out.
What breaks during the conversion
Even though the file comes across looking right, several PowerPoint features get flattened or dropped. Knowing what to expect saves a fix-up pass later.
- Animations. Slides supports a small subset: fade, slide, cube, and a handful of others. PowerPoint's motion paths, morph transitions, and timed "wipe" sequences are simplified to a basic transition or removed entirely. Re-time any timing-sensitive animations by hand after the import.
- Fonts. Custom fonts that are not in the Google Fonts library fall back to a default. Pre-convert text to a Google Font before upload, or accept that the converted deck will use a substitute face on machines that do not have the original font installed.
- Embedded video. Videos linked from a local drive often stay linked, but the file path has to exist on the viewer's computer, which is rarely true. Re-host videos on YouTube or Google Drive and paste the link back into the converted slide.
- Charts and SmartArt. Most modern PowerPoint charts re-render correctly as native Google Slides charts. SmartArt diagrams sometimes come through as a flat group of shapes; if that is a problem, convert the SmartArt to images inside PowerPoint before upload.
- Slide masters and layouts. Custom masters usually come across, but the spacing of placeholder text can shift by a few pixels because Slides renders text slightly differently. Check the slide masters in the converted file and adjust if needed.
Power math for technical slide decks
Plenty of decks converted to Slides are technical — engineering reviews, plant maintenance walk-throughs, motor spec comparisons. Those slides are usually full of units that don't agree with each other: horsepower in one table, kilowatts in another, BTU/h on the HVAC page, ft·lbf/s on the pump curve. Walking a meeting through the deck is much smoother when all those numbers are consistent, and the conversion math is fast with a power conversion calculator that handles watts, kW, MW, hp, BTU/h and more.
Take a single conversion as a worked example. To convert kilowatts to mechanical horsepower, divide the kilowatt value by 0.7457, because 1 mechanical horsepower is defined as exactly 745.6998715822702 watts, which is 0.7456998715822702 kilowatts. For a 100 kW motor:
- Formula: hp = kW ÷ 0.7457
- Substitute: hp = 100 ÷ 0.7457
- Result: hp ≈ 134.1 mechanical horsepower
So 100 kW ≈ 134.1 mechanical hp. The metric horsepower (PS) variant of the same 100 kW comes out to about 136.0 PS, since 1 kW ≈ 1.360 PS — roughly a 1.4% gap from mechanical hp that shows up on European spec sheets. The tool's Show all units at once option lists both horsepower values side by side so the difference is visible without leaving the page.
HVAC ratings are the other place this comes up. Air conditioners in North America are quoted in BTU per hour, while international models are quoted in watts or kilowatts. A "1-ton" AC unit, defined as 12,000 BTU/h, is roughly 3,517 W of cooling capacity, because 1 BTU/h ≈ 0.293 W. If the converted deck is read by an audience that uses metric, putting a single line in the methodology section like "1 BTU/h ≈ 0.293 W; 12,000 BTU/h ≈ 3.5 kW" reads cleanly. Use the converter to get the precise figures; don't multiply by a rounded constant by hand.
Troubleshooting common conversion problems
Most conversion issues come down to four root causes.
- The file is over the upload limit. Split the deck into chunks under 100 MB, or compress the images in PowerPoint (File > Compress Pictures) before uploading.
- The deck opens but looks wrong. Drive and Slides render PowerPoint slightly differently on the server than desktop PowerPoint does. Open the file in PowerPoint first, then "Save a copy" as a fresh .pptx; this clears out the corruption that sometimes builds in heavily edited decks.
- Fonts vanish or substitute badly. Install the missing font on every viewer's computer (impractical) or convert the deck text to a Google Font before uploading. Embedding fonts in PowerPoint does not carry through to Google Slides.
- Animations fail to convert. Trim the animation list in PowerPoint before upload or rebuild the affected slides in Slides natively.
If your deck is one of several you need to convert, consider scripting the upload with the Drive API — the same File > Open with Google Slides action is exposed as a one-line request per file, and a folder full of .pptx files can be processed in roughly the time it takes to upload the first one.
For technical presentations where horsepower, kilowatts, and BTU/h all appear on adjacent slides, normalizing every figure through the converter during the cleanup pass keeps the converted deck consistent across slides — the same 100 kW then reads the same in every chart that mentions it, and the mechanical-horsepower versus metric-PS gap stays visible rather than hidden inside rounded numbers.