Rise 360 is one of the most widely used authoring tools for responsive online courses. It makes it easy to build clean, mobile-friendly training without managing complex timelines or layers.
But Rise 360 does not translate your course automatically through the standard authoring workflow. You still need to move the content through a translation process, bring it back into Rise, and review the finished course in context.
There are two common approaches:
- Manual translation inside Rise 360
- Exporting the course as an XLIFF file for external translation
Manual translation can work for one short course and one target language. For anything larger, exporting XLIFF is usually the more efficient and controlled option. It gives your translators access to the course text in a structured format and makes it easier to use translation memory, terminology databases, AI-assisted workflows, and quality assurance tools.
Here’s how the process works.
Why Use XLIFF Instead of Manual Translation?
XLIFF stands for XML Localization Interchange File Format. It is an industry-standard file format used to move translatable content between authoring tools, translation management systems, and computer-assisted translation tools.
When you export a Rise 360 course as XLIFF, the file can include much of the text learners see on screen, including:
- Lesson and block text
- Quiz questions and answers
- Knowledge check content
- Titles and instructions
- Text formatting information
- References to course content and assets
Rise 360 uses XLIFF 1.2 for its traditional export and import workflow. Most professional translation tools can work with this format.
XLIFF also gives you more control over the translation process. You can provide a glossary, reuse previously translated content, assign separate translation and editing stages, and track terminology across multiple courses.
There is one important limitation: XLIFF does not translate audio or video content. If your course includes narration, subtitles, or text embedded in a video, you need to handle those separately. That may mean translating subtitle files, creating a new voice-over script, recording new narration, or recreating text that is permanently embedded in a video.
Text baked into screenshots and images also needs separate attention. The standard XLIFF export will not pull that text out for translation.
How to Translate a Rise 360 Course: 7 Steps
1. Duplicate Your Course
Start by creating a copy of the original Rise 360 course for each target language.
From the Rise 360 dashboard:
- Find the course you want to translate.
- Open the course menu.
- Select Duplicate.
- Rename the copy to include the target language.
For example:
Onboarding Training – German
You should keep the original course unchanged. The duplicate becomes the working file for that language and will eventually receive the translated XLIFF.
Create a separate copy for every target language. This keeps your files easier to manage and prevents changes made to one language from affecting the source course or another translation.
2. Export the XLIFF File
Open the duplicated course and go to:
Settings > Translations
Expand the section for traditional XLIFF translation. From there, select the appropriate source language code and decide whether to include HTML formatting.
Including HTML formatting helps preserve elements such as bold text, italics, links, and other formatting applied within the course. It can make the XLIFF file more complicated for some workflows, but removing the formatting may cause that styling to disappear when you import the translation.
Then select Export XLIFF File and save the file.
Keep the exported file tied to the specific Rise course that created it. Rise 360 may reject the file if you try to import it into a different course copy.
3. Translate the Content
You can upload the XLIFF file to a translation management system, or you can work with an eLearning translation partner that manages the process for you.
A complete translation workflow usually includes:
- Translation by a native-speaking linguist
- Editing for accuracy, tone, and readability
- Terminology review
- Formatting and tag checks
- Linguistic quality assurance
- Preparation of the final XLIFF for import
If you use AI or machine translation to create a first draft, make sure the workflow includes human review. A translator who understands eLearning can spot problems that a general translator, or an automated system, may miss.
That includes inconsistent terms, overly literal instructions, awkward quiz feedback, and language that does not sound natural when learners read it on screen.
4. Import the Translated Content Back Into Rise 360
Once the translated XLIFF is ready, return to the duplicated course.
Go to:
Settings > Translations > Import translated text
Select the completed XLIFF file and upload it. Rise 360 will replace the source-language text with the translated content.
If you receive an error that the translation file does not match the content, confirm that you are working in the same course copy used for the original export. Also check that the XLIFF file is complete and that the structural tags and IDs were not changed during translation.
Only the text should be translated. Structural elements, placeholders, and formatting tags should remain intact.
5. Translate the User Interface Labels
The main course XLIFF does not always include every built-in interface label.
These labels may include:
- Next and Previous buttons
- Start Course
- Complete
- Retry
- Menu
- Submit
- Knowledge check instructions
- Navigation and accessibility text
Go to Settings > Labels to review the available options. Rise 360 includes built-in label sets for some languages. If the available set does not fit your project, you may need to edit the labels manually or export and translate the labels separately, depending on your workflow.
Make sure the label language code matches the language assigned to the course. This matters for both the learner experience and assistive technologies such as screen readers.
Do not assume that translating the lesson text completes the entire Rise 360 translation. A course can have accurate body content and still show important navigation elements in English.
6. Complete QA and In-Context Review
This is where you find the issues that do not appear in the exported file.
Publish the translated course to Review 360 and share it with a native-speaking subject matter expert or language reviewer. Ask them to review the course as a learner, not just scan a bilingual document.
They should check:
- Grammar and spelling
- Tone and cultural fit
- Terminology
- Quiz questions and feedback
- Button labels and navigation
- Links and interactive elements
- Accessibility labels
- Text wrapping and layout
- Mobile and desktop views
- Audio, video, and subtitle alignment
A translation can look perfect in a spreadsheet and still fail once it is live in the course. German, Finnish, and many Romance languages often expand compared with English. Longer text can crowd buttons, create awkward line breaks, or push content lower on the page.
Review 360 makes it easier for stakeholders to comment directly on the published course. If you do not have a native-speaking SME available, an eLearning translation partner can provide linguistic and in-context review.
7. Publish
After the language review is complete, make the required corrections and publish the course for the target audience.
Before distribution, confirm:
- The correct language version is being published
- The LMS package settings are correct
- Completion and tracking work as expected
- The course opens correctly on supported devices
- Audio, video, captions, and links function properly
- The translated course has a clear version name
For larger rollouts, keep a record of the source version, translated version, reviewer comments, and publication date. This makes future updates much easier to manage.
What About Articulate’s Built-In AI Localization Tool?
Articulate now offers Articulate Localization, an AI-powered localization workflow directly within Articulate 360. It can provide a fast first-pass translation without requiring you to leave the platform, and it supports multi-language course workflows with in-context validation.
That speed can be useful when you have many courses or tight launch deadlines. But AI translation is not the same as finished localization.
AI-only output can still struggle with:
- Tone and formality
- Idiomatic phrasing
- Industry-specific terminology
- Consistent product names
- Quiz feedback and instructional nuance
- Cultural references
- Customer-facing, compliance, or certification content
It also does not remove the need for layout review and learner testing. Text expansion, crowded buttons, media issues, and incorrect labels still need to be caught during the QA and in-context review stages.
For many teams, the most practical option is a hybrid workflow:
- Use AI to create a fast first draft.
- Have a native-speaking translator with eLearning experience review and correct the content.
- Complete in-context QA in Review 360.
- Publish only after the course has passed linguistic and functional review.
Read our comparison of Transcend and Articulate AI Localization for a closer look at translation memory, human QA, media localization, terminology management, and version control.
Can I Do This Myself?
Yes: if you have the right resources.
You can manage Rise 360 translation internally if you have:
- A translation management system that supports XLIFF
- Qualified translators for every target language
- A terminology list or glossary
- Native-speaking SMEs
- Someone who can perform in-context QA
- Time to manage exports, imports, revisions, and publishing
The challenge is that many L&D teams have only some of these resources. You may have a fluent employee who can review German but no qualified reviewer for Japanese, Arabic, or Brazilian Portuguese. Or you may have translators but no one who understands responsive eLearning layout and accessibility.
That is why many teams use an eLearning translation partner for the full workflow. If you are evaluating providers, our guide on how to choose an eLearning translation partner covers the questions worth asking about authoring-tool experience, QA, terminology, project management, and LMS testing.
Frequently Asked Questions
Can Rise 360 translate courses automatically?
Rise 360’s traditional XLIFF workflow does not automatically translate your content. You can export the course for external translation, or use Articulate Localization for an AI-assisted, integrated workflow. Either way, review is still needed before publishing.
What’s the difference between translating and localizing a Rise 360 course?
Translation converts the words from one language to another. Localization also adapts tone, terminology, examples, imagery, formatting, and learner expectations for the target audience.
Does XLIFF work for video content in Rise 360?
No. XLIFF is designed for translatable course text. Video text, subtitles, narration, and voice-over require separate localization workflows.
How long does translating a Rise 360 course typically take?
It depends on word count, language pair, number of languages, review requirements, and media. A short text-only course may take a few days. A larger course with multiple languages, voice-over, and full in-context QA can take one to three weeks or longer.
If you are planning a Rise 360 translation project, we can review your course structure, discuss the right workflow, and provide a custom quote. Transcend also works extensively with Articulate Storyline: see our complete Articulate Storyline translation guide for the corresponding process.