.avif)
Freevisuals
Error 86::1 is genuinely one of the longest running, most persistently reported import errors in After Effects, with documented cases stretching back across many years and multiple versions without Adobe ever fully resolving the underlying cause. The message typically reads something like the source compression type is not supported, or could not open source file, please check that file exists with correct permissions, and it appears despite the exact same file playing back perfectly fine in QuickTime, Premiere Pro, or virtually any other media player on your system.
Error 86::1 in After Effects most commonly indicates the application's importer does not recognize the specific codec inside a video file's container, even though the file itself is not genuinely corrupted and plays correctly elsewhere. This post covers the three most consistently confirmed fixes, re-encoding the affected file through Adobe Media Encoder, the genuinely unusual but repeatedly confirmed file extension renaming trick, and addressing a separate, distinct variant of this same error tied to oversized image dimensions on JPG imports specifically. It also covers a known persistent behavior where After Effects continues rejecting a flagged file even after clearing caches, along with frequently asked questions.
By Jack Wright, Founder, Freevisuals. Updated 2026.
The core issue behind Error 86::1 in the overwhelming majority of reported cases traces back to a codec mismatch, the specific compression method used to encode your video file's actual image data is not one After Effects' importer recognizes, even though the file's container format, .mov or .mp4 specifically, looks entirely standard from the outside. This genuinely is not the same thing as file corruption, despite After Effects' own error message often describing the file as damaged or unsupported, and confirming this distinction matters considerably for choosing the right fix rather than assuming your source footage is genuinely lost.
This is the most consistently reported effective fix across the many documented cases of this error. Taking your specific affected file and running it through Adobe Media Encoder, converting it to a standard H.264 MP4 even if it was already technically an MP4 file to begin with, resolves the issue for the large majority of editors who try it. This works because Media Encoder's own encoding pipeline outputs a file using a codec configuration After Effects' importer reliably recognizes, effectively normalizing whatever exotic or unusual compression setting your original file was using into something After Effects can actually read correctly.
This fix sounds genuinely implausible, but it has been independently confirmed by multiple editors across separate Adobe community threads spanning several years, and it costs nothing to try. Simply renaming your affected file's extension, changing .mov to .avi, for instance, or to virtually any other extension, then attempting to import it again into After Effects, resolves the error for a meaningful number of documented cases. The underlying explanation appears to be that After Effects' import detection logic behaves differently once triggered by a different file extension, sidestepping whatever specific detection path was failing previously, even though the actual file content itself remains completely unchanged.
Since this fix is genuinely low risk, your original file remains fully intact regardless of what you rename it to, it's worth trying early in your troubleshooting process specifically because it takes only a few seconds and has a real, documented track record of success despite how unusual it initially sounds.
For a demonstration working through general After Effects file import and crash troubleshooting, watch Fix After Effects Crash When Opening Files, Not Responding, which covers a genuine diagnostic sequence relevant to import related errors more broadly. This is worth watching specifically because understanding the general pattern of testing a file in isolation, checking whether the issue is file specific or system wide, applies directly to diagnosing exactly which of the fixes in this guide is most likely to resolve your particular case.
It's worth knowing about a genuinely distinct cause behind this exact same error code, specifically affecting very large, high resolution JPG image imports rather than video files. Documented cases show this error triggering on JPG files with pixel dimensions in the range of roughly 18,500 pixels wide or larger, with the exact same file opening correctly in Photoshop and standard photo viewers, but being rejected by After Effects specifically as corrupt or damaged during import.
Two confirmed fixes address this specific variant. Reducing your image's actual pixel dimensions before import, even a relatively modest reduction from an extremely large source file, resolves the issue directly, since the underlying limitation appears tied to a dimension threshold After Effects' JPG importer specifically struggles with. Alternatively, saving your source image as a PNG file instead of a JPG resolves the issue entirely while preserving your full original resolution, since PNG imports do not appear to hit this same specific dimensional limitation even at considerably larger file sizes than the equivalent JPG would need to be reduced to.
A genuinely frustrating pattern reported consistently across many documented cases involves After Effects continuing to reject a specific file even after you believe you've resolved the underlying issue. Once a particular file triggers this error, closing and reopening your project, or clearing your media and disk cache, often does not clear whatever internal flag After Effects has attached to that specific file, meaning the identical error continues appearing on subsequent import attempts even after the file itself has been fixed or replaced. Renaming the file, beyond simply being a potential fix in its own right as covered above, also serves as a reliable way to force After Effects to treat it as a genuinely new file, bypassing this specific persistent flagging behavior when it's the actual underlying obstacle rather than the original codec or dimension issue itself.
For editors working specifically with files stored in OneDrive or a similar cloud synced folder, a related file naming issue has been reported, where simply adjusting your file's name, replacing spaces with dashes specifically, resolved an otherwise identical import failure affecting both After Effects and Premiere Pro simultaneously. macOS users specifically should also be aware that Apple's Catalina update dropped native support for several older QuickTime codec formats, meaning files encoded in one of these now unsupported formats can trigger this exact error purely due to genuine operating system level compatibility loss rather than anything specifically wrong with After Effects itself.
For persistent cases specifically tied to a particular After Effects version, some editors have reported success rolling back to a slightly earlier point release, suggesting this error has, at various points, been tied to genuine regression bugs introduced within specific version updates rather than a single, permanently consistent underlying cause across every affected release.
Given how frequently this error traces back to codec compatibility issues introduced somewhere upstream of After Effects itself, building a deliberate media ingest routine reduces how often you encounter it in the first place. For footage arriving from a genuinely wide variety of sources, screen recording software, phone cameras, and various third party editing or conversion tools, running a quick standardization pass through Media Encoder before that footage ever reaches your After Effects project catches codec compatibility issues early, while you're still organizing your media rather than midway through an active composition when discovering a specific file simply won't import.
This is particularly worth building into your workflow if you regularly receive footage from clients or collaborators using unfamiliar recording setups, since you have genuinely no control over the specific codec settings their equipment or software defaulted to, and a consistent ingest and standardization step protects your own project timeline from being derailed by a compatibility issue that has nothing to do with your own specific system or After Effects installation.
For editors who repeatedly encounter this error with footage from the same specific camera, screen recording application, or conversion tool, it's worth investigating whether that particular source has an adjustable codec or container setting during actual capture or export, rather than only ever encountering and fixing the resulting import error after the fact. Many recording and screen capture applications specifically offer alternative codec options, and switching to a more universally compatible setting at the point of original capture, even if it means a marginally larger file size, can prevent this error from recurring across future footage from that same specific source entirely.
This kind of upstream fix, addressing the actual root cause at its point of origin rather than repeatedly treating the resulting symptom after each new recording session, is particularly worth the initial investigation time for anyone who finds this specific error recurring predictably across projects sourced from the same recurring equipment or software.
A frequent mistake involves assuming your source file is genuinely corrupted based purely on After Effects' own error message, when the file frequently plays correctly in every other application on your system, indicating a codec recognition issue specific to After Effects' importer rather than genuine file damage. Another common issue involves not distinguishing between the video codec variant of this error and the separate oversized JPG dimension variant, applying video specific fixes to an image import issue that actually requires a completely different, unrelated solution.
Once you've genuinely resolved a specific instance of this error, taking a moment to note which particular fix actually worked, along with the specific file type, source, and codec involved if you can identify it, builds genuinely useful personal reference material for the next time this same error appears. Given how many genuinely distinct causes and fixes exist for this single error code, a quick personal record of what worked for your specific past cases considerably speeds up your response the next time, letting you jump directly to the fix that has actually worked for you before rather than working back through every possible cause from scratch each time.
For editors who have already spent considerable time troubleshooting a genuinely stubborn instance of this error without success, it's worth stepping back and confirming your specific file genuinely still plays correctly in at least one other application before continuing further, since this confirms you're still dealing with a codec recognition issue rather than the file having become genuinely damaged at some point during your own troubleshooting process. If the file no longer plays correctly anywhere at all, working from a fresh copy of your original source material, rather than continuing to troubleshoot a file that may have picked up genuine damage along the way, is worth doing before investing further time into fixes that assume the underlying file itself remains intact.
A genuinely reliable import and media handling workflow matters most when it's supporting efficient project work. Our own After Effects templates library is worth exploring once your specific import issues are resolved, and our free LUT library is worth pairing with any project needing a consistent color treatment. For premium templates and additional creative assets, Motion Array and Envato are both worth exploring, and for properly licensed music, Artlist and Epidemic Sound both carry genuinely strong catalogues.
Usually not. This error most commonly indicates After Effects' importer doesn't recognize your specific file's codec, even though the file plays correctly in other applications and is not actually damaged.
This appears to change how After Effects' import detection logic processes the file, sidestepping whatever specific recognition path was failing, even though the file's actual content remains completely unchanged. It's an unusual but genuinely well documented fix.
It's a distinct variant, specifically tied to very large JPG pixel dimensions, roughly 18,500 pixels wide or beyond in documented cases. Reducing your image dimensions, or saving as a PNG instead, resolves this specific version of the error.
After Effects can flag a specific file internally once it triggers this error, and this flag often persists even after clearing caches or reopening your project. Renaming the file forces After Effects to treat it as new, bypassing this persistent flagging behavior.
Yes, particularly on Mac, where macOS Catalina dropped support for several older QuickTime codec formats, meaning files encoded in these now unsupported formats can trigger this error due to genuine OS level compatibility loss.
Error 86::1 has remained a persistent, well documented issue across many years and versions of After Effects, but the confirmed fixes covered here, re-encoding through Media Encoder, the file extension renaming trick, and addressing the separate oversized JPG variant specifically, resolve the overwhelming majority of cases without requiring you to abandon or recreate your original source material. Understanding that this error rarely indicates genuine file corruption, and knowing about the persistent flagging behavior that can outlast your actual fix, saves considerable unnecessary troubleshooting time when this frustrating but ultimately solvable error appears.
Building the preventative ingest habits covered throughout this guide, standardizing footage from unfamiliar sources before it ever reaches your project, and investigating adjustable codec settings at the point of original capture for recurring problem sources, reduces how often this genuinely long standing error interrupts your regular After Effects workflow going forward across future projects and deadlines.
One of the possible reasons why you get this error is that the media files that you are trying to use are corrupted or damaged. This can happen if you download the files from an unreliable source, transfer them from another device, or edit them with a different program. Corrupted or damaged files can have missing or incorrect data that makes them unreadable by After Effects.
The simplest way to fix this problem is to download or copy the files again from a reliable source. For example, if you downloaded the files from a website, you can try to download them again from the same website or a different one. If you copied the files from another device, such as a camera or a USB drive, you can try to copy them again using a different cable or port. Make sure that the download or transfer process is completed without any interruption or error.
To check if this solution works, you can try to import the files again into After Effects and see if the error persists. If it does, you can try the next solution.
Another way to fix this problem is to use a different program to edit the files. Sometimes, the program that you use to edit the files can change or damage the data in a way that makes them incompatible with After Effects. For example, if you use a program like Premiere Pro or Final Cut Pro to edit the files, they might have some settings or effects that are not supported by After Effects. To avoid this, you can use a program that is compatible with After Effects, such as QuickTime or Media Encoder, to edit the files.
To do this, you can follow these steps:
If this solution works, you can continue with your project using the new file. If it does not, you can try the next solution.
Another possible reason why you get this error is that the media files that you are trying to use are missing or unlinked. This can happen if you move, rename, or delete the files after importing them into After Effects, or if you use a network drive or an external storage device that is not connected. Missing or unlinked files can cause After Effects to lose track of where the files are located and how to access them.
The easiest way to fix this problem is to locate and relink the files using the File > Replace Footage command. This command allows you to replace the missing or unlinked files with the original files or new files that are in a different location. To do this, you can follow these steps:
If this solution works, you can continue with your project using the replaced files. If it does not, you can try the next solution.
Another way to fix this problem is to consolidate all the footage in the project using the File > Consolidate All Footage command. This command allows you to copy all the files that are used in the project to a single folder and relink them automatically. This can help you avoid the problem of missing or unlinked files in the future. To do this, you can follow these steps:
If this solution works, you can continue with your project using the consolidated files. If it does not, you can try the next solution.
Another possible reason why you get this error is that the media files that you are trying to use are in a format that is not supported by After Effects. This can depend on the version of After Effects that you are using, the codec of the files, and the settings of your system. Unsupported media format can cause After Effects to fail to recognize or decode the files.
The most common way to fix this problem is to convert the files to a different format that is supported by After Effects. For example, if the files are in a FLV format, you can convert them to a MOV format. To do this, you can use a program like QuickTime or Media Encoder, which are compatible with After Effects. To do this, you can follow these steps:
If this solution works, you can continue with your project using the converted files. If it does not, you can try the next solution.
Another way to fix this problem is to install the required codec or plug-in for After Effects. A codec is a software that compresses and decompresses the data in a media file, while a plug-in is a software that adds extra features or functions to a program. Sometimes, the files that you are trying to use might have a codec or a plug-in that is not installed or enabled on your system. This can prevent After Effects from reading or playing the files.
To fix this, you can try to install the codec or the plug-in that is needed for the files. For example, if the files are in a MKV format, you can install a codec or a plug-in that supports the MKV format, such as the K-Lite Codec Pack or the MKV Importer for After Effects. To do this, you can follow these steps:
If this solution works, you can continue with your project using the files with the installed codec or plug-in. If it does not, you can try the next solution.
.avif)
.avif)
.avif)
.avif)
