Feature
Translate inside Word and PowerPoint.
The TranslateX add-ins translate documents where they are being written: in place, in Office, with one command for a whole deck. No copy-paste round trips, no reformatting afterwards.
Why add-ins
The worst translation workflow
is the copy-paste one.
Copy a paragraph out of Word, paste it into a website, copy the result back, fix the formatting it destroyed, repeat for forty pages. The Office add-ins delete that loop: the translation happens inside the document you already have open.
Inside Word
Translate the document you are writing.
The Word add-in translates directly in the document: no exporting, no pasting into a browser, no reformatting when the text comes back. Styles, headings, and tables stay what they were, and the translation lands where the original text stood.
- Translate in place while you work, without leaving Word
- Formatting and structure preserved, so nothing needs rebuilding
- The same engine and language pairs as the rest of TranslateX
The same engine, glossary, and layout rules behind every surface.
Inside PowerPoint
"Translate all slides." One command, whole deck.
Decks are the format where copy-paste translation hurts most: dozens of text boxes per slide, each one a chance to break the design. The PowerPoint add-in translates a slide, or the entire deck with Translate all slides, while the slide structure stays intact.
When the deck crosses writing directions, Arabic to English or back, TranslateX applies the same RTL and LTR handling as everywhere else, so the translated deck reads naturally.
Arabic & RTL excellence →One command translates the whole deck. Text boxes, titles, and tables stay in structure.
Who this is for
For the person who lives in the document.
Batch translation suits the archive; the add-ins suit the deadline. When Reem Al-Suwaidi, the communications director in our sample workspace, has the Arabic press release open in Word at 4 p.m. and needs the English version approved by 5, the translation has to happen in the document she is already editing, with the edits she is still making.
The add-ins make translation part of authoring instead of a step after it. Draft in one language, translate in place, adjust the wording, and the file that leaves Word is the file that gets published. For decks, the same rhythm: finish the Arabic board pack, run Translate all slides, and review the English deck in the same PowerPoint session.
- No export-import cycle, so version confusion never starts
- Review and adjust the translation in the native editor
- Works with the file you have open, not a copy somewhere else
Same engine everywhere; pick the door closest to where the work already is.
Beyond Office
One engine, every surface where text lives.
Word and PowerPoint
Add-ins bring TranslateX into the two Office apps where institutional documents are actually made, with no round trip through a browser.
Inside WriteX
Document translation is also available inside WriteX, Lisan's writing platform, so drafting and translating can happen in one place.
Browser and API
Browser extensions and an API with SDK exist at the Lisan platform level, for web content and for teams wiring translation into their own systems.
Consistency included
The add-ins follow your rules too.
Translating inside Office does not mean escaping governance. The same glossary terms, translation memory, and organizational style that apply on the web platform apply through the add-ins, so a contract translated inside Word uses the same approved terminology as one translated in a batch job.
- Glossary terms enforced in every surface
- Your organization's writing style applied consistently
- One place to manage terminology, every door benefits
Same rules whether the job starts in a folder, in Word, or in PowerPoint.
Frequently asked questions
Which Office applications does TranslateX integrate with?
Microsoft Word and Microsoft PowerPoint. In Word you translate the document you are editing in place; in PowerPoint you can translate a slide or the entire deck with Translate all slides.
Do I still have to fix the formatting after translating?
No. The point of the add-ins is removing the copy-paste-reformat loop entirely. Text is translated in place and the document structure stays intact. See layout preservation.
Do the add-ins use my glossary and style guide?
Yes. The same glossary enforcement, translation memory, and organizational style apply through the add-ins as through the web platform and desktop app. See style governance.
Is TranslateX available outside Microsoft Office?
Yes. Document translation is also available inside the WriteX writing platform, and browser extensions plus an API and SDK exist at the Lisan platform level. The Windows desktop app covers files and screens.
Can the add-in translate a deck from Arabic to English?
Yes, and it applies TranslateX's native RTL and LTR handling while doing it, so an Arabic deck comes out as a naturally reading English deck rather than a direction-confused one.
Translate the document. Keep the design.
Right-click a file, work inside Office, or press F6 on anything on screen. TranslateX returns the same document in the other language: fonts, tables, and layout intact, terminology on brand.
Arabic, English & more · Layout preserved · On-premises available