How to Save a Skool Course on an External Drive

Use the external drive as an archive, not a gamble

An external SSD or hard drive can keep a large offline course from filling the computer, but a removable destination introduces new failure modes: an incompatible filesystem, a loose cable, insufficient space, accidental disconnection, and the mistaken belief that one external copy is a backup.

The reliable pattern is:

download -> verify locally -> organize -> copy to external drive -> verify again

Use this workflow only for course videos you own or have permission to retain.

Estimate capacity before choosing the drive

Count total course runtime and measure one representative file. The rough bitrate formula is:

gigabytes ≈ megabits per second × hours × 0.45

Then add:

• 20–30 percent operational headroom;
• space for course notes, worksheets, and manifests;
• temporary or replacement versions;
• future modules you are authorized to add.

A 100 GB course does not belong on a nearly full 128 GB drive. Read the complete storage-estimation guide before buying or repurposing storage.

SSD or hard drive?

Drive speed rarely improves the source download itself, but it affects file moves, verification, and playback of large high-bitrate recordings.

Choose a filesystem intentionally

The filesystem determines which computers can write to the drive and how large files are handled.

Formatting erases a drive, so do not reformat storage that contains the only copy of anything important. Use the operating system's official disk tool and confirm the exact target before changing a filesystem.

Build the course structure on the drive

Create one top-level folder and keep its manifest inside:

Skool Courses/
  course-name/
    00-course-record/
      manifest.csv
      readme.txt
    01-start-here/
    02-foundations/
    03-implementation/
    90-replays/
    98-needs-review/

Use relative paths in the manifest. A path such as 03-implementation/04-build-the-dashboard.mp4 still works if the drive letter or mounted volume name changes.

The course file-naming guide contains the complete manifest fields.

Download locally before copying

Direct-to-external downloads can work, but they make a cable interruption, drive sleep, or mount problem look like a media failure. A safer course workflow is:

1. Download into a local needs-review folder.
2. Wait for all browser processing to finish.
3. Open the MP4 and inspect the beginning, middle, and end.
4. Rename it with its module and lesson position.
5. Copy it to the external course folder.
6. Mark it copied in the manifest.
7. Open it from the external drive.
8. Mark it verified on archive.

If the internal disk is too small for even one working file, use a high-quality directly connected drive, keep the cable still, and reduce the queue to one job. Verification remains mandatory.

Mac and Windows handling

Apple's current guidance shows connected storage under Locations in Finder. Microsoft's current guidance uses File Explorer for connected USB, SD, and external hard drives.

On either system:

• copy one test file before the course;
• confirm you can create, rename, and delete a disposable test file;
• open a video directly from the drive;
• use normal eject or safe-removal controls before unplugging;
• never disconnect during an active copy or download;
• label the physical drive so it can be matched to the manifest.

See the dedicated Mac workflow and Windows workflow for operating-system setup.

One external drive is not a backup

A backup requires another independent copy. External drives can fail, be lost, or be overwritten.

For a creator-owned course migration, keep:

1. the working archive;
2. a second copy on a separate approved device or storage system; and
3. the source platform until the migration has been checked.

Open samples from the second copy. A successful copy dialog is useful evidence, but it is not the same as a restore test.

External-drive checklist

• Permission covers the local course archive.
• Capacity includes operational headroom.
• The drive type fits how often the course will be used.
• The filesystem matches the computers that need write access.
• Existing drive data is protected before any formatting.
• The module structure and manifest exist on the drive.
• Files are verified before and after copying.
• The drive is ejected before disconnection.
• A second independent copy exists.

When the storage is ready, use the Skool Course Downloader workflow in small, verifiable batches.

Expand

Close

Last substantively reviewed August 2, 2026. See our editorial and corrections policy.