Articulate Localization - Shrink Text on Overflow Bug
Hi all, Articulate Localization is a dream come true that my team and I have been waiting for for years. We are however running into an issue/bug in Storyline 360 with 'shrinking text on overflow' Currently we use the settings you see below. The text of each box is 'wrapped' and if there is too much text the size of the text automatically decreases. This functionality is essential, because it allows you to easily manage multiple translations because if there is too much text then the text simply slinks a little bit to still fit in the box. As a result you don't need to make ridiculously large boxes for lengthy languages like Ukrainian and Bulgarian (these versions of the training then simply have text that has smaller font). However, Articulate Storyline 360 breaks this functionality when there are multiple translations. Here is the Ukrainian Translation for example: As you can see, suddenly, scrollbars have appeared. This should not be possible but it still happened, if you Publish or Preview the Project the scrollbars are still visible. Therefore, our trial of Articulation Localization has come to a very short end because we cannot use this for our clients if the text of each text box does not shrink in other languages other than the source language. Is anyone else experiencing this bug and/or can this bug be resolved so we can use this feature as well. Secondly, when using Upgraded Project Text the option to 'Shrink text on Overflow' disappears whilst this feature is 100% necessary for running multiple translations in the same Storyline file. Japanese uses about 50% of the space Bulgarian uses, so making huge text boxes for everything just because there are languages that need a lot of room means there is also a lot of empty space on other languages. In short, it's MUCH better if Storyline simply reduces the font size of these languages so you don't need to leave insane amounts of room. We are excited about Articulate Localization, but it needs to work perfectly in Storyline 360, because we (on average) would like to have twenty languages running in one file. Best regards. Kaj DekkersArticulate 360 User Guides are Moving!
Hey, everyone! As we get ready to say goodbye to 2025 and hello to 2026, we're setting you up for even greater success in the new year. In the next few weeks, we’re moving the user guides you know and love in ELH over to our other documentation database in Product Support! That means you’ll soon have a “one-stop shop" for all of your Articulate 360 documentation needs. This change will also improve the accuracy and responsiveness of Artie, our AI support agent. (Did you know you can ask Artie to find documentation for you instead of searching?) Unifying our databases enables us to analyze usage more deeply so we can better tailor our documentation to meet your needs. Plus, it gives us more options for translating user guides into other languages to serve our global community. Once everything has been transferred, the directories for the individual user guides you depend on (and may have bookmarked), like those for Storyline 360 and Rise 360, will remain available in ELH for your convenience. When you follow the links to the individual articles, they’ll take you to the Product Support knowledge base. We'll have landing pages for each Articulate 360 product there as well. We have a few more things to put in place before flipping the switch, but the transition should be seamless for you when it happens in the next few weeks. Let us know if you have any concerns or questions in the meantime.Introducing Custom Block Localization (Public Beta)
We’re thrilled to announce an exciting enhancement for all Localization users! You can now translate Custom Blocks in Rise! What’s New With this update, Rise translation now includes Custom Block elements, including: Text Text to speech audio This functionality is now live. Next Steps We’d love to hear your feedback and learn about your experience using this new feature. Your insights are invaluable as we continue refining how teams create localized learning experiences. Refer to the documentation here for more information!AI Voice Availability Differences Between Storyline and Rise – Anyone Else Noticed This?
Hi there, While working with AI voices in Storyline and Rise, I noticed a small inconsistency in the voices available between the two tools. Some voices that appear in Storyline don’t seem to show up in Rise, and vice versa. For example, voices like Jessica — Woman | Young | English | American accent | Dialogue | Cute and Brittney – Social Media Voice – Fun, Youthful & Informative are available in Storyline but don’t appear in Rise (at least in my environment). It’s not necessarily an issue, but it does make it a bit challenging to maintain voice consistency across courses, especially when some modules are built in Storyline and others in Rise. I’ve already raised a support case with Articulate regarding this, but I was curious to check with the community as well. Have you noticed similar differences in AI voice availability between Storyline and Rise? If so, how are you maintaining consistency across projects? Would love to hear your experiences! Thanks!Articulate Localization: what's your feedback?
Hello everyone! I was curious to hear recent feedback on Articulate Localization. When I first tried it when it came out, I was impressed with some functionalities like re-translation. But I encountered a lot of issues with the translation itself. For example, lack of coherence, some texts were not translated at all. Localization has had a few updates since. Is any of you willing to give me feedback on your recent experiences. What you like and what can still be improved? Thank you ! StephanieMy New Go-To Companion for Multilingual Courses
If you’ve ever localized an eLearning course, you already know: it can be a time-consuming process. Export the text, send it to a translator, wait, re-import, fix the formatting, double-check everything, realize something was missed, fix the mistakes, double-check again, publish to SCORM (or whatever format is needed), and done. Well… that works when you only need one translation. But what if you need five, ten, twenty or more translations? You find yourself stuck in a cycle of exporting and importing, while the part of you that loves designing meaningful learning experiences quietly sighs. That’s why I was genuinely excited to dig into Articulate’s new Localization add-on for Rise 360 and Storyline 360. This didn’t feel like just another feature—it felt like a game changer for both me and my customers. So here’s a quick breakdown of what Articulate’s Localization add-on is all about, why it matters for course creators, and just as importantly, why it’s great for our customers too. A New Add-On That Makes Localization Easier Than Ever Articulate’s Localization add-on is a powerful feature available for Rise 360 and Storyline 360 that streamlines the entire process of translating eLearning courses into multiple languages. With support for over 70 languages—including right-to-left scripts like Arabic and Hebrew—it allows you to manage all versions of your course within a single project. It starts with instant AI translation, which helps you quickly generate translated drafts right inside your project. From there, you can invite reviewers to do in-context validation—they can see the translated course as it appears to learners and edit directly within that view, ensuring both accuracy and tone feel right. You also get multi-language workflow management, which means all your translations stay together in one place. No version chaos, no tracking down lost files. And perhaps the most learner-friendly feature: both Rise 360 and Storyline 360 include a built-in language switcher, so learners can toggle between languages inside the course—no duplicate versions or separate links needed. No more juggling files, rebuilding layouts, or managing five different course versions for five different languages. It’s all streamlined and integrated. Articulate’s Localization Add-On Helps Me To Work Smarter, Not Harder Articulate’s Localization add-on makes a real difference in how I approach my work—and not just because it saves time (though it absolutely does). With localization that works fluently together with the same tools I already use, I can keep my momentum. There’s no need to switch between apps, juggle spreadsheets, or figure out where a certain translated sentence ended up. It takes away a lot of the stress and risk. I don’t have to worry that formatting will break, or that content will go missing after a re-import. Everything stays clean and consistent, which means I can spend less time double-checking and more time creating. And the biggest benefit? Everything’s in one place. I don’t have to manage multiple versions of the same course in different folders or try to track which version is the most current. It’s all there, organized, and easy to work with. In short, it’s not just more efficient—it helps me stay in the creative flow, doing the part of the job I actually enjoy. Articulate’s Localization Add-On Helps Me Serve My Customers Better This part is huge—because when localization gets easier for me, the people I build for feel the benefit too. For one, it shortens timelines. Customers no longer have to wait weeks while I manually manage translated versions. With everything in one place and a more efficient workflow, I can deliver multi-language courses faster and with fewer back-and-forths. It also ensures a high-quality, consistent experience for their learners. Each language version maintains the same look, feel, and structure as the original—something that really matters when you’re delivering training at scale. It helps reinforce trust in the learning content and in the brand behind it. Another big win? Customers no longer have to upload and manage multiple SCORM files for each language in their LMS. One course, one upload—with a built-in language switcher that gives their learners the version they need, when they need it. And for customers working across borders or managing global teams, this kind of scalability is a game changer. Whether they need two languages or twenty, they get a process that’s streamlined and repeatable—without added complexity or surprise costs. In the end, it’s not just about efficiency. It’s about helping customers deliver better learning to more people, more confidently. Final Thoughts Localization used to be something I tolerated. Now? It’s something I can actually offer confidently—and even build into proposals proactively. If you’re supporting international learners or working with global customers, Articulate’s Localization add-on is worth exploring. It doesn’t just make your workflow smoother—it makes your courses better, faster, and more flexible. I really appreciate the hard work the team at Articulate has put into this add-on. It’s clear they’ve been listening to the challenges we face—and building real solutions that make our work better. Already tried the Localization add-on? I’d love to hear your thoughts. Drop a comment and let’s swap ideas. About me: Paul Alders LinkedIn Profile The eLearning BreweryIntroducing Localized Timelines!
We heard your feature requests loud and clear! If you’ve ever localized a course, you know that different languages often require timeline adjustments due to variations in syntax, word order, and text length. Until now, making those changes meant impacting your source version. ✨ What’s new? You can now adjust timelines for individual target language courses directly within Storyline, without affecting the source language version. That means: Greater flexibility when localizing Cleaner workflow between source and translated courses No more timeline workarounds to accommodate narration expansion For more detail on how this works, check out the user guide. Install the March 2026 Storyline update (or later) to set per-language timing and duration for each object, cue points, and slide duration, including those on layers and slide masters. Note: Localized timelines are currently in public beta; functionality may change based on feedback.You can now Localize Text to Speech on Rise and Storyline!
We’re thrilled to announce an exciting enhancement for all Localization Pro users! When you translate your course, the script will be automatically translated and new audio will be generated and re-inserted in the target language, saving you time and effort. What’s New With this update, translation now includes: Automatic translation of the script (the text that powers Text to Speech). Automatic generation and insertion of localized audio in your translated course. Validator updates: Validators can now update the script, and importing their suggestion will automatically update the audio as well. This functionality is now live in both Rise and Storyline. Important Note for Storyline Users This update applies to both AI Text to Speech and Legacy Text to Speech shapes. You’ll no longer need to manually replace audio after translation, it’s all handled automatically during the translation process! Next Steps We’d love to hear your feedback and learn about your experience using this new feature. Your insights are invaluable as we continue refining how teams create localized learning experiences.Translation for Custom Blocks, Code Blocks, and Text-to-speech
I was just on David's call and these new features in Rise look really great. I can see a lot of possibilities—if I can get them translated. What are the translation options, processes, and limitations for each of these features? For example, are text boxes in Custom Blocks included in the XLIFF exports? What about text in a Code Block? During the call, David inserted a calculator using a code block. The calculator had a heading at the top. How would I go about getting that heading translated? Finally, if I use the text-to-speech feature, how do I go about getting that text translated so I can generate the speech in other languages? Is it included in the XLIFF file? I'm loving these new features, but everything I do needs to be translated and I'm trying to avoid creating extra work and opportunities for things to get missed. Thanks!
