Articulate Studio retires December 31, 2026. Your courses keep running.

From Articulate’s Studio 360, Replay 360, and Peek 360 end-of-support guide (accessed November 14, 2026; the date is also on the Presenter 360 product page):

• The date: December 31, 2026, for Studio 360, Replay 360 and Peek 360.
• What stops: Articulate stops providing updates and technical support.
• What keeps working: the apps remain available and functional, and you can keep publishing. Future operating-system updates may eventually cause compatibility problems.
• Published content: keeps working and does not need to be republished, and Review 360 keeps working for these projects.
• What Articulate recommends instead:Storyline 360 or Rise 360 for new Studio-style projects; Storyline 360’s screen recorder, or imported video, in place of Replay 360 and Peek 360.

Most libraries end up using more than one of these, course by course.

1. Leave the published course where it is. If a course is accurate and nobody needs to edit it, the package in your LMS keeps running. Check that it is an HTML5 publish: a Flash (SWF) publish has not played in a current browser since 2020, end of support or not.
2. Move it into Storyline 360 while Studio still runs. Articulate documents a route for each product:
   • Quizmaker: the 32-bit Storyline 360 imports Quizmaker ’09, ’13 and 360 quizzes; the 64-bit version only Quizmaker 360 (Articulate).
   • Engage: Storyline imports Engage ’09, ’13 and 360 interactions, but that Engage must be installed and activated on the same computer (Articulate). Do these first.
   • Presenter: use Storyline’s PowerPoint import with the Presenter .ppta file in the same folder as the .pptx, or only the slides come across. Annotations, attachments, player settings and presenter bios do not import (Articulate).
3. Rebuild Engage interactions in Storyline or Rise. Most Engage interactions (tabs, timelines, process steps, FAQs) map onto a Rise block or a Storyline slide. A rebuild is also the moment to fix keyboard access and reflow on small screens.
4. Migrate to another tool. If you are leaving Articulate, publish each course to HTML5 while Studio still runs and keep the source files (.pptx, .ppta, .quiz, .intr). An HTML5 publish and the PowerPoint behind a Presenter course can be imported elsewhere later; a Flash publish mostly cannot.

1. List your Studio courses and find their source files while the tools still run.
2. Import Engage and Quizmaker projects into Storyline 360 now if you will stay with Articulate.
3. Republish anything still on Flash to HTML5, or mark it for a rebuild, and keep the source files somewhere outside the authoring PC.
4. Retest the courses you keep with a keyboard and a screen reader, then replace the old packages.

Scormbusters does not convert Studio courses. What it does today, checked against the importer:

• The PowerPoint behind a Presenter course imports as an editable course. Its Quizmaker quizzes and Engage interactions are not in the .pptx; you rebuild those from native question and interaction blocks.
• A published Presenter ’09 package:one lesson per slide, named after it, with the slide’s text and speaker notes, read from presentation.xml. Layout, pictures and narration are compiled into Flash and are listed per slide in the import report.
• Quizmaker and Engage Flash publishes: recognized and named in the report, so you are told the content is in Flash instead of getting a misleading partial import. Nothing is converted.
• HTML5 publishes that use Storyline’s data files: read by the Storyline importer. Not yet validated on a real Studio 360 package.

The import scorecardshows the same thing in numbers: from the two real Studio packages we could find, only Presenter’s slide text comes across. That is less than we can do for Captivate or Storyline, and we would rather say so than have you find out after paying. The rebuild preview is free and shows what can be read from yours.