Meet StoryDraft: turn your content into an editable Storyline project

Your storyboard is ready. Your PowerPoint has the material. Or you have a published course that needs rebuilding, but no editable source.

The next step is usually a lot of assembly: moving text, placing pictures, building questions and wiring up the parts that make a course work.

StoryDraft is now live. It uses AI to turn your content into a real Articulate Storyline .story project, ready for you to open, edit and finish.

It is a starting point for instructional designers and Storyline developers, not a promise that the first build is ready to publish.

Start with the content you already have

You can bring a Word storyboard or training manual (.docx), a PowerPoint deck (.pptx), or a supported extracted-course ZIP.

A clear storyboard gives StoryDraft more to work with: learner copy, images, questions, answer keys and descriptions of the interactions you want. A manual or presentation provides a different starting point. The AI can plan learning activities around that material, but your review still matters.

For a legacy course, extraction comes first. StoryDraft does not open arbitrary published SCORM packages directly. Use CourseGraph to extract the course, then bring a supported extraction pack into StoryDraft to rebuild it as an editable Storyline draft.

Review before you build

After upload, review the course title and accent color, check the image matches, and read the source findings before generating the project.

Images come from your source material. Unclear matches are presented for you to confirm. Missing material and unsupported behavior are called out in the conversion report rather than silently disappearing.

That report gives you a useful handoff into Storyline: what was built, what was adapted, and what still needs attention.

Editable means more than text on slides

The output is a native .story project, not a collection of slide screenshots. Text remains editable. Supported questions become native questions. Buttons, variables, triggers and supported animations can be changed in Storyline.

The builder supports six native question types: multiple choice, multiple response, true/false, fill in the blank, sequence and matching. It also supports text-entry fields, sliders, layers, navigation, motion paths and learner-triggered animations.

What appears in your draft depends on your source and conversion path. A feature the builder supports is not a guarantee that the AI will reproduce every interaction in an uploaded file. See the feature matrix for the details.

You still own the finishing work

Download the project and open it in Articulate Storyline. Check the wording, layouts, image placements, questions and learner behavior. Finish the parts that need your judgment, then preview and test before publishing.

StoryDraft does not generate missing artwork or narration. Complex source scripts need manual review, and unsupported interactions may remain as authoring notes. Compatibility across Storyline versions, LMS publishing behavior and accessibility certification require separate testing.

The point is to spend less time assembling the first draft and more time making the course right.

Try it with a course you know

Start with a storyboard or a short presentation you can easily check. Upload it, review the findings, and see how much of the build you can carry forward.

Try StoryDraft on the Free plan, then open the result in Storyline and make it yours.