Video file won't import? How to fix it

You have a clip ready for a YouTube tutorial, but your video editor rejects it, gets stuck importing, or shows video without sound. The cause may be the file itself, the browser, or a limit in the editor.

Work through these checks before converting or deleting anything. If you are using an editor in a browser, TooLab's Browser Info can show which media codecs your browser supports. That is a useful clue, but it does not inspect your file or guarantee that the editor accepts it.

Check where the import fails

1. Open Browser Info and review the listed supported codecs. If you know the clip's video and audio codecs, compare them with the browser's support. For more detail on what browser codec information means, see how to check your browser's supported video formats.
2. Try opening the original clip in a media player on your computer. If it will not play there either, the file may be incomplete or damaged.
3. Try importing a short, ordinary video from the same device. If that works, the editor can import files in general, and the original clip is the likely issue.
4. Note what happens with the problem file: does it fail before selection, stop during upload, hang while processing, or import with missing picture or sound? Each symptom points to a different cause.

A file ending in .mp4 or .mov is not guaranteed to use a compatible format. Those extensions describe the container, which can hold different video and audio codecs.

What the result means

The editor rejects the file immediately

The editor may not accept that file extension, codec, resolution, or file size. Check its import requirements. A common example is a MOV file containing HEVC video when the editor only accepts a narrower set of formats.

Import starts, then stops or stays at zero

The file picker found the clip, but the upload or reading process did not finish. A slow or unstable connection can interrupt a cloud editor's upload. If the file is stored on an external drive, network share, or cloud-synced folder, the editor may also lose access while reading it.

The editor imports the clip but shows a blank preview

The editor can read the container but may not decode the video stream. Browser playback support and an editor's import support can differ. A browser codec result is only a clue, not proof that the editor can process the clip.

Picture imports, but sound is missing

The video and audio streams can use different codecs. The editor may accept the picture format but not the audio format, or the clip may have no audio track. Test another clip and check whether the editor shows an audio waveform or track.

The editor appears frozen during processing

Large, high-resolution clips take time to prepare, especially on a computer with little free memory or storage space. If progress does not change after several minutes, try a short copy of the clip or a smaller export from the original recording.

How to fix the import

1. Close and reopen the editor. Cancel the failed import, reload the page or restart the app, then select the file again. In a browser, wait for the editor to finish loading before starting another import.
2. Put a copy on the computer's internal drive. Copy the video from a camera card, USB drive, network folder, or cloud-synced folder to a local folder, then import that copy. Use a short filename with ordinary letters and numbers, such as lesson-intro.mp4. On Windows 11, check free space under Settings › System › Storage. On macOS, check under System Settings › General › Storage.
3. Check the file format and codec. Look at the editor's accepted formats and compare them with the clip's actual video and audio codecs. Do not rely on the extension alone. If the source uses a format the editor does not support, make a separate copy converted to a format the editor recommends. MP4 with H.264 video and AAC audio is widely supported, but follow the editor's own requirements if they differ.
4. Make a shorter test copy. Export or trim a 10 to 20 second section from the original, then try importing it. If the short copy works, the full file may be too large for the editor, or a section of the original may be damaged. Keep the source untouched while you investigate.
5. Try a supported browser or update the current one. For a web editor, use a current browser that the editor supports. Close other tabs and temporarily disable extensions that might interfere with file access or uploads. Browser codec support varies, and an editor may support fewer formats than the browser itself.
6. Transfer the original again if it still fails. A copy interrupted during transfer can look like a valid video file but stop partway through. Copy it again from the camera or phone, or record a short new clip and test that. Avoid using a copy sent through a messaging service if it may have changed or compressed the video.

When the source file may be damaged

If the clip fails in multiple media players and multiple editors, and a fresh copy from the recording device behaves the same way, the source may be corrupted. Check whether the camera or phone still has a playable original. Do not overwrite or format the card until you have copied any important footage elsewhere.

If only one part of a long recording fails, try making a copy that ends before the damaged section. For important footage that cannot be copied or played, stop using the storage card and ask a data recovery professional before attempting repairs that write to it.

Why phone videos can be harder to import

Phones may record variable frame rate video, which means the time between frames changes as the phone records. Some editors handle this poorly, especially when the clip is long or uses a high-resolution mode. A converted copy with a constant frame rate can be easier to edit, but it may take extra time and storage space.

For a tutorial, test the converted copy in the editor and check that the picture and sound stay in sync before building the rest of the project. Keep the original recording until your finished video has exported and played correctly.