Translate your MadCap Flare files without copy-pasting
Export your MadCap project to XLIFF 1.2. Upload the file to Redokun. Your translator works in one shared Web Editor — no copy-pasting into Word, no separate terminology spreadsheet to keep in sync.
Once you start, you’ll wonder how you ever managed your technical document translations without Redokun.

Your technical documents already live in MadCap Flare.
Your translation process probably doesn't.
Exporting breaks the connection.
Content gets pulled out of Flare and handed to an agency or freelancer working outside that structure — someone has to reconnect the pieces later.
Terminology drifts.
Without a shared Glossary, the same part number or UI label gets translated differently across manuals, and across languages.
Every update starts from zero.
A product revision usually means re-translating the whole manual again in every language — not just the lines that changed.

Enter Redokun:
From MadCap Flare export to translated document, in one workflow

The same XLIFF 1.2 file format your project already generates — this isn't a dedicated Flare plugin, it's file-format support for what Flare already exports.
No conversion step, no copy-pasting into Word first.
Translation Memory suggests matches from anything translated before. Your Glossary flags the terms that have to stay exact.
See what's done and what's still in progress, without asking.
Ready to bring back into your project.
Upload the file. Everything else happens around it.
- Redokun accepts the XLIFF file your MadCap Flare project exports — the same XLIFF 1.2 format Redokun already supports, not a separate plugin. Your translator opens it in Redokun's Web Editor. Translation Memory suggests matches from anything translated before. Your Glossary flags the terms that have to stay exact.

Every translator sees the same Glossary
- Product names, part numbers, and technical terms — the same words, used the same way, across every manual, datasheet, and language. Nobody has to remember what the last translator called a component three product revisions ago.

Change one line, not the whole XLIFF file
- Every product update brings revisions to manuals and datasheets. Quick Revisions identifies only the segments that changed since the last translation — your translators review what's new, not the whole document again. A revised manual across 8 languages doesn't mean starting from zero in any of them.

Translating XLIFF files with Redokun couldn’t be easier - see for yourself
What manufacturing teams say about translating with Redokun
Two ways to get started right now, depending on your needs.
For one-off translation needs. Ideal if you have less than 4 projects per year.
Keep translations consistent and accurate without sacrificing speed.
For one-off translation needs. Ideal if you have less than 4 projects per year.
Keep translations consistent and accurate without sacrificing speed.
What designers and marketers ask before choosing Redokun.
Your layout comes back exactly as you left it: fonts, styles, formatting, and design all intact. Redokun extracts the text from your InDesign file, lets your translators work on the content in the web editor, and rebuilds the translated file in InDesign format when you export. You get a finished InDesign document ready to use, with no manual reformatting required. The same applies to Word, PowerPoint, and all other supported formats.
If you work with many InDesign files, it’s also useful to know how to create InDesign documents with translation in mind. Feel free to share this best practice and tips to your designers!
DeepL translates text. Redokun translates documents, and gives you back a finished file in exactly the same format as the original. With DeepL alone, you copy text in, get translated text out, and spend hours reformatting the result back into your InDesign or Word file.
With Redokun, you upload the file, generate the draft translation using DeepL, ChatGPT, or Google Translate within Redokun’s Web Editor, let your translators review it online, and export a finished, layout-preserved document ready to send.
Redokun also adds consistent terminology across every project, reuses approved translations automatically, and gives you full visibility into project progress — none of which a standalone translation engine provides.
Sure! Redokun’s free trial is a great way to experience how quickly you can complete your translation projects. It doesn’t require a credit card.
The free trial is based on our Basic plan and gives you access for 14 days.
You can upload a file of up to 100MB, containing up to 20,000 words.
We support various file types, including InDesign (.idml), Microsoft Office (Word, Excel, PowerPoint), HTML, SRT, JSON, XLIFF 1.2, and more. You can check the full list of supported file types here.
Once you start translating your test file and see how it works, if you’d like to continue and complete your translation project, you can simply purchase one of our plans to keep translating.
The Project Pass is designed for one-time or occasional translation projects. It gives you access to Redokun’s core translation workflow for 30 days, with a simple pay-as-you-go pricing model.
Redokun’s subscription plans (Workspace plan) are better suited for teams with ongoing or recurring translation needs, wanting to build a scalable translation workflow. They include advanced features such as translation memory, AI fine-tuning, activity tracking, and long-term workspace access. If you only need to translate a document once or don’t require long-term asset reuse, the Project Pass lets you complete your project quickly without committing to a subscription.












%20(1).png)
