How to make a bilingual PowerPoint deck: a hands-on walkthrough

Introduction

In trade, consulting, government work, and technical exchange, a PowerPoint translation is less forgiving than Word or Excel. A broken Word file can be reflowed, and a broken Excel file can be recalculated. When a PowerPoint layout breaks — color blocks out of place, arrows pointing at empty boxes, a timeline that no longer meets its nodes — the deck basically has to be rebuilt.

The manual route is familiar: copy the text from each slide into a translation tool, paste it back into the text boxes piece by piece, then adjust the font size, line breaks, and alignment slide by slide. A 9-page deck done this way starts at an hour or two, and you still cannot promise that every slide will match the original.

The PowerPoint add-in in this walkthrough—TopCopilot AI, which treats the whole deck as one piece. It offers two write-back modes:

Direct mode (Translation): the translation replaces the source, and the whole deck becomes English only
Bilingual mode (Bilingual): the original slide stays, and the translation is written on the copied slide beside it, so you can compare page by page

This is the biggest difference between PowerPoint and Word or Excel. In Word, bilingual means two lines in the same paragraph. In Excel, bilingual means two lines in the same cell. In PowerPoint, bilingual means one original slide and one translated slide, placed next to each other. Text boxes on a slide sit in fixed positions, so both languages on the same slide would squeeze each other.

This walkthrough focuses on bilingual mode — in PowerPoint, one Whole presentation and one Start translate the whole 9-page Japanese deck in a single pass: it becomes 18 pages, original and English slides sit in pairs, and the color blocks, arrows, timeline, and diagrams all stay. The run takes 69.0 seconds.

The add-in translates between 14+ mainstream languages. The example below translates Japanese into English.

1. When you need it: which decks should be translated as a whole?

