How-to

How to translate a PowerPoint presentation

DocTranslating translates an entire PowerPoint presentation (.pptx, and legacy .ppt) into 100+ languages in one operation — no retyping text box by text box. Slide layouts, tables, charts and inline formatting are preserved in the translated deck. Microsoft Azure gives the best formatting fidelity for slides, DeepL produces the most natural output for European languages, and Google Cloud has the widest language coverage. Gemini doesn't accept PowerPoint files — convert to PDF first or use one of the other three engines.

Updated June 26, 2026 · 9 min read

Translating a presentation by hand is slow and error-prone: you click into each text box, retype the translation, move to the next slide, and repeat — often across dozens of slides. Then the translated text turns out longer than the original and overflows the boxes you carefully sized. This guide covers the faster approach: translating the whole .pptx (or legacy .ppt) file at once so you get a complete translated deck back with the layout intact.

Why PowerPoint files translate cleanly

A .pptx file is structured internally as XML — every title, text box, table cell and chart label is a labelled element that a translator can identify individually. That structure is what makes it possible to extract each piece of text, translate it, and put it back exactly where it belongs. It's the same reason a Word document translates well, and the opposite of a PDF, where text has been flattened into fixed positions with no structure left to work from.

Because of that structure, these elements carry over reliably:

• Slide titles and body placeholders — the main text areas on each layout.
• Text boxes — including callouts, captions and free-floating labels.
• Tables — rows, columns and cell alignment.
• Charts and diagram labels — the text attached to visual elements.
• Inline formatting — bold, italic, colour, font sizing and hyperlinks.
• Images and shapes — stay exactly in place; only the text around them changes.
• Slide order and transitions — the deck's structure is untouched.

Step-by-step: translate a PowerPoint presentation

1. 1

   Upload your .pptx or .ppt file

   Drag your presentation onto the upload area or click to browse. DocTranslating detects the format and shows only the engines that accept it. Modern .pptx works with three engines; legacy .ppt is supported by DeepL and Google Cloud.

2. 2

   Choose your source and target languages

   Set the language the deck is written in (or leave it on auto-detect) and the language you want it translated into. Auto-detect is reliable on presentations because the text is clean, unlike scanned PDFs where OCR quality can interfere.

3. 3

   Pick a translation engine

   Choose Microsoft Azure for the best formatting fidelity on slides, DeepL for the most natural output on European languages, or Google Cloud for the widest language coverage. Gemini doesn't accept PowerPoint files. The comparison below explains the trade-offs.

4. 4

   Translate the whole deck at once

   Click Translate. The entire presentation is processed in a single operation — no need to go slide by slide. Download the translated .pptx and open it in PowerPoint to review the layout and check for any text that needs resizing.

Which translation engine is best for PowerPoint?

All three engines that accept PowerPoint preserve the overall slide layout, but they differ in formatting fidelity, language coverage, file-size limits, and whether they accept the legacy .ppt format.

The text-expansion problem (and how to handle it)

This is the edge case that catches people off guard with slides specifically. Translated text is often longer than the original — German, Russian, Finnish and Arabic frequently run 20–35% longer than English. In a Word document that just adds a line; on a slide, where every text box is a fixed size, the longer text can overflow the box, get clipped, or trigger PowerPoint's auto-shrink and come out at an awkwardly small font.

A few practical habits keep this under control:

• Leave breathing room in the original. If you know a deck will be translated, don't fill text boxes to the edge — leave 20–30% slack.
• Review every slide after translating. Overflow is easy to spot and quick to fix, but only if you actually open the deck and look.
• Adjust box size or font, not the wording. Resizing a text box or nudging the font down a point usually solves it without touching the translation.
• Watch the languages known for expansion. Pay closest attention when translating into German, Russian, Finnish, Arabic or Portuguese.

Translating legacy .ppt files

Presentations saved before 2007 use the older .ppt format. Two engines accept it directly — DeepL and Google Cloud — while Microsoft Azure requires the modern .pptx. If you want to use Azure:

File size limits and heavy decks

The limits are 30 MB on DeepL, 20 MB on Azure and 10 MB on Google Cloud. Presentations hit these limits far more easily than Word documents because slides are image- and media-heavy. Two ways to get under the limit:

• Compress the media inside PowerPoint — File → Compress Pictures, or Compress Media for embedded video. This often halves a deck's size.
• Split the presentation — save it as two or more smaller decks, translate each, and reassemble afterwards.

Right-to-left presentations work cleanly

Translating a presentation written in Arabic, Hebrew or Persian — or translating into one of those languages — works properly, because .pptx stores text in logical reading order and mirrors the layout correctly. This is the opposite of scanned PDFs, where translating from a right-to-left source is still a limitation. If you have both an editable .pptx and a PDF export of the same slides, translate the .pptx.