How to translate Google Slides, end to end, without the export wrecking the deck

TL;DR: Google Slides has no built-in way to translate a whole presentation, and almost every translation tool on the market only accepts a .pptx. The route that works today is export to PowerPoint, translate with a tool that edits the text inside the file rather than rebuilding it, then import the result back into Slides. Done that way the layout, tables, images and speaker notes survive, and translated text that grew gets shrink-to-fit so it stays inside its box when Slides reopens it.

If you have searched for how to translate Google Slides, you have probably noticed the market pretends Workspace does not exist. Our June 2026 competitor research put eleven products in a matrix; apart from Google's own free Marketplace add-ons, every one of them accepted PowerPoint and none accepted a Slides file. Google Slides is the orphaned format, which is strange for a tool used by most startups, by the regional offices of companies that never open PowerPoint, and by anyone whose sales deck lives in Drive. This is the end-to-end path we recommend, with the export and import steps spelled out and the checks that tell you whether it worked.

Why is it hard to translate Google Slides directly?#

Google Slides is a browser application with the file stored in Drive, not a document format you can hand to a tool. There is no File menu entry for translating a deck. The Gemini sidebar, as our research recorded it, translates the text you point at rather than the whole presentation, and a full-deck translation requires a Marketplace add-on or an Apps Script. Add-ons vary in what they preserve, and none in our research claimed to handle overflowing text.

That leaves two families of workaround. The first is copy and paste: select text, translate it in a chat assistant, paste it back. On a five-slide deck this is fine. On a forty-slide investor update with tables and notes it takes a morning, and the terminology drifts because each paste is translated in isolation.

The second is export. Slides can save a deck as a Microsoft PowerPoint .pptx, and the export is faithful for the ordinary building blocks: text boxes, tables, images, charts, notes. Once you have a .pptx you can use any PowerPoint translation tool, and the result can be opened back in Slides. The whole question then becomes which tool to put in the middle, because that is where decks get wrecked.

What breaks between the export and the import?#

Three things, and none of them is translation quality.

Rebuilt slides. A tool that reads the deck as text and generates a new file from a template has thrown away your layout before it starts. A chat assistant's add-in that sees a markdown view of the deck cannot put back an image it never saw, and our research recorded chart values being invented in that mode. The fix is a tool that edits the text runs inside the original .pptx structure and leaves everything else untouched. SlideVerso's engine works that way: shapes keep their coordinates, fonts and fills, table cells keep their widths, charts stay charts, and the notes slide behind each slide is translated along with the visible text.

Overflow. Portuguese, Spanish, French and German are longer than English. Japanese and Chinese change the width of every character. A box that fitted the English original has nowhere to put the extra text, so it spills. Slides and PowerPoint both support a per-box setting, "Shrink text on overflow", which recomputes the font size on open. SlideVerso sets it on every text frame it writes, so when you import the deck into Slides the text fits without you touching a single box.

Drift. Decks translate in batches, so no single call sees the whole file, and the same product name can come back three ways. The engine runs one whole-deck pass first that locks a glossary, proper nouns and register into a small contract every batch translates against. Slide 30 keeps the term slide 2 introduced.

We should be plain about one thing. The engine has a native Google Slides path in its code, but the web app does not expose it yet, so today the export route is the one we support, and the pair pages say so rather than promising a Drive connection that is still being wired. Nothing you upload is kept: input files are deleted after processing and outputs are purged on a timer, which is the answer to "do you touch my Drive" for the export route. Details are on the privacy page.

How do you translate a Google Slides presentation, step by step?#

Here is a run you can reproduce with a real deck. Take an 18-slide investor update in English with a metrics table, one chart, a team slide with photos and speaker notes, going to Brazilian Portuguese.

1. In Google Slides, open the deck and choose File, then Download, then Microsoft PowerPoint (.pptx). Save the file.
2. Open the SlideVerso app and upload the .pptx. The slide count is read on upload, so the price is known immediately.
3. Pick the target. The picker offers 46 languages and regional variants, including Portuguese (Brazil) as its own entry rather than a generic Portuguese.
4. Look at the free watermarked preview of one translated slide. This is your first check that the layout survived.
5. The quote shows $19, because 18 slides is inside the up-to-30 tier. Pay by card. Most decks under 80 slides finish in a few minutes, with progress shown live.
6. Download the translated .pptx. Upload it to Drive, right-click it, and open with Google Slides. Choose File, then Save as Google Slides, to get a native Slides file again.

Now verify:

• On the metrics table, the column widths match the original and the Portuguese headers sit inside their cells.
• Click the chart. It is still a chart with editable series, with translated labels, rather than a picture.
• On the densest text box, open Format options, then Text fitting. "Shrink text on overflow" is selected. That is the autofit the engine set, and it is why the box did not spill.
• Open the speaker notes under a slide that had them. They are in Portuguese.
• Use Find to confirm that your company name and your key metric render the same way on every slide.

If the job had come back incomplete it would have been refunded automatically; a no-human-in-the-loop service can only be priced honestly if completeness is a hard gate rather than a promise.

What about sharing the translated deck with your team?#

Once the file is saved back as a Google Slides document it behaves like any other: share it, comment on it, present it from the browser. The imported deck keeps the theme and master slides that came through the export, so the only difference your team sees is the language.

Two habits make repeat translations painless. Keep the English deck as the source of truth and re-export when it changes, rather than editing translated copies in parallel. And keep the deck's defining terms in a short list you can check with Find, so a stakeholder in São Paulo sees the same vocabulary the London deck uses.

Which decks are not worth this workflow?#

A five-slide, text-only deck going to a language of similar length is faster to translate by hand in the sidebar. The export route earns its keep as soon as the deck has a table, a chart, notes, or more than a dozen slides, or the target language changes text length. That is most investor updates, most sales decks, and every regional launch.

Per-deck pricing fits the way this work arrives. A founder localises the sales deck twice a year and the investor update once a quarter, which is a handful of decks, not a seat. The language pair pages list every supported target with the same three-step flow, and the preview slide is free on every one of them, so the cheapest way to know whether your deck survives is to export it and look.