Short answer
Wix can’t run a SCORM zip. Host the package, then launch it from a Wix button or HTML embed, minding the mobile-editor gotchas.
The portfolio lives on Wix because Wix is what you already knew how to use. The course is a SCORM package you just published out of Storyline. So you open the Media Manager, drag the .zip in, and wait for the magic. There is no magic. Best case, Wix files it away as an attachment nobody can open. Worst case, you spend an afternoon convinced the export is broken when the export is fine.
Here is the part the “add SCORM to Wix” tutorials bury: Wix can’t run a SCORM course any more than it can run a video codec. What it can do — beautifully — is show a button or a frame that points at a course running somewhere else. That’s the whole job.
Wix builds the page around your course. It was never going to run the course itself.
/01How Wix and the player split the work.
A SCORM package is a .zip that expects to talk to a JavaScript runtime — the thing that answers LMSInitialize() and stores completion, score, and resume state. Wix doesn’t ship that runtime. So the division of labor is clean and it never changes: the host extracts the package and serves the player; Wix owns the header, the footer, the responsive layout, and the link that launches it.
Publish from Storyline, Rise, or Captivate. Upload the package to a host that serves the player — on Training OS the module plays on your public portfolio at /portfolio/<handle>, and Pro adds an embed URL at /embed/<courseId> and private share links — and then, before you touch the Wix Editor, paste that URL into a fresh browser tab. If audio, completion, and resume work there, they’ll work behind a Wix button. If they don’t, fix it at the host; no amount of editor wrangling rescues a broken launch.
This split is also why updates stay painless. Re-publish in your authoring tool, re-upload to the host if the URL pattern is stable, and your Wix button keeps pointing at the same place. You almost never re-touch the page.
/02Two ways to put it on the page.
Once that URL is solid, Wix gives you exactly two good patterns. Ranked by how rarely they break across the Editor-versus-live gap:
Option 01
A Wix button that opens the module in a new window.
Best for: portfolios, client demos, anything that has to survive mobile
In the Wix Editor, drop a Button (or a styled text link), set the web address to your launch URL, and switch on Open in new window. Stack real context above it — the learning objective, an estimated time, a “best in Chrome” note. That copy is what keeps a cold visitor from bouncing the instant the new tab opens.
- Works well
- Sidesteps iframe restrictions and small-viewport clipping entirely
- Full-window playback — how Storyline and Rise expect to run
- Behaves the same in the Editor preview and on the live site
- Watch out for
- Leaves your Wix page for the module
- Not an inline-on-the-page feel
Option 02
An inline iframe via the Embed HTML element.
Best for: desktop landing pages where the demo should live on the strip
Add an Embed → Embed HTML element (sometimes labelled Custom Embed) and paste an iframe pointing at your launch URL. Give it room: full width, a real fixed height — at least 600px, 700–800px for taller players — and allow="fullscreen" if your authoring tool uses the fullscreen API. Then resize the section itself so the strip isn’t shorter than the frame. On Training OS, the iframe embed URL (/embed/<courseId>) is a Pro feature.
- Works well
- Module feels like part of the page
- Good for long-form desktop pages with an inline demo
- Watch out for
- The embed component can strip iframe attributes on publish
- Wix mobile stacking crushes fixed-height frames
- Editor preview and live site can disagree
Inline embed · paste into a Wix Embed HTML element
<iframe
src="https://www.trainingos.com/embed/your-course-id?creator=your-handle"
width="100%" height="760"
allow="fullscreen"
title="Onboarding module — interactive course"
></iframe>/03The Wix mobile editor will lie to you.
Wix keeps a separate mobile layout, and it is where embeds quietly go to die. Three failure modes, in the order I actually hit them:
1. The mobile section collapsed your frame.
Wix stacks sections tightly on phones, and a fixed-height iframe inside a short strip gets clipped to a sliver — or to nothing. Bump the section height and padding in the mobile editor, or, far simpler, fall back to the new-window button for phone visitors.
2. The Embed HTML element ate your attributes.
Wix’s embed sandbox sometimes rewrites or drops iframe attributes on publish, so the frame that worked in the Editor renders empty live. Strip your markup down to the minimum iframe above, republish, and re-check — don’t debug against the preview.
3. You changed the domain or SSL and forgot to re-test.
Swapping a connected domain or SSL setting in Wix can quietly turn a working HTTPS embed into a mixed-content block. It’s rare, but it’s a thirty-second pass: after any domain change, reload the launch URL on the live site and confirm it still fires.
/04Before you hit publish.
Run this once, from a logged-out window on the live site — phone and desktop both:
- The button or iframe launches the module, not a download prompt or an empty strip.
- Audio plays, completion fires, and resume works if your package relies on them.
- On a phone, the frame isn’t clipped — bump the section height or fall back to the button.
- After any domain or SSL change in Wix, reload the launch URL and confirm no mixed-content block.
Wix is one of several builders that hand the runtime off to the host — the same split applies if you ever move the portfolio. If you’re weighing where to host the package in the first place, start with how to host a SCORM file so it plays in the browser, and if the client site happens to run WordPress instead, the moves are nearly identical in embedding SCORM in WordPress.
/05Frequently asked questions.
Can I upload a SCORM .zip straight to Wix?
Why does my Wix HTML embed show an empty box after publish?
Should I link out or embed inline on Wix?
Can I put a module behind Wix Members?
See what Allure Training OS includes
About the author
Jonathan Borgwing
Jonathan Borgwing founded Allure Training OS. He writes about hosting SCORM, xAPI and sharing work clients can open.