How to Translate a PowerPoint Presentation (and Find the Text It Misses)

To translate a whole PowerPoint presentation, upload the .pptx file to a document translator instead of translating slide by slide. PowerPoint's own Review > Translate command only works on text you select, and Microsoft lists whole-file translation for Word, not PowerPoint (Microsoft Support). But before you upload, spend two minutes finding out where your deck keeps its text. A .pptx is a ZIP package with a separate file for each slide, each set of speaker notes, each slide master and layout, each chart, and each SmartArt graphic (Microsoft Learn). BookTranslator rewrites only the slides and the notes, and you should not assume any other tool reads every part either. Text in the parts a tool skips comes back in the original language.

We built a 3-slide test deck with text in each of those places, wrote a free checker that lists where every piece of text lives, and ran the deck through a local reproduction of the file handling BookTranslator uses. This guide shows what came back translated, what did not, and what to change in your deck first.

Quick Answer: Where Your Slide Text Lives

Only .pptx files are accepted. If you have an older .ppt file, a template (.potx), or a slide show file (.ppsx), open it in PowerPoint and save it as a .pptx first.

Step 1: Run the Checker on Your Deck

Download inspect_pptx_text.py and run it on your file:

python3 inspect_pptx_text.py "Sales kickoff.pptx"

It needs only Python 3, and it reads the file without changing it. It prints a count of text items by location, then lists each one. Here is the summary for our sample deck:

Counts by location:
  charts           cached value                       3
  charts           title/label                        1
  masters+layouts  fixed text (shown on slides)       1
  masters+layouts  prompt (not shown in slideshow)    86
  notes            paragraph                          1
  slides           alt text                           1
  slides           line-break                         1
  slides           mixed-formatting,link-not-on-first-run 1
  slides           paragraph                          8

Paragraphs with split formatting, links, breaks or fields: 2
Text items outside slide/notes paragraphs (charts, SmartArt, masters, comments, alt text): 6

Read it from the bottom up:

• The last line is the number to act on. In our deck, six items sit outside the slides and notes: one footer on the slide master, the chart title, three chart labels, and one alt text. A translator that rewrites only slides and notes will return all six in English.
• "Prompt (not shown in slideshow)" is safe to ignore. These are the "Click to edit Master title style" placeholders that every template contains. They do not appear when you present.
• The flagged slide paragraphs need a look. The next section explains why.

The README describes the sample deck, lists file hashes, and includes the script that builds the deck, so you can repeat the test.

What Happened to Our Test Deck

We ran the sample deck through the paragraph rewrite that BookTranslator's PPTX handler uses, reproduced locally on 2026-10-31. Instead of a real translation, we used a placeholder that adds "[DE]" in front of each paragraph. That keeps the language model out of the test, so the results show only what the file handling keeps, moves, or drops.

BookTranslator returns two files for a PowerPoint task: a translated deck and a bilingual deck. Here is what each one looked like:

Three of these results are easy to miss when you skim a translated deck.

Formatting inside a sentence is flattened. A slide paragraph is stored as a series of "runs", and each run carries its own formatting. To keep the sentence whole for translation, the handler sends the paragraph as one piece and writes the result back into the paragraph's first run. The whole paragraph then takes the first run's formatting. Bold or colored words in the middle of a sentence lose that formatting, and a link on any run but the first one is dropped. This is a fair tradeoff: word order changes between languages, so the bold words often should not sit in the same place anyway. But you need to know to put them back.

Manual line breaks are not kept in place. A Shift+Enter break inside a bullet is not a run, so the words on either side are joined with no space before translation, and the break ends up after the translated text. If your deck uses line breaks to split a heading over two lines or to stack a label, make each line its own paragraph (press Enter instead) before you upload.

Ampersands can come back escaped. PowerPoint stores &, <, and > in escaped form, such as & for &. In our test, that escaped form reached the translator, and the translated slide displayed R&D instead of R&D. With a real translation, the result depends on whether the model returns the escaped form, so after translating, search the deck (Ctrl+F or Cmd+F) for &, <, and > and replace them with the characters they stand for.

