Where to Host Course Videos: The Honest Comparison

Where your course videos live decides three things at once: what they cost to deliver, whether you can protect them, and whether losing access actually means losing access.

Most instructors decide it by accident, on day one, and live with the consequences for years.

YouTube: free, and the wrong tool

The appeal is obvious. It is free, it plays everywhere, and everyone knows how to upload to it. So instructors set videos to "unlisted", embed them, and consider the problem solved.

Here is what unlisted actually means: anyone with the link can watch, forever, without an account. That is not access control. It is the absence of a directory listing. One student pasting the address into a group chat has published your paid course, and you will not know.

Beyond that:

• No per-student watermarking. Every copy is anonymous. If your course leaks, you cannot tell who leaked it.
• No revocation. A student who refunds keeps whatever links they saved.
• Suggested videos and someone else's branding. Your paid lesson ends with recommendations for your competitors' free content.
• Rules you do not control. Videos can be flagged, restricted or removed by systems you cannot appeal to quickly, and your course goes down with them.

YouTube is an outstanding marketing channel. Publish free content there and let it bring people to your platform. It is not somewhere to keep the thing people paid for.

A dedicated video host: a real step up, with a ceiling

Dedicated video-hosting services are built for people who want a clean, controlled player, and it shows: no suggested videos, no external branding, and restrictions so your videos only play on your own site.

That is meaningfully better than unlisted — it closes the pasted-link problem. It does not stop a student capturing the video and re-uploading it, and it does not tell you who did.

Where it runs out:

• Bandwidth is metered on the plans that matter, so the "somebody else handles it" feeling disappears at scale.
• Per-student watermarking is rarely standard, so you lose the highest-value protection control.
• It is a second system. Enrolment lives in your platform; access lives elsewhere. Two systems that must agree about who can watch what — and eventually will not.

Reasonable for a small paid catalogue. Increasingly awkward as you grow.

Raw delivery infrastructure: cheapest per gigabyte, most expensive in time

Video-delivery services are what platforms themselves are usually built on. Used directly, they give you low per-gigabyte pricing and excellent global delivery.

The catch is that they give you delivery, not a product. Everything that makes delivery safe — tying playback to a specific enrolled student, expiring access, watermarking, handling the case where a session ends mid-lesson — is yours to build and yours to maintain.

That is real, ongoing engineering, and it is exactly the work a platform exists to absorb. Choose this route if you have a developer and a specific requirement you can state in one sentence. Otherwise you are rebuilding a course platform to avoid paying for one.

Built into the platform: one system, one answer

When hosting is part of your course platform, everything that matters shares a single source of truth about who is allowed to watch.

That sounds abstract until something goes wrong. A student refunds — does their access actually stop? With separate hosting, only if two systems talk to each other correctly. With integrated hosting, revoking access is the same act as unenrolling them.

It also makes the strongest protections practical at all. Per-student watermarking requires the player to know which student is watching, which requires playback and enrolment to be one system. The same is true of device limits and activity monitoring: they all need one identity to reference.

Side by side

What to actually do

If you are launching: use whatever your platform provides. It is included, it is integrated, and it removes a decision you do not yet have enough information to make well.

If you are on YouTube unlisted today: move. This is the highest-value change available to you, and it is more urgent than anything on your content roadmap.

If you are on a dedicated host and it works: you are fine for now. Revisit when bandwidth costs start showing up on the invoice, or the first time you need to know which student leaked something.

If you are considering building on raw infrastructure: only with a developer, and only for a reason you can state plainly. "It is cheaper per gigabyte" stops being that reason once you price your own time.

How much any of this costs per month is worked through in the bandwidth guide, and the protection side in the protection guide.