For teams building with Adapt Learning
Translate the course. Keep the build green.
Translate Adapt course exports instantly with context-aware AI. Human-level language, protected JSON, CSV and XLIFF 1.2, and 100% valid syntax. No translation-induced build errors. No days lost fixing brackets.
Syntax is not up for translation
You have the translation. Then Adapt refuses to build. One missing comma, an unescaped quote or a renamed system key is all it takes. A rushed copy-and-paste into a general-purpose AI tool turns into days of tracing errors through JSON instead of publishing training. XLIFF inline tags and CSV column mappings are just as unforgiving.
Qopywriter.ai separates the lesson from its scaffolding. Learner-facing text goes to the AI. Property names, IDs, component references and configuration values stay protected. The output is checked before it comes back to you.
Valid, supported JSON, CSV and XLIFF 1.2 exports stay valid. Zero build errors caused by translated file syntax. Existing plugin, theme, dependency and asset issues are outside this guarantee.
The beam edits the string, not the structure. Even the system value text stays out of its path.
Three formats. One protected workflow.
Adapt course translation should fit your toolchain, not force a new one. Each format gets its own structural rules. The AI never treats your course as a wall of plain text.
Titles, body copy, instructions and feedback get translated. Keys such as _id, _parentId and _component stay put, along with nesting, arrays, booleans and asset paths.
IDs stay IDs. A text component stays a text component.
{
"_id": "co-05",
"_parentId": "b-01",
"title": "Bienvenido al curso"
}Adapt Learning CSV translation preserves headers, row identifiers, delimiters and column mappings. A comma in a sentence belongs inside the cell, not at the start of an accidental new column.
Quoted commas and embedded line breaks remain correctly contained.
_id,title,body
co-05,Bienvenido al curso,"Aprende, practica y aplica."Adapt XLIFF localization keeps source segments and translation-unit IDs intact. Inline elements such as <g>, <x/> and paired <bpt>/<ept> tags retain their relationships.
Target text changes. Formatting and placeholders survive the round trip.
<trans-unit id="co-05-title">
<source>Start <g id="1">course</g></source>
<target>Iniciar <g id="1">curso</g></target>
</trans-unit>Export options depend on your Adapt version and localization extension. Qopywriter.ai translates the exported files; your existing Adapt importer remains part of the workflow. Check compatibility details.
Language quality, not just file repair
“Resume” on a course button is a verb, not a CV. Assessment feedback has to make sense beside the question, not just as a sentence on its own. Context matters.
Our AI reads across segments instead of translating each line in isolation. It keeps corporate terminology consistent, respects the learning objective and carries the same instructional voice across the entire Adapt project. The result is human-level linguistic accuracy that rivals professional translation agencies, without an agency handoff for every update.
For legal, medical or high-stakes compliance training, keep a qualified in-language reviewer in your sign-off process. File validation and instructional review do different jobs.
Your learning path
Tu ruta de aprendizaje
Choose a learning path to continue.
Elige una ruta de aprendizaje para continuar.
Learning path completed.
Ruta de aprendizaje completada.
Keep your open-source workflow
Open-source e-learning localization does not need a framework fork or a week of manual repairs. Keep Adapt where it is. Replace the risky copy-and-paste step.
Use the localization export available in your Adapt Authoring Tool installation, or collect the content JSON from your framework project. Keep an untouched source copy and confirm that the original course builds.
Upload JSON, CSV or XLIFF 1.2 and select your target language. Context-aware translation handles the lesson text; format-specific checks protect the keys, column mappings and tags around it.
Reimport through your matching localization workflow. To translate Adapt Framework content directly, place the translated JSON in the intended src/course/<locale>/ folder and set the project language. Build, then check text length, feedback and course layout.
A small but important CLI detail: CSV and XLIFF are interchange formats. Import them back through the matching workflow before building. The CLI compiles the Adapt course project, not a standalone CSV or XLF file.
$ grunt buildPricing for course teams
Every plan includes context-aware AI, JSON syntax protection, CSV column preservation and XLIFF 1.2 tag protection. Start with a trial, test your import, then pick your allowance.
For individual IDs and smaller course updates.
For regular multilingual course production.
For agencies and in-house learning teams.
An annual allowance for planned course releases.
Before your first import
Working with a custom component or an unusual export? Start with a small sample, not your entire course library.
Yes. Adapt Authoring translation works through your existing export and import setup. Upload a supported JSON, CSV or XLIFF 1.2 export, translate it, then reimport through the matching workflow. For framework projects, translate the learner-facing content in your course JSON files. Export options depend on your Adapt version and installed localization extensions. No Qopywriter plugin or framework fork is required.
The tool separates learner-facing text from structural data before translation. Titles, instructions and feedback are translated; property names, IDs, component references and configuration values remain protected. Quotes are escaped correctly and the output is checked as JSON. It is not a prompt asking a chatbot to rewrite your entire file.
Yes. CSV translation preserves headers, delimiters, row identifiers and column mappings, including quoted commas and line breaks. XLIFF 1.2 translation preserves source segments, translation-unit IDs and inline tag relationships while translating target content. Use the same localization extension or importer that produced the export.
The AI delivers human-level linguistic accuracy by reading cross-segment context, maintaining corporate terms and preserving the intent of instructions and assessment feedback. That is the difference between a coherent course and a collection of individually translated strings. The quality rivals professional translation agencies; qualified human review remains part of sign-off for regulated or high-stakes content.
Valid, supported exports stay structurally valid: parseable JSON with protected keys, CSV with intact column mappings, and XLIFF 1.2 with valid XML and protected inline tags. That means zero build errors caused by translated file syntax. The guarantee does not cover pre-existing project errors, incompatible plugins, theme issues, missing assets or broken dependencies. Your normal import, build and course review still apply.
Upload the JSON, CSV or XLIFF 1.2 localization files, not a published SCORM ZIP. After translation, import the files into your source course and publish a fresh package through Adapt. Narration, video subtitles and text baked into images need their own localization work.
Yes. The free trial includes a limited character allowance, with no credit card required. Start with one representative module, including a custom component or tagged segment if your project uses them. Translate it, reimport it and run your usual build before choosing a plan.
First, build the untouched source course. If that fails too, check the reported dependency, plugin or asset error before changing the translation. Next, confirm that the importer matches the export format, the target locale is configured and the files are in the expected location. Read the first build error, not the cascade after it.
Still stuck? Send the error message, your Adapt version and the affected file format to support@qopywriter.ai. Remove confidential course content from any sample you share.
Keep your build green
Start with one module. Translate it, reimport it, run your build. Then move on to the rest.