Updated 31 July 2026
Skool video download not working?
Most failed Skool downloads are one of five causes, and only some of them are bugs. Find your symptom below — including the cases where a refusal is the tool behaving correctly.
1. The lesson is locked for your account
Gated, dripped, and higher-tier lessons do not issue a playable stream to an account that cannot open them, so every downloader fails on them — the honest ones say so, the rest fail silently. Check whether you can watch the lesson normally on Skool. If you cannot watch it, no tool can save it, and this one records it as skipped with the reason in the manifest.
2. The lesson is a YouTube embed
YouTube lessons are deliberately not downloaded — Chrome Web Store policy forbids it, and a listing that ignores that gets taken down. They are kept in their course position as links in the manifest instead, so the course structure survives even where the video must stay on YouTube. If your course is mostly YouTube embeds, the pre-run counts will tell you before you spend anything.
3. The stream link expired
Skool’s video streams and attachment links are signed URLs with short lifetimes: hours for attachments, roughly a day for video. Any workflow built on copying a stream URL out of devtools dies this way — the link you saved is dead by the time you use it. The fix is structural: store which lesson to fetch and resolve a fresh link at download time, which is how this extension works.
4. The video is DRM protected
DRM-protected video is not downloadable with this tool, full stop. No supported-platform exception, no workaround. A tool claiming to defeat DRM is describing a legal problem, not a feature.
5. The export was interrupted
Laptops sleep and browsers get closed, and a multi-gigabyte course export will meet both. What matters is what survives: progress here is checkpointed only after bytes are committed to disk, together with the position in each stream, so a retry resumes from state known to be good. A progress counter alone cannot do that — resuming from “lesson 38” when lesson 38 is half-written produces corrupt files that look like successes.
Still stuck?
Every export writes a manifest listing each lesson and its outcome — saved, skipped with reason, or failed with reason. If a failure is not explained by the causes above, that manifest line is what support needs to diagnose it.
Common questions
Why do some lessons say “locked” or “skipped”?
Your Skool account cannot open those lessons — they are gated behind a level, a payment, or a drip schedule. No downloader can fetch a stream the platform refuses to issue for your account, and one that claims otherwise is advertising unauthorised access.
This extension counts locked lessons before the run starts and records each one in the manifest with the reason, so a skip is visible instead of silent.
Why did my YouTube lesson not download?
By design. YouTube downloads are against Chrome Web Store policy, so YouTube lessons are recorded in their course position as links in the manifest instead. A tool that quietly includes YouTube downloading risks its listing — and your workflow with it — being removed.
A download link that worked yesterday fails today. Why?
Stream and file links on Skool are signed and expire — within hours for attachments and about a day for video. Saved or shared URLs going dead afterwards is normal. The extension stores which lesson to fetch, not the temporary link, and resolves a fresh one at download time.
My export stopped halfway. Do I start over?
No. Completed files and stream positions are checkpointed only after bytes are durably on disk, so a retry continues from known-good state instead of restarting the course. Automatic recovery after a hard browser crash is verified as a release test before it is claimed.
The output file is 0 bytes or will not play.
That points at the joining step, not the fetch. If it happens with this extension, send the manifest line for that lesson to support — the manifest records exactly what was fetched and what was written, which usually identifies the failure in one look.
Related: the full step-by-step walkthrough· what a downloader should and should not touch · exporting one whole course in a run