Premiere Pro "The importer reported a generic error": how to fix it
By the FixMP4 engineering team · · 8 min read
"The importer reported a generic error" is Premiere Pro's catch-all import failure. You may also see "File format not supported", "Unsupported compression type" or "The file has no audio or video streams". The message is vague because the importer only knows that it failed. Most of the time the footage is fine and Premiere's cache, decoder settings or the file's location are the problem. Occasionally the file really is broken. This guide goes from the fastest fixes to the deeper ones.
Before anything: is it one file or all files?
- Only one clip fails, similar clips from the same camera import: suspect that file (damage or an unusual setting).
- All clips from one device fail: suspect the codec or hardware decoding.
- Everything fails, including files that imported last week: suspect the media cache, an update, or permissions.
Also play the failing clip in VLC. VLC opening it is a strong sign the file is healthy.
Fix 1: clean the media cache
Premiere keeps a media cache of conformed audio (.cfa), peak files (.pek) and index files for every clip it has seen. If these get out of date, for example after a crash, a drive change or an update, imports can fail with a generic error.
- Close all projects.
- Open Preferences, Media Cache.
- Click Delete next to Remove Media Cache Files, and choose to delete all files.
- Optionally move the cache to a fast internal drive with plenty of space.
- Restart Premiere and import again.
This is safe: your footage and project files are not touched; Premiere rebuilds the cache as needed.
Fix 2: rename, move and re-import
Premiere is sensitive to paths:
- Move the file to a short path on a local drive, for example D:\Footage\shoot1.
- Remove special characters, emoji and very long names from the file name.
- Avoid importing directly from a camera card, a phone connected by USB, a cloud-synced folder or a network share. Copy the files first.
- Import through the Media Browser panel for camera card structures (it understands spanned clips and sidecar files), and through File, Import for single files.
Fix 3: hardware decoding and codecs
Modern footage is often H.265 (HEVC), 10-bit, 4:2:2 or high frame rate. Premiere decodes some of this on the GPU, and the result depends on your graphics hardware and driver.
- Update Premiere Pro and your graphics driver.
- Open Preferences, Media and toggle Enable hardware accelerated decoding, then restart and try again. If it was on, turn it off; if it was off, turn it on.
- On Windows, some HEVC handling depends on system components; installing HEVC Video Extensions can help with playback in other apps but Premiere uses its own decoders, so updating Premiere matters more.
- Check the codec with MediaInfo. Formats Premiere does not import natively include WebM with VP9 or AV1 in some versions, MKV, and unusual audio codecs inside MP4.
Fix 4: variable frame rate and screen recordings
Phone videos, screen recordings and game captures are often variable frame rate. Premiere usually imports them but sometimes fails with a generic error, or imports them with sync drift. Transcode a copy to constant frame rate with Shutter Encoder, HandBrake or Media Encoder, using an editing-friendly codec such as ProRes 422 or DNxHR. Editing from these intermediates is also smoother on slower machines.
Fix 5: project and preferences
If imports fail in one project only, create a new project and import there. If that works, import the old project into the new one (File, Import, select the .prproj). If imports fail everywhere, reset preferences by holding Alt (Windows) or Option (Mac) while launching Premiere until the splash screen appears.
When the file is actually damaged
If VLC cannot play the file, MediaInfo lists no video or audio stream, and the size looks right for the length of the recording, the file was most likely not finalised. This happens when a camera or phone loses power mid-take, when a recorder app crashes, when a card is pulled during writing, or when a screen recording is killed. MP4 and MOV store the index of every frame in a section written at the end (the moov atom). Without it, Premiere's importer finds a file with data but no description and gives up with a generic error.
Recovering the clip
- Keep the original untouched and work on a copy.
- Record or find a short healthy clip from the same camera with the same resolution, frame rate and codec. It supplies the codec settings that the broken file lost.
- Open the FixMP4 repair tool, add the broken file and the reference. The rebuild happens locally in your browser; client footage is not uploaded.
- Check the free preview. If the footage is there, export the repaired MP4 and import it into Premiere.
FixMP4 rebuilds H.264, HEVC and AAC streams. Cameras that record linear PCM audio may give back video without camera audio; the preview shows this before you pay. Our article on choosing a reference file has tips for getting the match right.
If the broken file is a Premiere export
That is a different situation: an export that crashed mid-render. The best fix is to export again from the project. If the project is gone, the partial export can sometimes be rebuilt; see Premiere Pro export corrupted.
Quick reference
| Symptom | First fix |
|---|---|
| Generic error on files that used to import | Clean media cache, restart |
| Generic error only on HEVC/10-bit clips | Update Premiere and GPU driver, toggle hardware decoding |
| Generic error on screen recordings | Transcode to constant frame rate ProRes or DNxHR |
| Error only from card or phone | Copy files locally, import via Media Browser |
| No player can open the file | Repair the file structure, then import |
Related reading
For the same family of problems in other apps, see DaVinci Resolve Media Offline, HandBrake "No valid source found" and iMovie "file could not be imported". If the file needs repairing, the main guide to repairing a corrupted video explains each step.
Frequently asked questions
What does "The importer reported a generic error" mean in Premiere Pro?
Premiere tried to open the file with its importer and the importer failed without a specific reason. Typical causes are a stale media cache, a codec or hardware decoding issue, a file path problem, or a file that is damaged.
Does clearing the media cache delete my footage?
No. The media cache holds conformed audio and index files that Premiere generates from your footage. Deleting it only forces Premiere to rebuild them; the original media and your project are not touched.
Why does an iPhone or drone clip fail to import into Premiere?
These are often HEVC, 10-bit or variable frame rate files. Older Premiere versions or systems without hardware HEVC decoding struggle with them. Update Premiere, toggle hardware decoding, or transcode a copy to an editing codec.
How can I tell if the file is corrupted instead of Premiere?
Play it in VLC and check it with MediaInfo. If no player can open it and MediaInfo shows no video stream, the file is damaged, typically a missing index after an interrupted recording.
Have a broken recording right now?
Diagnose it and hear or watch a free repaired preview. Nothing is uploaded.
Open the repair tool