Translate training documents without breaking the layout.
Manuals, slide decks, workbooks, job aids. Upload a DOCX, PPTX, XLSX, HTML file, or PDF, pick one of 13 languages, and get back a file that opens, reads, and works like the one you uploaded — with a fidelity score to prove it.
What each format keeps. Honestly.
Different formats make different guarantees possible. Here is exactly what survives translation in each one — including the one case where the output is rebuilt rather than preserved.
DOCX
Headings, styles, lists, tables, and inline formatting are preserved. Bold stays bold, your heading hierarchy stays intact, and the translated file opens in Word like the original did.
PPTX
Slides keep their layout, with text translated inside its original placeholders. Because translations run longer or shorter than English, the fidelity report warns you when text boxes are at risk of overflowing.
XLSX
Cell text is translated in place; formulas, numbers, and sheet structure are left alone. A training tracker or glossary workbook comes back organized exactly as it went in.
HTML
Markup is preserved and text is translated between the tags. For Arabic, the document direction is set to right-to-left so the output renders correctly in the browser.
PDFs are a print format, not an editing format, so Lokalizeit returns a clean, rebuilt text PDF — readable, well-structured, and faithful to the content. It is not a pixel-for-pixel visual replica of the original design.
Every file gets a fidelity score.
A 0–100 score per file tells you whether the structure survived: completeness, formatting markers, number and link integrity, length sanity, and untranslated-segment detection. The warning list points at exactly the segments worth a human look, so review effort goes where it matters.
Read the methodologyCourses go through the same pipeline.
The same translate-in-place approach handles SCORM course packages from Articulate Storyline and Rise 360 — upload the exported zip, download an LMS-ready translated package. And for Arabic, documents and courses alike render right-to-left, with English terms preserved inside Arabic sentences.
How SCORM translation worksDocument translation questions.
- Will my translated PDF look identical to the original?
- No, and we say so up front. PDF output is a rebuilt text PDF: the content, order, and structure are preserved in a clean layout, but it is not a visual replica of the original design. If you need the original look, translate the source DOCX or PPTX instead — those keep their formatting.
- Which languages can I translate into?
- Thirteen target languages: Spanish, French, German, Italian, Portuguese, Russian, Hindi, Chinese, Japanese, Korean, Arabic, Turkish, and Swahili. The source language is English. Arabic output renders right-to-left.
- How do I know the translation is complete and intact?
- Every file gets a fidelity score from 0 to 100 measuring completeness, formatting preservation, number and link integrity, length sanity, and untranslated-segment detection — plus a warning list naming exactly which segments to review.
- What happens to numbers, links, and email addresses?
- They must come out exactly as they went in. The fidelity score includes a dedicated number-and-link integrity check that flags any segment where a figure changed or a link was dropped.
- What does document translation cost?
- Per word, per quality tier — you see the exact credit cost before you confirm. Repeated segments are billed at 10% of the per-word rate and fuzzy matches at 70%, so recurring boilerplate gets cheaper. Signup includes 2,000 free credits.
- Can you translate whole training courses too?
- Yes. SCORM course packages exported from tools like Articulate Storyline and Rise 360 go through the same pipeline: upload the zip, get back an LMS-ready translated package. See the SCORM translation page for how that works.
Try it on a real document.
Upload a file, see the exact quote, and judge the output with its fidelity score. No card required.