An unsupported-file message in Clipchamp is a reason to inspect the actual media, not just its extension. Check the source copy, file/container and codecs; even a supported format can fail if a file is incomplete or damaged.
Quick answer and symptom diagnostic table
| Symptom | First check |
|---|---|
| File rejected immediately | Confirm it is a complete media file and compare its format with Microsoft’s current list. |
| MP4 or MOV rejected | Inspect the video/audio encoding and try obtaining the original again. |
| Import appears stuck | Allow for conversion where needed; if it never progresses, follow the loading checklist. |
| File contains project instructions | Open the project in its original app; obtain an exported media file for import. |
Keep the original while testing a new download or converted copy.
Media file vs project file distinction
Verify that the file you are importing is actual video media rather than a project configuration:
- Video Media Files: Files with extensions like .mp4, .mov, or .webm contain raw video data.
- Clipchamp Project Files: Files associated with saved editing projects contain timeline instructions, not embedded media.
- Local Player Test: Open the file in a desktop media player (such as VLC or QuickTime). Playback is a useful check, but does not prove the whole file is intact or that Clipchamp supports its encoding.
Container vs codec: why renaming suffixes fails
A file extension (like .mp4 or .mov) is merely an external container box. Inside that box are encoded video and audio streams created by specific codecs:
- Containers: .mp4, .mov, .avi, .mkv.
- Video Codecs: H.264 (AVC), H.265 (HEVC), VP9, AV1, ProRes.
- Audio Codecs: AAC, MP3, PCM, AC3.
Renaming a file from video.mkv to video.mp4 in File Explorer changes only the container label. It does not alter the underlying codec stream. Clipchamp will still reject the file if the internal codec stream is unsupported.
Supported formats for Clipchamp accounts
Microsoft’s supported-format list applies to personal and work accounts. It includes MP4, MOV, WebM, AVI, DIVX, 3GP, WMV, VOB and MKV. Some inputs are converted before editing, so longer loading does not by itself mean rejection.
Microsoft recommends MP4 or WebM for faster video import. The container does not guarantee every encoding inside it is readable. Follow the actual error and current support guidance rather than treating all HEVC, ProRes, MKV or AVI files as universally unsupported.
Enjoying this read?
Get weekly insights on video editing, AI workflows, and creator growth straight to your inbox.
Initial troubleshooting steps
Keep the original, confirm any cloud download or camera transfer completed and inspect the file with a media player. If the source can be obtained again, test that new copy.
Microsoft’s unsupported-file guidance suggests obtaining the affected file again or converting it outside Clipchamp. If the whole project will not open, use the separate loading checklist before changing codecs.
Converting a file copy with compatible settings
Use a converter to create a new output file, leaving the original untouched. A practical compatibility candidate is MP4 with H.264 video and AAC audio. Check the converter’s current controls and the destination’s requirements; settings are not a guarantee that a damaged input can be repaired.
Preserve intended dimensions and duration, and inspect frame-rate choices instead of forcing every source to 30 fps. Conversion can change image quality, color or timing. See HandBrake’s official container documentation for MP4/MKV choices.
Open the converted copy locally and compare it with the original before importing it. Renaming a file’s extension is not conversion.
Import and review converted copy
After importing your converted file into Clipchamp:
- Inspect playback: Play the clip on the timeline to verify video smoothness and audio alignment.
- Check image sharpness: Ensure the conversion did not introduce unwanted compression artifacts.
- Verify clip duration: Confirm the full video duration imported without early truncation.
If failures persist
If conversion does not resolve the issue:
- For whole-project loading stalls, see Clipchamp Project or Media Not Loading.
- For export errors after importing, see Clipchamp Export Stuck or Failing.
- For output size questions, see Why Is My Edited Video Larger Than the Original?.
Optional Cubix workflow
For a separate edit in Cubix, start with your original footage. Upload the source media, make the intended changes and inspect the exported video. See Cubix export instructions for that workflow.
The editor entry opens Home. It does not transfer a third-party project or automatically upload/import the reader’s files.
Don’t miss the next one.
Join our newsletter for exclusive tips, product updates, and the latest from the Cubix team.