The course is built and published. Now it has to reach a client, a subject-matter expert, or a stakeholder who has no LMS, no seat in your authoring tool, and no patience for a 200MB zip and instructions about which file to double-click. Publish for Web, zip the output folder, and drop it in — you get one private link that opens the running course in any browser. No hosting to configure, no LMS to borrow, no account for the reviewer. Add a password when the content is under NDA, and set an expiry so the review copy doesn't outlive the project.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML file or ZIP bundle, or click to choose.
Single file or ZIP. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.
Publish for Web in your authoring tool — Storyline 360, Rise 360, Captivate, iSpring, Lectora — and you get a folder rather than a single file: story.html or index.html plus the assets, scripts, and media it depends on. Zip that whole folder and drop the ZIP in. miinideck unpacks it, finds the entry page, and serves the course behind one private link, so the relative paths your course needs resolve instead of breaking the way they do when someone opens the file from their Downloads.
Send the link. It's unguessable and no-indexed, so an unreleased course or a client's proprietary content never turns up in search, and only the reviewers you send it to can open it. They click through the real course in their browser — interactions, branching, audio, quiz logic all running — with nothing to install and no account to make.
Re-publish as you revise and replace the file; the link stays the same, so the SME always lands on the current cut instead of hunting for 'v4_final_FINAL'. Password it for content under NDA, set an expiry so the review copy dies with the project, and put it on your own domain on Studio so the whole hand-off reads as your studio rather than a file host.
Yes — that's the exact case this fits. Publish for Web instead of publishing for LMS, and you get a folder of static files (story.html or index.html plus its assets) that runs in any browser on its own. Zip that folder, drop it in, and send the private link. The reviewer opens the course, clicks through it, and never touches an LMS, a seat in your authoring tool, or a download. What you give up by not going through an LMS is tracking — see the SCORM question below.
No, and it's worth being straight about that, because it's the real dividing line. SCORM, xAPI, and completion reporting are the LMS's job — the course talks to the LMS at runtime and the LMS records who finished what and what they scored. A private link hosts the course; it doesn't run the reporting layer. If you need graded completion records for compliance or certification, you need an LMS (or your authoring vendor's own hosted delivery, which is built for that). Use a private link for the part that isn't graded: client review, SME sign-off, stakeholder walkthroughs, portfolio samples. On miinideck you can still see that the link was opened and when, which is usually what a review actually needs — but that's an access log, not a completion record.
Depends on the media inside it, and this is the constraint worth checking before you publish. The single-upload ceiling is 10MB on the free tier, 25MB on Solo, and 50MB on Studio. A course that's mostly slides, interactions, and compressed audio usually lands well under that. A course carrying full-length embedded video usually doesn't. The standard fix is the one video-heavy courses use anyway: host the video on a video platform and let the course embed it, so the bundle stays light and the video streams properly instead of forcing every learner to download it. If your course genuinely must ship dozens of megabytes of embedded media, an LMS or your vendor's hosting is the better home for it.
Yes, and it's free on every plan. Every link is already unguessable and no-indexed, so proprietary training content stays off search by default. Add a password on top when the content is under NDA — the file is held back until the passphrase checks out server-side, so someone who ends up with the URL still can't open the course. Pair it with an expiry so the review copy stops working when the engagement does.
Yes. Turn on Review and anyone with the link can pin a comment to the exact element they're looking at — a wrong term on slide 12, an interaction that doesn't read as clickable — without making an account. That beats the usual alternative of a spreadsheet full of 'slide 12, the box on the right'. Collecting and resolving that feedback is free on every plan; exporting the whole thread as a prompt for an AI tool is a Studio feature.
On the free tier links self-destruct after 7 days, which suits a quick SME pass. On Solo ($4.99/mo) links never expire, so a course you hand to a client can stay at the same URL indefinitely, and you can still set a deliberate expiry per link when a review window should close. Studio ($14.99/mo) adds your own domain and white-labelling, so the link and the page after expiry both carry your studio's name.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.