Blog·
How to translate a Keynote presentation (and why .key is the hard case)
Apple Keynote has a built-in translate feature that works one selection at a time, and almost no translation tool reads .key files. Here is the export route that actually works, what the round trip costs, and how to decide where the deck should end up.
- keynote
- apple
- file-formats
- workflow
TL;DR: Keynote's built-in translate handles one selection at a time, which is fine for a phrase and unusable for a deck. Almost nothing on the market reads .key files directly, because the format is proprietary and undocumented. The workable route is export to .pptx, translate that, and then decide — based on where the deck has to be presented — whether to import it back into Keynote at all.
If you build in Keynote, you have probably already discovered that the translation tooling ecosystem behaves as though you do not exist. That is not an oversight and it is not personal. It is a consequence of the file format, and understanding why makes the workaround obvious instead of annoying.
Can Keynote translate a whole presentation?
No, and it is worth being precise about what it does do, because the feature exists and is easy to mistake for more than it is.
Apple ships system-wide translation and Keynote exposes it. On a Mac you select text, Control-click, and choose Translate; on iPhone and iPad you select text and tap Translate. You can then copy the translation or replace the selected text with it. Apple's own documentation describes it in exactly those terms: a selection-level operation.
For a sentence in a slide you are editing, this is excellent. For a 60-slide deck it is a repetitive strain injury. Every title, every bullet block, every label in every diagram, every speaker note, one at a time, with no record of what you have already done and nothing to catch the box you skipped. People do it anyway, once, and then go looking for a tool.
Keynote also has a separate feature that gets confused with this one: formatting a presentation for another language and region, which sets how numbers, dates, times and currency are displayed in tables and charts. That is localisation of formats, not translation of words. It is genuinely useful after you have translated the deck, and it does nothing to the text.
Why does almost no translation tool support .key files?
Because of a difference in what the two file formats are.
.pptx (PowerPoint) | .key (Keynote) | |
|---|---|---|
| Specification | Published open standard, documented | Proprietary, no public specification |
| Internal structure | A zip archive of XML parts anyone can read | An Apple package with binary payloads |
| Library ecosystem | Mature, in every mainstream language | Effectively none for editing |
| Cost to build a translator for it | Days, using existing libraries | Reverse engineering, and it breaks when Apple ships a new version |
| Who writes tools for it | Everyone | Almost nobody |
That last row is the whole story. A vendor deciding which format to support looks at that table and picks .pptx. Even the tools that advertise Keynote support are, in most cases, converting to something they can handle, translating that, and converting back — the same round trip you would do yourself, performed behind the curtain and charged for.
Which is fine, as long as you know it is happening, because the round trip has a cost and you should be the one deciding whether to pay it.
What does the export round trip actually cost?
Keynote exports to PowerPoint through File, Export To, PowerPoint. Keynote also opens .pptx files. So the loop is available in both directions, and how lossy it is depends entirely on what your deck is made of.
Usually survives cleanly: text boxes, standard fonts, images, tables, charts built in Keynote, basic builds and transitions.
Usually does not: Apple-specific transitions such as Magic Move, which has no PowerPoint equivalent and is approximated or dropped. Custom fonts that are not installed wherever the file is next opened. Some animation timing and layering. Keynote-specific theme placeholder behaviour, which converts into PowerPoint's own layout model imperfectly.
The practical advice follows from that split. Do the round trip once, at the end of the editing cycle, rather than repeatedly through a deck's life. Each conversion is an approximation, and approximating an approximation is how a deck slowly stops looking like the one you designed. If the deck is heavily animated, consider replacing Apple-only transitions with standard ones before exporting rather than after, so you choose the substitution instead of letting the converter choose it.
Where should the translated deck end up?
This is the decision that determines your whole workflow, and it is usually made by accident. Make it deliberately.
It has to be presented from Keynote, on a Mac, by you. Export to .pptx, translate, import back, then spend fifteen minutes fixing the transitions the round trip disturbed. Worth it if the animation is part of the pitch.
It has to be presented by someone else, somewhere else. Almost always a Windows machine or a conference room laptop, which cannot open .key at all. Export to .pptx, translate, and stop there — ship the .pptx. You skip half the round trip and the recipient can actually open it.
It is going out as a fixed document. A leave-behind, an attachment, something for a portal. Export to .pptx, translate, export to PDF. Nothing to break and nothing to substitute on the viewer's machine.
It is a template you will reuse in many languages. Keep the master in Keynote, do the translation from a single exported .pptx per language, and never import translations back into the master. One source, many outputs, no accumulating conversion damage.
Notice that in three of those four cases the answer is that the translated deck lives as a .pptx and the round trip is one-way. That is the option people miss, and it is usually the right one.
A checklist for a Keynote deck going multilingual
- Finish the deck first. Translate a frozen deck, not a live one.
- Decide where it ends up using the four cases above, before you export anything.
- Neutralise Apple-only effects if you are round-tripping — swap Magic Move for a standard transition yourself.
- Export once via File, Export To, PowerPoint.
- Open the exported
.pptxand check it before translating. Any damage here is conversion damage, and confusing it with translation damage later will waste an afternoon. - Translate the
.pptx, including speaker notes. - Check the layout in the target language. Text length changes and Keynote's tight, typographic layouts have less slack than the average PowerPoint. The failure patterns are in what breaks when you translate a deck.
- Import back only if case one applies, and check the transitions afterwards.
Step 5 is the one people skip and the one that saves the most time.
Where does SlideVerso fit?
SlideVerso works on .pptx, which means it sits at step 6 of that checklist rather than at step 1. It will not take a .key file, and we would rather say so here than let you find out at the upload screen.
What it does at step 6 is the part that matters after a conversion: it edits the text inside the exported file rather than rebuilding the slides, so whatever survived the Keynote export survives the translation unchanged. Speaker notes are translated with the deck. Pricing is per deck by slide count — $19 or ¥2,980 up to 30 slides, $39 or ¥5,800 up to 80, $69 or ¥9,800 up to 150 — with no subscription, which suits Keynote users well, since decks that start in Keynote tend to be individual set pieces rather than a monthly production line. One slide comes back watermarked and free before you pay.
If you are weighing this against the other options, including the ones that will take a .key file by converting it for you, we compared the field in PowerPoint translation tools compared.
Frequently asked questions
Can Keynote translate a whole presentation at once? No. Apple's Translate works on a text selection — Control-click on Mac, tap Translate on iPhone and iPad — and can replace the selected text with the translation. Translating a full deck means repeating that for every text box and every note.
Why do so few tools support .key files?
.key is a proprietary Apple package with no published specification, while .pptx is a documented open standard with mature libraries in every language. Supporting Keynote natively means reverse engineering that breaks with each Apple release, so most vendors target .pptx and expect an export.
Does exporting Keynote to PowerPoint lose formatting? It can. Apple-only transitions such as Magic Move, uninstalled custom fonts and some animation timing do not survive cleanly. Plain text-and-image decks usually convert without trouble. Export once, check the result before translating, and keep conversion damage separate from translation damage.
Frequently asked questions
- Can Keynote translate a whole presentation at once?
- No. Apple's built-in Translate works on a text selection — select text, Control-click on Mac or tap Translate on iPhone and iPad, then replace the text with the translation. It is a per-selection tool, so translating a long deck means repeating it for every text box on every slide.
- Why do so few tools support .key files?
- Because .key is a proprietary Apple package format with no published specification, unlike .pptx which is a documented open standard. Building a reader for it means reverse engineering, so most translation vendors target .pptx and expect you to export.
- Does exporting Keynote to PowerPoint lose formatting?
- It can. Apple-specific transitions such as Magic Move, some custom fonts and certain animations do not have PowerPoint equivalents and are approximated or dropped. Straightforward text-and-image decks usually survive the export cleanly; heavily animated ones do not.