Storyline's 2025 Year In Review
🎉 Wrapping up 2025 with a grateful (and honestly pretty tired) smile. It’s been a big year for Storyline 360, so I wanted to share a few highlights before we close the book. This year was about making Storyline more helpful in very real, practical ways, not just adding shiny features for the sake of it. A few things I’m especially proud of: 🚀 AI started pulling its weight This wasn’t about slapping a chatbot into the product. We focused on tangible wins that save time and reduce friction. Things like high-quality text-to-speech, automatic captions for audio and video, AI-generated alt text, image generation, and even quiz question generation. These are the kinds of tasks that used to slow authors down but should now feel easy or even trivial. We also introduced AI-generated JavaScript entrance animations, which might look like a small feature on the surface, but it’s actually a big deal for the future of AI in Storyline. We reworked how the AI Assistant chat works and laid the foundation for a whole new wave of AI-powered features. In 2026, we’re excited to keep pushing this further, helping you create objects and triggers, sync things on the timeline, and design better, more interactive courses without needing to be a power user on day one. ♿ Accessibility made meaningful progress The new Accessibility Checker, better screen reader support, Set Focus triggers, and captioning improvements were all driven directly by customer feedback. There’s still more to do, but this year delivered real improvements that authors and learners can feel. 🎨 More expressive interactivity and design tools Fluid morph transitions, new emphasis animations, shape merging, and a new JavaScript API opened up a lot of creative space. Courses don’t have to feel static anymore, and we’re seeing authors do some really impressive things with these tools. 🎥 Media just works better now We made some investments in media support this year for cleaner caption workflows, better playback reliability, and fewer weird edge cases. We also snuck in support for WebM, which enables videos with transparent backgrounds and unlocks some really fun design possibilities. A lot of unglamorous work here, but it makes a big difference day to day. 🛠️ A mountain of fixes and polish Hundreds of quality-of-life improvements landed this year. Some tiny, some massive, all aimed at making the authoring experience smoother and more predictable. None of this happens without customers pushing us, questioning us, and telling us when something feels off. That feedback keeps us honest, so please keep it coming. If you’ve used any of these features, I’d genuinely love to hear what’s working for you and what still feels rough. Tell me straight. What helped the most this year, and where did we miss? Here’s to an even better 2026!Problem with the screen recording in Articulate. HELP!
Hi everybody. Ok, there is a big problem which I am facing. 😬 Screen recording I have. Screen recording as simulation was done by me by selecting an 'x' size of screen size, which is never a trouble maker. Now I put that same recording as simulation where slide by slide test mode was selected by me. Now my smart colleague chose to change the screen size to 720x540. I had kept it 960x540 earlier. Now she wants me to simply copy and paste the slide as shown in below screenshots for ref. I 'simply' copy it and by doing ctrl+v I could duplicate the slide.😒 (Note: this is happening for any slide that I try to duplicate). As shown below in the SS, the recording size or ratio gets distorted and goes out of the slide size or canvas. Since its a recording, I get no option to fix this by adjusting the edges of it like how we increase or decrease the picture or image size. It 'simply' doesn't allow me to have a clean duplicate file or slide of the ones created. Therefore, I seek for help from anyone who could do some miracle. Else, I have to redo everything or to think about some something else. Because these things aren't in my control. Watch the SS attached carefully. Thanks. 😇Suggestion: single triggers that can affect multiple objects, layers or variables.
Greetings, I would like to suggest triggers that can affect grouped objects, layers and variables, Storyline 360. GROUPED OBJECTS If you want to hide multiple assets in a group, you must change their states to Hidden for each of them individually. You cannot say "change state of [group 1] to Hidden", despite Hover states reacting normally. A single command that changes states to "all selected objects" would also be welcomed. GROUPED LAYERS Let's say you have a click-to-reveal in a secondary layer, not the base slide, that calls other layers to reveal text boxes. You must have a trigger that closes each layer individually, because you cannot close that main layer nor hide it. I'd love a trigger that goes like "close [all selected layers from this list]" in one single command. GROUPED VARIABLES If your slide requires variables that must be reset on every visit, you have to trigger them to reset individually. OI'd like to see a trigger that "reset all selected variables to their [initial values]", again in one single command. Please note that while you can choose how to display your triggers, you still need one trigger/"thing". Thanks in advance.Grid and Alignment?
I am not sure what I did wrong but when ever I try to align and group shapes, icons or text boxes they don't line up correctly. I want to group a Shape, Icon and Text box together, but when I do it makes the "Group Box" twice the size than the shape? I am not sure what I am doing wrong? I have gone into the "Grid and Guides" pop out and I unchecked everything and I am still having the same issue?Morph not working with standard states
Greetings, I want to use the Morph transition with buttons that have both Hover and Visited states, using Storyline's own coded states, but to my surprise, the buttons don't follow along, unless I make custom states that I manually program with triggers. This seems like extra work for something that shouldn't be that jarring. Is there any plan to make the Morph transition work with SL's own states? The transition happens a lot of possibilities, but "not working with standard states" and "not working with layers" really grind my progress to a halt. Thanks in advance.Accessibility Issue: All-Caps Button Text
I am currently developing an accessibility-focused course, so it MUST meet accessibility standards. One issue I’ve identified is the use of all caps on buttons, which is not accessible. I can change this for the "Start Course" button; however, in other components, such as button stacks, the text appears locked in all caps. Is there a way to modify this so the button text uses standard capitalization?
