Can Copilot translate PowerPoint decks without the text overflowing?

TL;DR: Copilot can translate a PowerPoint deck and hand you a new, editable .pptx with the layout preserved, which makes it the strongest chat-tier option we have tested. It has three limits that matter in a deadline week: it does not resize or reflow text that no longer fits its box, it requires a paid Microsoft 365 Copilot seat, and the feature has moved between builds, at one point returning only text in the chat. If overflow is your problem, or you have one deck and no seat, a per-deck service that sets shrink-to-fit on every translated frame is the cleaner path.

People search for "copilot translate powerpoint" because Copilot is already open in the application where the deck lives, and using it costs nothing extra if the organisation pays for the seat. The question that decides whether the result is presentable is narrower than "can it translate", and almost nobody answers it directly: when the German or Japanese text is longer than the English it replaces, what happens to the box? This post answers that, with the sources we have, and shows how to check it on your own build.

How does Copilot translate PowerPoint decks today?#

Our June 2026 research on chat-tier deck translation rated Copilot in PowerPoint as the only purpose-built option among the assistants. Prompted inside PowerPoint, it produces a new editable presentation in the target language with the original layout carried across, rather than a text blob you paste back slide by slide. That already puts it ahead of the Claude add-in, which reads a lossy markdown view of the deck and drops images, and ahead of ChatGPT, whose default is translated text in the chat with a fragile Python route to a .pptx.

Where it sits in the interface has changed. A thread on Microsoft Q&A titled "I am not able anymore to translate PowerPoint presentations with Copilot" records users on version 2504 getting a new translated file from the chat prompt, users on 2508 getting only a textual response in the chat, and users on 2509 and later finding the function again as a translate option on the slide deck itself when opened in PowerPoint for the web, rather than in the Copilot chat pane. One reply notes that colleagues in other organisations did not have the problem at all, which points to tenant rollout as well as build number.

Two practical consequences follow. First, if your prompt returns text instead of a file, the feature has probably moved rather than vanished, and opening the deck from OneDrive in the browser is the recorded workaround. Second, a workflow that depends on a specific button existing on a specific date is a risk for anyone who translates decks for clients on deadlines, and it is fair to weigh that against a tool whose interface is a file upload.

Does Copilot resize text when it translates a slide?#

No, as far as our record goes. The research file we keep cites Microsoft's support documentation as stating that Copilot preserves layout but will not resize or reflow text that overflows after translation, alongside limits of roughly one million characters and 500 MB per file. The support article we cited has since been folded into a general "Edit with Copilot in PowerPoint" page that no longer mentions translation, so we cannot quote the current wording, and you should confirm on your own build. What the documentation as recorded describes is simple: the translated deck opens with the same boxes at the same sizes, and any box whose new text is longer than the old one overflows.

This is the point where "the layout is preserved" and "the deck is presentable" part ways. Preserving the layout means the shapes stay where they were. It says nothing about whether the words still fit in them. English to German expands because German compounds nouns. English to French and Spanish expands through articles and prepositions. English to Japanese changes the width of every character and removes the spaces that line-wrapping depends on. A title box sized with a few millimetres to spare in English has no room for any of that, so PowerPoint pushes the extra text past the bottom edge of the shape or onto the element below.

Copilot leaves that for you. On a ten-slide deck that is a few minutes of dragging handles. On a sixty-slide client readout with tables, it is the afternoon you were trying to save.

What does a tool that fixes overflow actually do differently?#

The fix is a single flag in the file format. A PowerPoint text frame can carry an autofit setting called shrink-to-fit, the option labelled "Shrink text on overflow" in the Format Shape pane. When it is set, PowerPoint and Google Slides recompute a fitting font size when the file opens, and frames whose text already fits are unaffected.

SlideVerso's engine sets that flag on every text frame it writes translated text into. It can do that because it edits the text runs inside the original .pptx structure rather than regenerating slides, so it is working on the same shapes, tables and notes that were in your file, and it never converts a chart or an image into something it cannot put back. Before translation starts, one whole-deck pass locks a glossary, proper nouns and register into a small contract that every translation batch works against, so slide 40 uses the same term slide 3 introduced. Every job either delivers a complete deck or fails and is refunded automatically.

That is the honest difference. Translation quality between Copilot and any other modern model is roughly level, and we do not argue on it. The gap is the last mile: does the text fit, did every graphic survive, is the terminology consistent, and is the output a finished file. Overflow is the piece Copilot explicitly leaves to you.

How can you check this on your own deck in ten minutes?#

Here is a comparison you can reproduce if you have a Copilot seat, and the second half works without one.

Pick a deck of 20 to 30 slides that has one dense title, one table and speaker notes on a few slides. Choose a target that expands, such as German, or one that changes character width, such as Japanese.

Copilot run. Open the deck in PowerPoint for the web from OneDrive, use the translate option on the slide deck (or the Copilot chat, depending on your build), and open the result. Go slide by slide and count the text boxes where the last line is clipped or spills past the shape. Right-click one of them, choose Format Shape, then Text Options, then Text Box, and look at the autofit setting. In our record it is unchanged from the source, which is why the text spilled.

SlideVerso run. Open the app, upload the same .pptx, pick the same target language, and look at the free watermarked preview of one translated slide. The price appears after upload and before payment: $19 for a deck up to 30 slides, $39 up to 80, $69 up to 150. Pay, wait a few minutes for a deck this size, and download. Open the same dense text box, right-click, Format Shape, Text Options, Text Box: "Shrink text on overflow" is selected, and the last line is inside the shape. Open the Notes pane on a slide that had notes and confirm they are translated too.

Then compare the count of overflowing boxes between the two files. That number, rather than any sentence-level quality judgement, is what your client will notice.

When is Copilot still the right choice?#

If your organisation already pays for the seat, the deck is short, the target language is close in length to the source, and you are comfortable fixing a handful of boxes by hand, Copilot is a perfectly good answer and it costs you nothing extra. It is also the only option in the chat tier that gives you an editable file inside the application without an export step.

If any of those conditions fails, and especially if the target is German, Japanese or another language that changes text length, the per-deck route saves the afternoon. There is no seat to buy, no annual contract, and the pricing follows the work: one deck arrives, one deck is paid for. The language pair pages show every supported target with the same three-step flow, and the preview slide is free on each of them, so the cheapest way to settle the question is to upload the deck you are worried about and look.