Before you start, link to this section
- Choose this format when separate assets are more convenient than one large HTML file.
- You need a suitable way to serve the extracted package to learners; exporting alone does not host it.
Step by step, link to this section
- Run Export → Publish readiness and fix missing assets or blocking issues.
- Choose Export → Web package (ZIP) and save the package.
- Extract the ZIP and keep its folders and filenames together.
- Upload the extracted package to your chosen web host, preserving its structure.
- Serve the package’s index.html over the host’s normal web URL.
- Test playback, attachment downloads, interactions, completion, and resuming from a learner browser.
What to expect, link to this section
The package contains an index page, player, course data, and referenced assets. Outside an LMS, player progress uses browser storage rather than reporting to an LMS.
Tips & troubleshooting, link to this section
- Do not move index.html away from its accompanying files.
- If opening files directly causes browser restrictions, test through a web server.
- Browser storage is tied to the browser and origin. It is not a central learner-results database.
- Changing the hosting URL or clearing browser storage can affect locally stored progress.
Still need a hand? Contact Agavien. Include your app version and the step where you got stuck.