The checker flags the first two cases as mixed-formatting, link-not-on-first-run, and line-break, so you can find them before you upload rather than after.

Step 2: Prepare the Deck Before You Upload

Work on a copy of the file. Most fixes take a few minutes even for a long deck, because the checker tells you where to look.

1. Convert SmartArt to shapes. Select the graphic, then choose SmartArt Design > Convert > Convert to Shapes (Microsoft Support). The text moves into ordinary grouped shapes on the slide, which do get translated. You cannot turn the shapes back into SmartArt, which is one more reason to work on a copy.
2. Split manual line breaks. Replace Shift+Enter breaks with real paragraph breaks wherever the checker reports line-break.
3. Note where links and highlighted words are. For each link-not-on-first-run or mixed-formatting paragraph, write down which words are linked or bold. You will reapply them in the translated deck. If a link matters a lot, putting it on the whole sentence, or on its first word, keeps it.
4. Resolve or delete comments. They are not translated, and you probably do not want reviewers' notes sent to a translation service anyway.
5. Leave the master, charts, and alt text for later. There is usually little text in each, so it is faster to translate them by hand in the finished deck than to move them onto the slides.

Step 3: Translate the Whole File

Upload the .pptx on the document translator page, choose the target language, and check the price shown before you pay. A whole-file upload translates every slide and note in one task. That makes it easier to keep a product name or a term the same on slide 3 and slide 30 than translating one text box at a time, though you should still check key terms in the result.

When the task finishes, the History page offers both downloads:

• Translated deck: the version to present. Fix it up as described in Step 4.
• Bilingual deck: every translated paragraph sits under its original in the same text box. Use it to review the translation with a colleague who reads both languages, not to present, because the text boxes now hold twice as much text and will often overflow.

If you only have a few slides, or you already pay for another tool, there are other routes. Google Translate's Documents tab takes .pptx files up to 10 MB (Google Translate Help); our Google Docs translation guide compares its options. DeepL also offers document translation; see what DeepL's document limits mean in practice before you rely on it for a long deck. For Microsoft's own tools, our guide to translating with Copilot explains what PowerPoint's Translate pane and Copilot can do today. Whichever you use, run the checker on the source deck first: the same hidden places hold text no matter which tool does the translating.

Step 4: Fix and Check the Translated Deck

Open the translated deck and go through it in this order.

1. Translate the leftovers. Use the checker's list. Open View > Slide Master for text typed on the master or layouts. Fix any & left by the ampersand issue above. For each chart, select it and choose Chart Design > Edit Data to change category and series names, then edit the title and axis titles on the slide. Re-enter alt text from the picture's right-click menu.
2. Look for overflow. Translations are often longer than the source, and short strings grow the most. The W3C cites IBM guidelines that put the average expansion from English into European languages at 200–300% for text up to 10 characters, and about 130% for text over 70 characters (W3C). Slide titles, button labels, and table headers are short, so check them first. In Slide Sorter view, overflow is easy to spot; fix it by shortening the wording, widening the box, or turning on "Shrink text on overflow" in the text box options.
3. Reapply highlights and links. Use the notes from Step 2.
4. Check numbers, dates, and units. Cells that held only numbers were left as they were, so "1,240" may need to become "1.240" for a German audience.
5. Check right-to-left slides. If you translated into Arabic, Hebrew, Persian, or Urdu, check text direction and alignment on every slide. Our guide to right-to-left translation covers what to look for.
6. Read the notes in Presenter View. Speaker notes were translated, so read them once as the presenter will see them.
7. Have a fluent reader review it if the deck goes to customers, investors, or a conference. A machine translation is a good first draft, not a final one.

Common Problems

If your slides started life as a PDF export, translate the original .pptx instead whenever you can. The PowerPoint file keeps editable text boxes, notes, and charts; the PDF keeps none of them. If the .pptx is lost and only a PDF remains, our guide to translating a PDF while keeping its format is the better starting point.