The video uses a real Japanese deck—Japan Digital Agency_Network Connection Plan.pptx (Japan's Digital Agency, a network connection plan), 9 pages in all. Decks like this are typical:

A complete structure: a cover, background and purpose, an overall diagram of the network connection plan, a configuration overview by connection method, a verification table by organization, an icon key, and appendices (overlapping IP addresses and multi-cloud connections)
Dense graphics: color blocks, arrows, a timeline (R4/R5/R6/R7 and the start of LGWAN provision), cloud and dedicated-line diagrams, and a three-column comparison. None of these should move
Terminology has to match: Dedicated line, Local government, and Interconnection router appear again and again, and each one has to be translated the same way throughout
Needs a bilingual view: the Japanese side keeps the original slides on file, and the outside audience presents from the translated slides. One file, two uses

Done by hand, 9 pages and more than three hundred text runs, plus a layout pass on every slide, takes half a day to start. Paste a whole slide through a general translation tool and the text boxes come back scrambled. Labels inside the diagrams are even harder to put back.

2. Walkthrough: from opening the deck to a finished translation

Step 1: Open the deck and start AI Assistant

Figure 1: the original Japanese deck, 9 pages

After you open the PowerPoint file, the top menu bar shows the "AI Assistant" tab. Open it, and the AI Assistant panel opens on the right. The mode at the top is Whole presentation (the whole deck), with Free / Upgrade beside it.

This walkthrough uses only that mode: the whole deck, in one pass.

Step 2: Set the translation options

Figure 2: the AI Assistant panel and Advanced settings

In the panel, set Target language to English, then expand Advanced to see two areas:

WRITE-BACK (write-back mode)

Translation: direct translation, with the translation replacing the source
Bilingual: bilingual, with the original slide kept and the translation written on the copied slide beside it

The panel states Bilingual in plain words: "The original slide stays. The translation is written on the copied slide beside it, so you can compare them."— the original slide stays, and the translation is written on the copied slide beside it, so you can compare them.

TRANSLATION STYLE (translation style)

Translation font: the translation font (it follows the source by default; this walkthrough uses Times New Roman)

This walkthrough uses Bilingual + Times New Roman, and leaves the rest at the defaults.

Step 3: Click Start, scan first, then translate

Figure 3: Scanning the document, and the bottom button changes to Pause

select "Start" . The panel first shows:

Scanning the document...

Don't edit the document during translation, or write-back may miss.

Important: do not edit the slides during translation, or write-back may miss.

The button at the bottom changes to Pause, and you can pause at any time. The panel status also shows the order of work: it scans the whole deck and settles the terminology, then translates and writes back paragraph by paragraph — this matters on proposal decks where the same terms repeat. Terminology is settled first, so a dedicated line does not come out as Dedicated line on the early slides and Private line on the later ones.

Step 4: Progress moves by paragraph, and you check each line on the right

Figure 4: progress 2/339 (1%), with Src / Tr listed on the right

After the scan, progress is counted by paragraph: 2 / 339 paragraph (1%), then it runs on through 34/339 (10%), 52/339 (15%), 93/339 (27%), 124/339 (37%), 162/339 (48%), 199/339 (59%), 239/339 (71%), and 270/339 (80%).

The panel on the right lists each line as Src (source) and Tr (translation), so you can turn the pages and check as you go:

Src September 2024 → Tr September 2024
Src Digital Agency → Tr Digital Agency
Src Dedicated line → Tr Dedicated line
Src Local government → Tr Local government
Src Interconnection router → Tr Interconnection router

One detail is easy to miss: at only 2/339, the status bar at the lower left already shows of 18 — the copied translation slides are placed as soon as translation starts, and the text is written into them page by page.

Step 5: 9 pages become 18, and original and translated slides sit in pairs

Figure 5: in the thumbnail pane, a translated slide follows each original

The thumbnail pane on the left shows how Bilingual is written: the page count goes from 9 to 18 — the Japanese cover on page 1 is followed immediately by the English cover on page 2. The overview diagram is the same, one original slide and one translated slide, and so on through page 18. Original and translated slides sit next to each other, so you compare by turning the page. You do not switch between two files.

Step 6: Layout kept on the overall diagram

Figure 6: the English overview of the network connection plan

On the translated slide, even this most complex overview keeps its layout. The title reads Overall Picture of Verification of Network Connection Approaches, and on the timeline the R4 / R5 / R6 / R7 marks and the Start of LGWAN Provision (Planned) node stay as they are. The three arrows, the A, B, and C color-block columns, and the footer page number are all still there. After the text becomes English, a few boxes wrap onto more lines, but the boxes and connectors do not shift.

Step 7: A three-column overview and the cloud / dedicated-line diagram

Figure 7: the English configuration overview by connection method

The configuration overview is titled Configuration overview by connection method, and the three-column comparison, the cloud and Dedicated line diagram, and the Local public entity A/B boxes all stay. In the panel, the short terms read: desktop study → Desktop study, on-site equipment → Actual equipment.

Step 8: Translating a dense summary table

Figure 8: the English verification table by organization

The verification table by organization is titled Verification Overview by Selected Organization, and the headers, row structure, and bullets all stay: Organization name, Configuration, CSP, Desktop/Actual device, and Verification details. Vendor names such as AWS, Azure, Google Cloud, and OCI are left as they are.

Step 9: The icon key

Figure 9: the English icon key

The icon page is titled About the icons used in the configuration diagram, and the segmented diagram above (Access line segment, Router segment, Line connection segment, and the rest) and the table below keep their structure, with each label replaced by English.

Step 10: Appendix diagrams, original slide beside the translation

Figure 10: the appendix, original slide (Japanese)

The appendix is the densest diagram in the whole deck: how overlapping IP addresses are handled, and an excerpt of the IPSec verification results. The original slide stays in Japanese. That is what Bilingual is for: the copy kept on file does not change by a single character.

Figure 11: the appendix, translated slide (English)

The translated slide beside it is titled Appendix: Handling IP Address Overlap ① – IPSec Approach (Excerpt of Verification Results), and the flow boxes, arrows, and numbered notes all stay. The panel on the right lists every Src / Tr pair so you can check them.

Step 11: The multi-cloud appendix

Figure 12: the English multi-cloud appendix

The multi-cloud appendix is titled Appendix: Support for Multi-Cloud Connectivity, and the Vendor ①/② diagram, the Legend box, and the issue list on the right all stay. In the panel: Cost → Cost, Network design → Network design.

Step 12: Translation finished

Figure 13: Done, 289 paragraphs shown, 69.0s

The panel shows:

Translation finished — 289 paragraph shown, 69.0s

Done

9 pages of Japanese, 339 paragraphs, and the whole deck in 69.0 seconds. Translation is finished, and the button at the bottom changes to Start over (start again) and Cancel. The title of the last translated slide is Classification and organization of issues (Classification and organization of issues), and the last line in the panel adds a note: "The original slide was copied and the translation was written on the next slide."— the original slide was copied, and the translation was written on the next slide.

In one sentence: translate, compare, and keep a copy on file, all in one deck.

3. What it does

Features	Details
Translate Entire Presentation	One Whole presentation, then one Start, translates the whole deck in one pass (this run: 9 pages, 339 paragraphs)
Bilingual comparison	The original slide stays, and the translation is written on the copied slide beside it. 9 pages become 18, arranged in pairs
Direct translation	In Translation mode the translation replaces the source, and the whole deck becomes English only
Layout kept	Color blocks, arrows, the timeline, the three-column comparison, the cloud and dedicated-line diagram, the icon key, and the footer page numbers all stay
Consistent terminology	It scans the whole deck to settle terminology, then translates paragraph by paragraph, so Dedicated line, Local government, and the rest stay consistent throughout
Check paragraph by paragraph	The right side lists Src / Tr for each paragraph, so you can check while turning pages
Translation style	Translation font can be set (Times New Roman in this walkthrough). By default it follows the source
You stay in control	You can Pause during translation, and Start over when it finishes
Speed	This run, 9 pages and 339 paragraphs, took 69.0 seconds for the whole deck

4. Who it is for

Trade and sales: Chinese–English and Chinese–Japanese versions of product proposals and quotation decks
Consulting and delivery: bilingual decks for clients, with the original kept on file and the translation sent out
Government and institutions: an internal reading copy of outside policy papers and technical proposals
Engineering: multilingual versions of architecture notes, verification reports, and other graphic-heavy decks
Marketing and brand: a fast way to produce multilingual launch and roadshow decks

5. Practical advice

Save a copy before you translate: the add-in writes only the translation and does not change the original slides, but save a copy before you start anyway
Do not edit slides during translation: the panel says Don't edit the document during translation, or write-back may miss
Look over dense tables and long sentences: on a page like the verification table, where cells are dense and sentences are long, English runs longer, so a few cells feel tight and two lines may overlap slightly. Turn to that page and look it over before you send it
Set one font before you send it out: the translation follows the source font by default. To match a company template, set Translation font under TRANSLATION STYLE
Use the paired slides when you deliver both languages: original and translated slides sit next to each other, so the Japanese archive and the outside presentation can be the same file. Turn the page to compare

6. Closing

The hard part of translating a deck is not "turning Japanese into English". It is whether the deck can still be presented once the language has changed: color blocks must not slip, arrows must not point at empty boxes, timeline nodes must still line up, and tables must not fall apart.

A good fit:

You actually have a native PowerPoint (.pptx) deck — proposals, verification reports, roadshow materials, and the like.
The slides contain color blocks, arrows, a timeline, diagrams, and dense tables, and you still need to use them after translation.
For a bilingual copy kept on file, or an English-only version when you do not want to rebuild the layout.
You want a draft quickly — this walkthrough: 9 pages, 339 paragraphs, 69.0 seconds.

In short: it is built for native PowerPoint decks that still have to be presented when the translation is done. Save a copy first, do not edit slides mid-translation, and glance at dense tables and long sentences yourself.