The tenant audit comes first
Ecosystem queries deserve ecosystem answers, and the ecosystem fact here is that Microsoft has spent three years consolidating its video story into Clipchamp. The old Microsoft Stream, once the tenant's video portal, has been folded into the Clipchamp brand; recordings live in OneDrive and SharePoint like every other Office file, inherit the tenant's permissions, retention, and e-discovery, and play inside the apps people already open. For an IT-led buyer, that governance story is the argument: a Loom workspace is another data store to govern, while a Clipchamp recording is a file in the store already governed.
The capability story is narrower, and this guide will not inflate it. Clipchamp records screen, camera, or both, edits on a timeline, and exports or shares by link. Its screen recording is capped at 30 minutes per recording. What it does not provide is Loom's social layer: a viewer page built for reactions and threaded comments, transcripts as the primary navigation, and the async-update culture that makes Loom feel like a communication tool rather than a file format. Tenants whose need is documentation and training libraries are well served by what they own. Tenants whose need is replacing meetings with watched, answered video messages are buying a different product, and should admit it early.
| Option | Already in tenant | Recording cap | Sharing and governance | Async layer |
|---|---|---|---|---|
| Clipchamp | Yes, with Microsoft 365 plans | 30 minutes per recording | OneDrive and SharePoint, tenant permissions | Basic: links and comments on files |
| Snipping Tool | Yes, built into Windows | Short clips | Local file | None |
| Cap | No | Plan-based | Vendor cloud or self-hosted | Full: transcripts, comments, analytics |
| Loom | No | Plan-based (5 minutes free) | Separate Atlassian-governed workspace | Full: the category benchmark |
Grading what you own
Clipchamp's recording flow is genuinely convenient for the tenant user: open the app or the browser, record screen and camera, trim, and share a OneDrive link into Teams or Outlook without a new account anywhere in the chain. Premium features ride on qualifying Microsoft 365 plans rather than a separate Clipchamp subscription, which is why this site's dataset carries its premium price as an honest null: there is no standalone price to compare, and pretending otherwise would corrupt the comparison tool below. The 30-minute recording cap is the hard limit to plan around; long training sessions must be chunked or recorded elsewhere. The Snipping Tool's screen recording, built into Windows, covers the shortest jobs (show the error, send the clip) at zero cost and zero governance risk, and IT departments underrate it because it is unglamorous.
Where the tenant bench stops: discovery and conversation. A library of Clipchamp files in SharePoint is findable by search but not browsable like a video workspace; comments live on files, not on a viewing page your audience is trained to open; and there is no transcript-first experience for the viewer who wants to skim. If your async practice depends on those behaviors, the tenant tools are a recording utility, not a Loom replacement, and the honest comparison is between the paid platforms.
The paid destinations, for tenants
Cap is the tenant-friendly paid answer: Pro at $8.16 per user per month billed annually, transcripts and comments included, and a self-hosting option for organizations whose data policies make a new video cloud a hard sell in the first place. Loom itself remains the benchmark for the viewer experience, at $15 to $18 per user per month for Business, with the 2026 seat-definition change (the retired Creator Lite role) priced in the flagship guide. Either purchase should be justified against the free baseline this page starts from: if Clipchamp covers 80 percent of your recordings, the paid tool only needs to win the remaining 20 percent, and a small seat count for the people who record externally may be the right buy.
