There's a moment familiar to every team where someone asks for the compliance course in German. The course exists, and it's been running for three years, but it was published from an authoring tool, exported, and uploaded to the LMS, and the source files are on a former contractor's laptop, or in a vendor's archive, or potentially nowhere at all.
The honest answer to "can we get this in German?" has always been: rebuild it. Re-license the tool, reconstruct the course, re-record the media, re-test every interaction. Per language. Most teams, quite reasonably, don't. The course stays in one language and the library everyone paid to produce freezes.
Now, that answer changes.
SCORM Studio, now generally available, translates published e-learning courses directly from the exported package. Upload the file you actually have. Get it back in every market you need, with the layout, media, and interactivity exactly as they were.
Key takeaways
SCORM Studio is generally available and translates a published SCORM course directly from the exported package — no source files, no rebuild, and no authoring-tool license.
The course stays in its original format. Layout, media, and interactivity come back exactly as they were, and depending on the format, subtitles, voice-over, and localized images are handled too.
Courses published from iSpring Suite, EasyGenerator, Adobe Captivate, Absorb Create, and CEGID (Talentsoft / e-doceo) are supported at launch — including courses from tool versions nobody can open any more.
Because it runs on Smartcat, the translation carries your translation memories, your glossaries, and your review workflow.
Translated, not rebuilt
SCORM Studio is non-destructive. Your course stays in its original format. It isn't edited — it's translated, pixel-perfect. Depending on the format, that includes subtitles, voice-over, and localized images.
That distinction matters, because the traditional way to translate a SCORM course has been a string export, where the text comes out but the context doesn't. Layout breaks under a language that runs 30% longer. The media stays in the original language. Interactions go untested. Someone reassembles the whole thing by hand. What comes back isn't the course you sent — it's a reconstruction.
SCORM Studio works on the package itself, so what you upload and what you download are the same course. Push it straight back to your LMS.
And because it runs on Smartcat, the translation carries your translation memories, your glossaries, and your review workflow. Your e-learning course localization ends up consistent with everything else your company publishes.
Which authoring tools are supported at launch
Courses published from:
iSpring Suite
EasyGenerator
Adobe Captivate (Classic and Modern exports, including courses from versions nobody can open anymore)
Absorb Create
CEGID (Talentsoft / e-doceo)
You need no source files and no license for any of these tools.
The point worth hammering home is that the tool your course was built in can be dead. Even if it's gone from the market, unsupported, and unlicensable, the course still translates.
What comes after translation
The request we hear most from teams already using SCORM Studio is about the checking rather than the translation itself.
Traditionally, a team member still has to open every module and review every slide. By slide forty of sixty, things get missed. So we've handed that work to our AI coworkers: they go through translated layouts, flag what looks wrong, and route the judgment call to the person who knows the content.
The goal has always been bigger than translating a file. This is how course libraries stay alive — multilingual, current, and maintainable, whether or not the source files ever turn up. This is how information remains accessible.
Get started
SCORM Studio is in your Smartcat workspace today. If you'd like a walkthrough with one of your own courses, contact us to get started. You can also see how teams are already using it in our session with eBay's L&D team, or read up on dynamic multilingual SCORM packaging.
