---
title: "SCORM hosting"
description: "Can I host a SCORM package in Coassemble?"
canonical_url: "https://support.coassemble.com/articles/scorm-hosting-PO4S1a7097"
md_url: "https://support.coassemble.com/articles/scorm-hosting-PO4S1a7097.md"
---
# Can I host a SCORM package in Coassemble?

> How to upload an existing SCORM package and host it in Coassemble, how it appears in your library, and what reporting you get on it.

Yes. You can upload an existing SCORM package and host it in Coassemble, where it sits in your library alongside the courses you've authored. Learners open it the same way they open anything else, and you get attempt-level reporting on how they go, including time spent, success, score and a question-by-question breakdown.

Hosting runs the package as it was authored. Your original design, interactions and wording are preserved exactly, which makes it the right choice for content you've already had signed off and don't want reshaped.

## How do I upload a package?

1. Click **New course** at the top of your library.
2. Select **Upload SCORM package**.
3. Choose your package file.
4. Wait while the package extracts. Coassemble shows a processing state while this happens.
5. Once extraction finishes, the package appears in your library as a course card with a **SCORM** label, ready to open and share.

## How does a hosted package appear in my library?

A hosted package appears as a course card, the same as anything else in your library, with a **SCORM** label so you can tell at a glance that it's a hosted package rather than an authored course. The cover image is editable, so a hosted package can look consistent with the rest of your library instead of standing out as an import.

When you first upload a package it needs to be extracted before it can run. Coassemble shows an explicit processing state while that happens, so you can see it's working rather than wondering whether the upload failed. Once extraction finishes, the package is ready to open.

## What reporting do I get on a hosted package?

Hosted packages are tracked by attempt, so you can see how someone worked through the content rather than just whether they finished:

* **Attempts:** how many times a learner has started the package.
* **Time spent:** how long they spent in it.
* **Success and score:** the result the package reported back.
* **Attempt comparison:** multiple attempts by the same learner shown side by side, so you can see whether a second or third run actually improved.
* **Question-level export:** individual question results downloaded as a CSV you can pivot, for picking out the questions a whole cohort is getting wrong.

## Can I give a learner another attempt?

Yes. If a learner is genuinely blocked, for example their session dropped out partway through or a technical issue cost them an attempt, you can grant them an extra attempt rather than resetting their record or asking them to start over from nothing.

## Should I host a package or convert it into a Coassemble course?

Both are available, and they suit different situations. They're also different paths into the product, so it's worth knowing which you want before you upload.

**Host it** when the package should stay exactly as it is. Upload it through **New course**, then **Upload SCORM package**. The original design, interactions and approved wording are preserved, nothing is rebuilt, and you get attempt-level reporting in Coassemble. You can't edit the content in Coassemble, so updates mean re-authoring in the original tool and uploading again.

**Convert it** when the content needs to change. Upload it through **Create with agent** instead, and the package is rebuilt as an editable Coassemble course made of blocks, so you can update it in minutes, translate it, and reuse screens. The tradeoff is that it takes your Coassemble theme rather than looking like a copy of the original, and some interactions are rebuilt as the closest equivalent block.

A useful rule of thumb: host compliance content that's already approved and rarely changes, and convert anything you expect to keep editing.

## Frequently asked questions

### Can I edit a hosted package in Coassemble?

No. A hosted package runs as it was authored, so the content stays exactly as it came out of your authoring tool. If you need to edit it in Coassemble, upload the package through **Create with agent** instead, which converts it into a course made of editable blocks.

### Can I see how learners answered individual questions?

Yes. Question results can be downloaded as a CSV, one row per question result, so you can pivot it to find the questions a cohort is struggling with.

### Why can't I open my package straight after uploading?

The package needs to be extracted first. Coassemble shows a processing state while that's happening, and the package becomes available once extraction finishes.

### Does hosting a package affect the copy running in my current system?

No. Hosting the package in Coassemble doesn't change anything about the file you uploaded, so it keeps working wherever it's running today.