What stays the same, what the engine may not touch, and where the guarantee ends.
Four formats, each with its own unit
Slide, section, sheet, and page stay what they were
Slides, boxes and speaker notes stay in place; sections stay; spreadsheet formulas are not touched; in a PDF the text is redrawn and everything else stays byte for byte. Preservation is checked and reported in your format’s unit. More in your documents.
The engine may not touch the structure
Content changes inside the structure that exists
The engine injects translated text into the elements already there. It does not create, delete, duplicate or reorder slides, sections or pages. That is a declared limit: rebuilding a deck, or cutting sixty slides to six, is human work, and SazAI Corpus comes in afterward.
In PDF, preserving means redrawing
Text moves; everything else stays byte for byte
In PDF the text is already drawn, so translating means redrawing. Translated text is repositioned, and a longer sentence can fill the space differently. Objects that are not text stay byte for byte the same. The translated PDF comes out with a substitute font, labeled as a derived rendering. Script limits are in languages.
What preservation does not promise
Structure is measured; the visual check stays yours
The product counts elements and measures the risk of a box overflowing. It does not look at the final page: there is no visual checker in the product today. Every element can be translated and a box can still overflow, because German runs longer than English. The risk is reported; the last look is yours. More limits in trust.
And today's state, dated. Translation stopped on 2026-08-23 when the provider credit ran out; the last complete translation job finished that day at 02:26 UTC. The credit was restored on 2026-09-30, and the next complete run will date this line. This page describes the capability and does not invite a live test until that run exists.
What comes back with the delivery: differentials.