Fix Microsoft Clipchamp Not Working in Microsoft 365
Why Microsoft Clipchamp Is Not Working, And Why It's Confusing
Here's the situation I hear constantly from IT admins and everyday Microsoft 365 users alike: you open Clipchamp, and your videos are just... gone. Or you try to play back a Teams meeting recording and hit a spinning wheel that never resolves. Or a colleague says they can't access the video you shared, even though you know you shared it correctly. It feels broken. But most of the time, it isn't, it's a misunderstanding of how Clipchamp actually works inside Microsoft 365.
Clipchamp is not a standalone video portal bolted onto Microsoft 365. That's the single biggest thing people get wrong. It's deeply woven into the same file storage layer that holds your Word documents, spreadsheets, and PDFs. Every video you create or upload through Clipchamp lives in OneDrive or SharePoint, not in some separate video silo. This design choice is intentional and has real implications for how you manage, share, and find your video content.
So when Clipchamp appears to be "not working," the actual failure is almost always one of four things:
- A OneDrive or SharePoint permission issue, the video file exists, but the user doesn't have access to the location where it's stored.
- A browser session or cache problem, Clipchamp's homepage didn't load your video index correctly because of a stale auth token or cached data.
- A Teams meeting recording routing issue, Teams recordings now route through OneDrive or SharePoint, not Stream Classic. If your tenant configuration is wrong, recordings either fail silently or appear in unexpected locations.
- A licensing or policy restriction, your Microsoft 365 plan or an admin Group Policy is blocking Clipchamp features outright.
I know this is frustrating, especially when your video content is time-sensitive, like a recorded all-hands meeting or a training session you were supposed to share by end of day. The good news is that because Clipchamp runs on the same platform as the rest of Microsoft 365, the fixes are well-documented and usually don't require a support ticket. Let's work through them systematically.
One more thing worth calling out: if you're an admin who migrated from Stream Classic and expected a familiar portal experience, you'll find that Clipchamp intentionally doesn't have one central video hub. That's by design, and it's explained in detail in the FAQ at the bottom of this guide. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before going through every individual troubleshooting step below, try this first. It resolves the majority of Clipchamp homepage not loading and video-missing complaints in under two minutes.
Step 1: Open a fresh InPrivate or Incognito browser window. Go to microsoft365.com, sign in with your Microsoft 365 account, and navigate to Clipchamp from the app launcher (the waffle icon in the top-left corner). Look for the Clipchamp tile. If you don't see it, click "All apps" and search for Clipchamp.
Step 2: On the Clipchamp homepage, look for your videos in the "All videos" section. If they appear here in the InPrivate window but not in your regular browser window, you have a cache or cookie problem in your main browser, clear your browser cache and cookies for microsoft365.com, clipchamp.com, and sharepoint.com, then try again.
Step 3: If videos are still missing even in InPrivate mode, navigate directly to your OneDrive by going to onedrive.com and looking in your Videos folder or searching by filename. Clipchamp stores every video as a regular file. If the file is in OneDrive, it will show up in Clipchamp once the homepage refreshes. If the file isn't there at all, scroll down to Step 3 in the full guide below.
Step 4: If you're dealing with a Clipchamp video playback error specifically, the video thumbnail loads but the video won't play, try switching browsers entirely. Clipchamp's video player is built on the SharePoint platform and is tested against Edge, Chrome, and Firefox. Internet Explorer and some older Edge (EdgeHTML) versions will fail silently.
Since every Clipchamp video is just a file in OneDrive or SharePoint, the first thing to confirm is that you can actually reach that storage. If your OneDrive is full, over quota, or temporarily locked by your IT admin, Clipchamp will silently fail to display or upload videos.
Navigate to onedrive.com and sign in with the same account you use for Microsoft 365. In the left sidebar, look at the storage meter at the bottom. If it's showing red or near-full, you need to free up space before Clipchamp will behave correctly. Video files are large, even a 10-minute Teams meeting recording can be 200–500 MB depending on resolution.
Next, check that your OneDrive is not paused or in a sync error state. If you're using the OneDrive desktop sync client, look at the OneDrive icon in your system tray. A red X or an orange warning triangle means sync is broken. Right-click the OneDrive icon and choose View sync problems to see the specific error.
For SharePoint-hosted videos (typically those uploaded to team sites or communication sites), you'll need to confirm that you have at least Read permission on the specific SharePoint library where the video lives. Ask your SharePoint site owner to check Site Settings > Site Permissions and confirm your account appears with the right access level. If you're the site owner yourself, navigate to the video file, click the three-dot menu next to it, choose Manage access, and verify the sharing settings are what you expect.
If everything checks out here, storage isn't full, sync is healthy, permissions look right, and Clipchamp still isn't showing your videos, move to Step 2.
Clipchamp's homepage is a web application that indexes your videos from across OneDrive and SharePoint. It caches parts of that index in your browser's local storage. When the index gets stale, especially after a password change, a tenant admin makes a configuration update, or you've recently been added to new SharePoint sites, the cached view won't match reality. Your videos exist, but Clipchamp doesn't know about them yet.
Here's the exact process to force a clean reload:
1. In Edge or Chrome, press Ctrl + Shift + Delete
2. Set the time range to "All time"
3. Check: Cached images and files, Cookies and site data
4. Click "Clear data" (Edge) or "Clear data" (Chrome)
5. Close and reopen the browser
6. Navigate back to Clipchamp via microsoft365.comAfter clearing cache, sign back into Microsoft 365. When you land on the Clipchamp homepage, give it 30–60 seconds to rebuild the video index. You'll see a loading state as it pulls in your video files from OneDrive and SharePoint. This is normal.
If you're on a managed corporate device where you can't clear cookies yourself, use an InPrivate window as a workaround: press Ctrl + Shift + N (Edge/Chrome) to open InPrivate/Incognito, navigate to microsoft365.com, and sign in fresh. The InPrivate session starts with no cached data, so it will always load a fresh Clipchamp homepage.
You should see your video count on the homepage update to reflect everything in your OneDrive Videos folder and any SharePoint libraries you have access to. If videos are still missing after a clean load, the issue is with how those videos are stored, not the browser. Proceed to Step 3.
This one is responsible for a huge percentage of Clipchamp "not working" complaints. Teams meeting recordings stopped going to Stream Classic a while back, they now route directly to OneDrive or SharePoint. If you can't find a Teams meeting recording in Clipchamp, it's almost always a routing issue, not a lost file.
Here's where recordings land depending on the meeting type:
- Personal/ad-hoc meetings: The recording organizer's OneDrive, inside the folder Recordings
- Channel meetings: The SharePoint document library for that Teams channel, inside the Recordings folder
To find a specific recording, open Teams, go to the Chat or Channel where the meeting occurred, and scroll back to find the meeting event. Click on it, if the recording was saved successfully, you'll see a link directly to the video file in OneDrive or SharePoint. Click that link, and you're now looking at the actual file. You can then share this link with others, or open it in Clipchamp by clicking Edit video if you want to trim it.
If the recording link in Teams shows an error like "This content isn't available" or simply doesn't appear, check whether the meeting organizer has left the organization. When an organizer's account is deleted from your tenant, recordings in their personal OneDrive become inaccessible unless an admin has run a data retention or transfer process first. Your IT admin can recover these through the Microsoft 365 admin center under Users > Deleted users > Restore (within 30 days) or through eDiscovery if retention policies were in place.
Once you locate the file in OneDrive or SharePoint, it will automatically appear on your Clipchamp homepage the next time it loads, no manual import required.
Someone tells you they can't watch the Clipchamp video you shared. You're sure you shared it. They're sure they're clicking the right link. What's going on?
Because Clipchamp videos are stored as regular files in OneDrive or SharePoint, the sharing model is exactly the same as sharing a Word document. The link you generate inside Clipchamp is the same as a SharePoint/OneDrive file share link. And the same rules apply, if the recipient's account doesn't have access to the storage location where the file lives, the link will fail.
To fix a sharing error on a specific video:
1. Go to onedrive.com (or your SharePoint site)
2. Find the video file
3. Right-click → "Share" (or click the three-dot menu → Manage access)
4. Review who the link is shared with
5. Check the link type:
- "People in [Org name]" = only your org can view
- "People with existing access" = only current collaborators
- "Anyone with the link" = public (use carefully per org policy)
6. Change to the appropriate setting and resend the linkA common mistake is sharing the Clipchamp editor link (which ends in clipchamp.com/edit/...) instead of the SharePoint video playback link. The editor link requires the recipient to have a Clipchamp account and edit permissions. If you just want someone to watch the video, share the file directly from OneDrive/SharePoint, they'll get the standard video player experience without needing any special permissions beyond what you grant on the file itself.
For external sharing (sharing with people outside your organization), your tenant's external sharing policies in the SharePoint admin center must allow it. If external sharing is disabled, the "Anyone with the link" option simply won't appear. Your IT admin controls this at SharePoint admin center > Policies > Sharing.
Upload failures in Clipchamp are almost always one of three things: file format not supported, file size exceeding limits, or a network/proxy issue blocking the upload to SharePoint. Playback errors are most often a browser codec issue or a network restriction on video streaming from SharePoint.
For upload failures: Clipchamp supports the standard video formats you'd expect, MP4, MOV, AVI, MKV, and WebM. If you're trying to upload a format like .flv, .wmv, or an older proprietary format, convert it first using a tool like HandBrake to MP4 (H.264/AAC) before uploading. After upload, the file is stored directly in your OneDrive just like any other file, so the same size limits that apply to OneDrive file uploads apply here, typically 250 GB per file for most Microsoft 365 plans.
If the upload starts but stalls or fails with a generic error, a corporate proxy or firewall may be blocking traffic to SharePoint upload endpoints. Ask your IT admin to confirm that these endpoints are whitelisted:
*.sharepoint.com
*.svc.ms
*.microsoft.com
clipchamp.comFor playback errors: If the video thumbnail appears but the video won't play, try these in order:
- Switch to Microsoft Edge, it has native support for the widest range of video codecs on Windows and is Clipchamp's most tested browser.
- Disable browser extensions, especially ad blockers or content security policy modifiers that may be interfering with the SharePoint video player.
- Check whether the issue is specific to one video or all videos. If it's just one video, the file itself may be corrupted or in an unsupported encoding. Try re-uploading a re-encoded version.
- On a corporate network, ask your admin if HTTPS inspection (SSL/TLS interception) is enabled, this can break video streaming from SharePoint in some configurations.
After resolving upload or playback issues, the video should appear and play correctly on the Clipchamp homepage as well as anywhere it's been embedded, in SharePoint pages, Teams channels, or direct links.
Advanced Troubleshooting for Clipchamp in Enterprise Environments
If you're an IT admin or working on a domain-joined machine and the steps above haven't resolved your Clipchamp issues, you're likely hitting a policy-level or tenant-level configuration problem. These are the scenarios I see most often in enterprise environments.
Check Whether Clipchamp Is Enabled at the Tenant Level
Clipchamp requires a Microsoft 365 license that includes OneDrive for Business and SharePoint Online. But even if those are licensed, an admin can disable Clipchamp specifically. Go to the Microsoft 365 admin center (admin.microsoft.com), navigate to Settings > Org settings > Clipchamp, and verify that Clipchamp is turned on for your organization. If you don't see a Clipchamp entry there, it may be managed through the Microsoft 365 Apps admin center instead.
Audit Conditional Access Policies
Conditional Access policies in Azure Active Directory (now called Microsoft Entra ID) can block access to Clipchamp if the policy is scoped to block SharePoint access from certain device compliance states or locations. Open the Microsoft Entra admin center, navigate to Protection > Conditional Access > Policies, and review any policies that target SharePoint or "All cloud apps." A policy requiring compliant or hybrid Azure AD-joined devices will block Clipchamp on a personal or unmanaged device even if the user has the right license.
Check Event Viewer for SharePoint Sync Errors
On Windows machines using the OneDrive sync client, SharePoint sync errors often surface in the Windows Event Viewer before they become visible problems in Clipchamp. Open Event Viewer (Win + R → eventvwr.msc), navigate to Applications and Services Logs > Microsoft > Windows > OneDrive, and look for Error-level entries. Event IDs in the 1xxx range typically indicate authentication failures; IDs in the 2xxx range are sync engine errors. These logs give you the specific error code you need to look up in the Microsoft support documentation for a targeted fix.
Group Policy Conflicts
In heavily managed enterprise environments, Group Policy Objects (GPOs) can restrict browser functionality in ways that break Clipchamp. The most common culprits are:
- GPOs that disable IndexedDB or localStorage in the browser, Clipchamp uses these for its video index cache.
- GPOs that set the browser's compatibility view to treat sharepoint.com or microsoft365.com as intranet sites, triggering legacy rendering modes.
- GPOs that block WebAssembly execution, the Clipchamp video editor uses WebAssembly for its processing pipeline.
Run gpresult /h c:\gpreport.html from a Command Prompt (as admin) on the affected machine and open the generated HTML file to see all applied policies. Look for any browser-related policies under the Computer Configuration or User Configuration sections.
If you've confirmed the tenant settings look correct, licensing is in place, no Conditional Access policies should be blocking access, and users are still hitting consistent Clipchamp errors, it's time to escalate. Before you call, gather the browser console error log (F12 → Console tab, screenshot the errors), the Event Viewer entries from the affected machine, and the user's UPN and license assignment details. This cuts the support call time significantly. You can open a ticket directly at Microsoft Support, choose Microsoft 365 and then Clipchamp or SharePoint as the product category.
Prevention & Best Practices for Clipchamp in Microsoft 365
Most Clipchamp headaches are preventable with a bit of upfront planning, especially around how you organize and share video content. Here's what I recommend based on both the official Microsoft guidance and real-world experience managing Microsoft 365 video content at scale.
Match your storage location to your sharing intent. Microsoft's documentation lays out a clear framework for this. For small-scale sharing, like a quick onboarding clip, uploading to your personal OneDrive and sharing a link is perfectly fine. For team collaboration where multiple people need to contribute and view videos, upload directly to a private Teams team or SharePoint team site. For organization-wide video content that anyone should be able to watch, a public SharePoint communication site is the right home. Getting this right from the start prevents the most common "why can't my colleague see this?" issues.
Don't rely on the Clipchamp homepage as your only way to find videos. The homepage is a convenience index, it shows videos from your OneDrive and places you've recently interacted with. It is not an exhaustive catalog of every video in your organization. For organization-wide video discovery, set up a dedicated SharePoint communication site with video content surfaced through the Highlighted content web part, scoped to video file types across your relevant sites.
Set retention policies before you need them. Because Clipchamp videos are regular SharePoint/OneDrive files, Microsoft 365 retention policies apply to them. If you need to keep meeting recordings for compliance or legal reasons, configure a retention policy in the Microsoft Purview compliance portal that covers the OneDrive and SharePoint locations where recordings land. Don't wait until you need to produce a recording for legal discovery to find out you never set this up.
Train your team on where recordings go. A significant source of "missing recording" tickets in IT help desks is simply that users don't know Teams recordings end up in OneDrive/SharePoint rather than a dedicated video portal. Five minutes of proactive communication, a quick email or Teams post explaining where to find recordings, eliminates a large volume of confusion down the road.
- Pin the Clipchamp app to your Microsoft 365 app launcher so you can reach your video homepage with one click, without hunting through menus.
- Create a dedicated Recordings folder in your team's SharePoint document library and point your Teams channel meeting recording policy to that location, keeps things organized automatically.
- When sharing a video externally, always generate a fresh share link from OneDrive/SharePoint rather than reusing old links, permissions can change and old links may silently stop working.
- Run a quarterly review of your OneDrive storage usage, video files accumulate fast. Archive or delete old recordings you no longer need to stay well under your storage quota and avoid upload failures.
Frequently Asked Questions About Microsoft Clipchamp
Why doesn't Microsoft Clipchamp have a single video portal like YouTube or the old Stream?
This is one of the most common questions I get, and the short answer is: Microsoft looked at how people actually used Stream Classic and found that 83% of all page views came from direct links and embeds outside the portal itself. Only 5% of traffic went to Stream's homepage directly. People weren't exploring a video portal, they were just using Stream as a hosting service and linking to videos from SharePoint intranet pages, Teams, and other tools. So Microsoft made those destinations, SharePoint, Teams, OneDrive, the actual home for video, rather than maintaining a separate portal that most people ignored. This means there's no "YouTube-like" browse experience in Clipchamp by design. If your organization needs a curated video destination, you can build one yourself using a SharePoint communication site with the Highlighted content web part scoped to video files.
Where exactly are my Clipchamp videos stored? Are they safe if I delete my OneDrive files?
Your Clipchamp videos are stored directly in your OneDrive for Business or in SharePoint document libraries, as regular MP4 or video files, just like any other document. They're not stored in a separate video database. This means they get the same protections as your other Microsoft 365 files: versioning, recycle bin recovery, eDiscovery, Legal Hold, and retention policy coverage. But it also means that if you delete the file from OneDrive, the video is gone from Clipchamp too. The Clipchamp recycle bin and OneDrive recycle bin are the same thing. You have 93 days (in most configurations) to recover deleted files from the OneDrive recycle bin before they're permanently removed.
My Teams meeting recording isn't showing up anywhere, not in Clipchamp, not in OneDrive. What happened?
A few things can cause a Teams recording to disappear entirely. First, if the recording failed mid-meeting (network drop, host ending the call abruptly), the partial recording may not have been saved at all, check the Teams meeting chat for a "Recording stopped" notification without a corresponding file link. Second, if the meeting organizer's OneDrive was full at the time of recording, the upload fails silently. Third, if an admin has set a retention policy that automatically deletes recordings after a certain period, older recordings may have already been purged. Finally, check with the meeting organizer, the recording goes to their OneDrive (for personal meetings) or the channel's SharePoint library (for channel meetings), not automatically to every attendee.
Can people outside my organization watch videos I share through Clipchamp?
Yes, but only if your Microsoft 365 tenant allows external sharing on OneDrive and SharePoint, and only if you specifically share the video with an "Anyone with the link" or "Specific people" setting that includes the external user. Your IT admin controls external sharing at the tenant level in the SharePoint admin center under Policies > Sharing. If external sharing is disabled at the tenant level, there is no way to share Clipchamp videos externally regardless of what settings you choose inside Clipchamp itself. When external sharing is allowed, recipients outside your org get a standard video playback experience in their browser, they don't need a Microsoft 365 account to watch the video, only to comment or collaborate on it.
I'm getting a "Something went wrong" error on the Clipchamp homepage with no error code. How do I diagnose it?
That generic error message is one of the most annoying things about Clipchamp's current error handling, it tells you nothing. The first thing to do is open your browser's developer tools (F12), click the Console tab, and reload the Clipchamp homepage. The actual error will appear in the console, look for red error lines mentioning SharePoint, OneDrive, or authentication. Common ones include 401 Unauthorized (your session token expired, sign out and back in), 403 Forbidden (a Conditional Access policy or permission issue), and 404 Not Found (a video file was deleted from the underlying storage). Once you have the real error from the console, you have something actionable to search for or hand to your IT admin.
Does Clipchamp work for organizations that want a single company-wide video library that everyone can browse?
It does, but not through a dedicated portal UI the way Stream Classic worked. The recommended approach is to create a public SharePoint communication site open to all users in your organization, and set it up as your video destination. You can use the Highlighted content web part on that site scoped to video file types, pulling in videos from across multiple SharePoint sites to create a browsable video library experience. Users can upload directly to that site, and the content surfaces in a familiar SharePoint page experience. For organization-wide announcements where only a few people publish but everyone watches, a SharePoint communication site with restricted upload permissions fits perfectly, you get the curation of a portal without a separate tool to manage.