Four formats, each with its own unit

Slide, section, sheet, and page stay what they were

Your presentation comes out with the slides, the boxes, and the speaker notes in place; your document, with the sections; your spreadsheet, with the sheets, without touching the formulas; your PDF, with the text redrawn over the page and everything else identical, byte for byte. The text changes language; everything else stays. The unit is not a detail of vocabulary. A presentation has slides, a spreadsheet has sheets, a PDF has pages that are already the final rendering. The product speaks to you in the word for your format, not the word for the most common format, because it is in that unit that preservation is checked and reported to you. The X-ray for each format is in [your documents](documents).

Layout stays because the engine does not have permission to touch it

It changes content inside the structure that exists, and that boundary is declared

Preservation is not a best-effort attempt: it is the consequence of a boundary. The engine changes content inside the structure you already built. It injects the translated text into the elements already there. It does not create, does not delete, does not duplicate, and does not reorder your slides, your sections, or your pages. This is a declared limit, not an open item. Your guarantee that the structure comes out the same as it went in depends exactly on the engine not touching it, and the two things cannot both be true at once. If your case is rebuilding a deck from scratch, or cutting sixty slides down to six, the structural work is human, and SazAI Corpus comes in afterward, to transform and prove it.

inthe boxes where the author placed them

translatesthe content, never the container

outthe same boxes, another language

What changes is what is inside the elements. The grid that positions them is not touched.

In PDF, preserving means redrawing

The text changes position; what is not text stays byte for byte the same

PDF is the only one of the four that is not an office format. In the other three, text is stored as letters, and the program that opens the file decides how to draw it. In PDF, the text is already drawn at a position, and translating means redrawing over the page. This has consequences we prefer to tell you before the purchase. Your translated text is repositioned, so a longer sentence can occupy the space differently. The objects that are not text stay byte for byte the same, which keeps your file auditable. A viewable translated PDF always comes out, with a substitute font, labeled as a derived rendering. And the writing restrictions that come from this, with the reason for each, are in [languages](languages).

What preservation does not promise

Structure is measured; the visual check stays yours

This is where this page stops selling to you. The product measures structure, counts elements, and measures the risk of a box overflowing. It does not open your final file, look at the page, and say it turned out nice. There is no faithful visual checker inside the product today, and we are not going to tell you there is. In practice: the system can state that every element was translated and injected, and a box of yours can still overflow because German runs longer than English. The risk is measured and reported to you; the last look is human, and it is yours. This, and the rest of the boundaries, are in [trust](trust).

And today's state, dated. Translation has been down since 2026-08-23 on provider credit, and the last successful run was on 2026-08-20 at 22:43 UTC. This page describes the capability and does not invite a live test until that returns.

What comes back with the delivery, and proves the structure arrived intact, is in [differentials](differentials).