Blog·
Translating a .pptx and keeping the speaker notes
Speaker notes are the first thing a translation workflow drops, because most routes only read the slide surface. How notes are stored in a .pptx, which tools translate them, and how to check yours survived.
- speaker-notes
- pptx
- workflow
- powerpoint
TL;DR: Speaker notes live in separate XML parts inside the .pptx, not on the slide, so any translation route that works from the visible slide surface silently leaves them in the original language. That includes copy-pasting into a chat assistant and most screenshot-based workflows. To translate a .pptx and keep the speaker notes, you need a tool that opens the file and walks its notes slides. SlideVerso extracts each slide's notes as a separate translatable block and writes the result back into the same notes slide, in place.
You find out about this at the worst possible moment. The deck is translated, the slides look right, you open presenter view to rehearse, and every note underneath is still in English. Nothing errored. Nothing warned you. The tool did exactly what it was built to do, which was translate the slides.
Where are speaker notes actually stored in a .pptx?
A .pptx is a zip archive of XML parts. Open one with an unzip tool and you will find ppt/slides/slide1.xml, slide2.xml and so on, each holding the shapes, text boxes, tables and placeholders that appear on that slide.
Speaker notes are not in those files. Each slide that carries notes gets its own part under ppt/notesSlides/, typically notesSlide1.xml, joined to its slide by an entry in the relationships file. A notes slide is itself a slide in the format's terms, with its own shape tree, and the text you typed sits in a body placeholder inside it.
That separation is the whole story. A program that opens the deck, iterates the slides, and translates the text it finds in each slide's shape tree is behaving correctly and will never touch a single note, because the notes were never in the collection it iterated. There is no error to raise. The deck is complete, and half the content of it is untranslated.
The same separation explains why notes are so often missing from a comparison table. Whether a tool handles them is not a quality difference, it is an architectural one: did the author walk the notes relationships or not.
Which translation routes keep the notes, and which drop them?
| Route | Reads the file? | Speaker notes | Notes |
|---|---|---|---|
| Copy-paste slide text into a chat assistant | No | Never | You are pasting what you can see; notes are not on screen |
| Screenshot or image-based translation | No | Never | Same reason, plus no editable output |
| Copilot in PowerPoint | Yes | Yes, per Microsoft's documentation, which lists speaker notes and comments | Needs a paid seat; does not fix overflow |
| Microsoft's older Presentation Translator add-in | Yes | No — translates slide content, not the notes below | Legacy add-in, different product |
| Dedicated .pptx translation tools | Yes | Usually; several state notes and chart data explicitly | Verify per tool, it varies |
| SlideVerso | Yes | Yes — each slide's notes are extracted as their own block | Written back into the same notes slide |
Two practical lessons come out of that table. The first is that "translate my PowerPoint" inside a chat window is a different operation from translating the file, and the notes are the clearest evidence of the difference. We wrote up the rest of that gap in what ChatGPT can and cannot do with a .pptx.
The second is that two Microsoft features, shipped years apart under the PowerPoint banner, behave differently on this exact point. The current Copilot documentation lists speaker notes among the text it translates. The older Presentation Translator add-in stopped at the slide. If someone on your team says "PowerPoint translates notes" and someone else says it does not, they are probably both right about different tools. What Copilot does not do is resize text that no longer fits, which is a separate problem we covered in Copilot's translation limits.
How does SlideVerso translate the notes?
By treating them as content, not as an afterthought.
When the engine opens your .pptx it walks each slide and extracts every text-bearing element into an addressable block: shapes, text boxes, table cells, SmartArt nodes, chart labels, and the notes slide. Each slide's notes get their own identifier of the form slide<N>_notes, so the notes are a first-class block in the same extraction pass as the title, not a special case bolted on afterwards. If python-pptx cannot see a notes slide for a given slide, the extractor falls back to reading the notes XML part directly, because real-world decks are full of files assembled by tools that wrote valid XML with unusual relationships.
Those blocks then go through the same pipeline as everything else. A whole-deck coherence pass runs first and locks a glossary, the proper nouns, the register and the section headings into a contract that every translation batch works against. That matters more for notes than people expect: notes are where a presenter's shorthand for a product or a metric lives, and a deck whose slides say one thing and whose notes say another is worse than a deck where both are wrong the same way.
On the way back out, translated text is written into the runs of the existing notes text frame rather than into a freshly created one. Run properties are copied wholesale from the source run onto the translated run, which is why bolded emphasis and size changes inside your notes survive instead of flattening to a default. The images, charts and everything the engine did not need to change are never rewritten at all, which is the same reason the slide layout survives.
How do I check my notes actually got translated?
Four checks, about two minutes, and worth doing on the first deck you run through any tool.
- Open presenter view, not the editor. View, then Presenter View, or start the slideshow with two displays. This is the view you will actually be reading from, so check it in the state you will use.
- Pick a slide you know has long notes, not slide 1. Title slides often have no notes at all, and a spot check on an empty notes pane tells you nothing.
- Check a slide in the middle and a slide near the end. Tools that batch work sometimes truncate; a note on slide 3 proves less than a note on slide 52.
- Look at formatting inside the note. If you had a bolded line or a bulleted list, confirm it is still bold and still bulleted, rather than one flat paragraph.
If you want to run this against your own deck before paying anything, upload it at the app and look at the free watermarked preview slide, then check the price band for your slide count: $19 or ¥2,980 up to 30 slides, $39 or ¥5,800 up to 80, $69 or ¥9,800 up to 150. Every job either delivers a complete deck or fails and is refunded automatically.
Frequently asked questions
How do I translate a .pptx file and keep the speaker notes? Use a route that opens the file and reads its notes slides, rather than one that works from the visible slide surface. Copy-pasting into a chat assistant can never include notes, because they are not on screen and not in the slide part of the file.
Does PowerPoint translate speaker notes? Microsoft's Copilot documentation lists speaker notes and comments among the text it translates. The older Presentation Translator add-in translated slide content but not notes. Check which one you are using.
Where are speaker notes stored in a .pptx?
In separate XML parts under ppt/notesSlides/, one per slide that has notes, linked to the slide by a relationship. A tool that only reads the slide parts will not see them.
The language pair pages list every supported target, and notes are translated on all of them.
Frequently asked questions
- How do I translate a .pptx file and keep the speaker notes?
- Use a route that reads the notes slides inside the file rather than the visible slide surface. Copy-pasting slide text into a chat assistant never includes notes, because they are stored in separate parts of the .pptx. Tools that parse the file itself, including SlideVerso, extract each slide's notes alongside its shapes and write the translation back into the same notes slide.
- Does PowerPoint's own translation feature translate speaker notes?
- It depends on which feature. Microsoft's documentation for Copilot in PowerPoint lists speaker notes and comments among the text it translates. The older Presentation Translator add-in translated slide content but not the notes below it. Check the specific tool rather than assuming, because both have shipped under the PowerPoint name.
- Where are speaker notes stored in a .pptx file?
- In separate XML parts. A .pptx is a zip archive, and each slide that has notes gets its own notesSlide XML file under ppt/notesSlides/, linked to the slide by a relationship. That is why a tool reading only the slide parts silently returns a deck with untranslated notes.
- Will my notes formatting survive translation?
- It survives when the translation is written back into the existing notes text frame rather than into a new one. SlideVerso edits the text runs in place, so run-level properties such as bold, size and font are copied onto the translated runs. Notes with heavy manual formatting are worth checking on the first slide.