On this page
TL;DR
Skool videos show up in three places: Classroom lessons (the main one — full course videos), community feed posts (short clips, updates, replies), and occasionally profile/Calendar event recordings. Hosting is native — you upload an MP4 and Skool transcodes and serves it. No YouTube embed required, no Vimeo bill. The player works on desktop and mobile, supports speed adjustment, and tracks completion at the lesson level. Where Skool falls short: per-second analytics, chapter markers, in-video CTAs, DRM, and downloadable transcripts. For most communities those are nice-to-haves. The bigger problem is engagement — most creators lose more money to members not watching than to suboptimal hosting. That's where DM automation and churn signals come in, not better video infrastructure.
Start your own Skool community in 60 seconds.
14-day free trial — no card required. Most community owners decide whether Skool fits within the first week.
Where Skool videos actually live
(1) Classroom: this is where structured course content lives. You build modules, add lessons, and each lesson can hold a video, text, attachments, or an embed. Members work through Classroom modules to learn — this is the closest thing Skool has to an LMS. Classroom completion is tracked at the lesson level, so you can see aggregate progress across your community. (2) Feed posts: members and admins can attach short videos directly to feed posts. This is where you'd post a quick update, a reaction video, or a clip pulled from a longer recording. Feed videos are inline — they autoplay (muted) when the post enters the viewport on most clients. (3) Calendar/event recordings: when you run a live call inside Skool's calendar feature (or upload a recording afterward), the recording typically lives as a feed post or a Classroom lesson. Skool itself doesn't host live calls — you'll use Zoom or similar — but the recordings end up in Skool. (4) DMs: video doesn't really live in DMs natively the way it does on iMessage or WhatsApp. You can paste a link, but inline DM video isn't a Skool feature.
Uploading Skool videos and formats that work
MP4 with H.264 video and AAC audio is the safest format and what you should default to. Other formats (MOV, AVI, MKV) sometimes upload, but you'll save time by exporting MP4 from your editor or running a quick HandBrake/FFmpeg pass. There's no published file size cap, but very large files (multi-gigabyte) frequently timeout — keep individual lessons under 2GB, ideally under 1GB. For talking-head content, 1080p at a reasonable bitrate (5–8 Mbps) usually lands well under that. For screen-share content, a slightly higher bitrate helps with text clarity. Skool transcodes server-side to its own bitrate ladder, so uploading 4K won't give your members 4K — most playback happens at 720p/1080p, which is fine for the kind of content most communities produce. To upload: open the Classroom editor for the relevant lesson (or the feed composer for a post), drag the MP4 in, wait for the upload + transcode to finish, save.
What Skool videos don't have
No per-second analytics. Skool tracks lesson-level completion (% of members who finished) but doesn't show retention curves or average view duration. If you need to see where members drop off in a 30-minute lesson, you'd need to host on YouTube unlisted or Wistia. No chapter markers. You can fake them in the lesson description, but the player has no built-in chapter UI. No in-video CTAs. No clickable elements at specific timestamps to send members to another lesson or product. No DRM. A determined screen-recorder can rip your videos. No downloadable transcripts. If you want SEO transcripts or accessibility-grade captions, you generate them separately (Descript, Otter, YouTube auto-caption + cleanup) and embed manually. No live in-platform calls. Skool doesn't host live video — you use Zoom or similar and post recordings after. For 90% of communities, none of these are dealbreakers — they're absences you should know about.
The real bottleneck: getting people to watch
You can host the best videos in the world on Skool's Classroom and 70% of your members still won't finish module 2. Hosting isn't the constraint — engagement is. The fix is operational: nudge members into the videos with timed DMs, catch the ones whose engagement is sliding before they churn, and follow up on incomplete lessons. Skool's native UI doesn't do any of this. There's no DM scheduling, no completion-based triggers, no churn signal at the engagement level. Tools4skool plugs into your existing skool.com session via a Chrome extension (no password stored) and adds the missing layer: Auto DM Sequences with multi-condition triggers (e.g., 'DM members who joined 7 days ago and haven't started Lesson 1'), churn risk scores so you spot disengaged members two weeks before they cancel, an unreplied filter so video questions in the inbox don't slip, slash commands for canned video-recommendation replies, and a Churn Saver that fires within 60 seconds of a cancellation with a save-the-relationship message. Kate Capelli — a US-based Skool creator — has cited a 7,000% ROI: $59/month in tooling led to $4,000/month in additional revenue inside two weeks. Free plan is forever (1 sequence, 20 DMs/day). Paid plans go $29/$59/$149 per month.
Stop leaving DMs, churn, and revenue on the table.
tools4skool plugs the holes Skool ships with. Free plan forever, paid tiers from $29/mo.
Book a demo →Frequently asked
Keep reading
Ready when you are.
Drop your email — we'll loop you in the day access opens.
Book a demo →