The .story file stayed with the contractor, or the Rise account left with the person who built it. The published zip still holds most of what a rebuild starts from. Drop it in for a Word storyboard of every screen, narration from the captions, the questions in a file Storyline imports, the media named by slide, and a PowerPoint deck with each slide back in its own layout. Read in your browser, never uploaded.
Free · No account · Your files never upload
The zip you published from Storyline 360 or Rise 360: SCORM, xAPI, cmi5 or Web. It is read in this tab and never uploaded.
A published course is not a project file, but it is not a sealed box either. Storyline writes every slide’s text, the asset library and every question with its correct answer into the package, because the player needs them to run. Rise writes the whole course into one data file for the same reason. This reads those back out, in course order, and hands you a rebuild kit: a Word storyboard, a question file for Storyline’s own import, the media renamed after the slide that uses it, and a read-me.
For a Storyline course there is one more thing in the kit. The package records where every object sat, how big it was, and what color it was painted, so the kit includes a PowerPoint deck with each slide put back together: text boxes with their fonts, pictures, and plain shapes, in their places, with the narration and the notes in the speaker notes. Storyline imports PowerPoint, which makes the deck a starting point rather than a picture of one. Every layer becomes its own slide, straight after the slide it belongs to.
Narration comes back as words when the course had closed captions, which is one more reason to caption everything. Slide notes come back when the Notes tab was switched on in the player. The storyboard says plainly which of those your course had.
The courses people need this for are exactly the ones they cannot send anywhere: internal training, client work, material under contract. Your zip is opened in this tab by code that came with the page. There is no server to upload it to, and the kit is assembled on your machine.
A published package is the fallback, not the first move. The .story file turns up more often than people expect, and there is one place almost nobody checks: a course published to Review 360 with Upload project file ticked can hand the project file straight back. Six places to look for a lost Storyline source file walks through the rest before you spend a week rebuilding.
The vendor delivered a SCORM package and kept the source. The person who built the course left, and so did their laptop. A compliance course needs one policy change and nobody can find the .story file. Or you are moving a Storyline course to Rise and want the words and pictures in hand before you start. In every case the job is a rebuild, and a rebuild goes faster from a storyboard and named media than from clicking through the course with a screenshot tool.
It does not rebuild the project. Triggers, states, variables and animation stay behind. Each slide in the deck is drawn as it stands when its timeline finishes, so a slide that builds itself up arrives finished. In the deck, a shape whose outline PowerPoint has no name for is drawn as the nearest rectangle or circle, in the right place and color, and a gradient comes across as its first color. Nothing can be hidden on a PowerPoint slide, so anything the course reveals on a click is simply there. It does not transcribe speech, so narration with no captions comes back as sound files only. A Rise quiz that draws from a question bank does not carry the bank. It reads Storyline 360 and Rise 360 output; Captivate, iSpring and the others store their content differently and are not supported.
One more thing. A published course is still somebody’s work. Use this on your own organization’s courses, or on content you have the rights to reuse.