How to Put Plugins in After Effects (Full Setup Guide)

You've downloaded the plugin, double-clicked the installer, restarted After Effects, and still nothing appears where it should. That usually isn't a random glitch, it's a file-path mismatch or the wrong install method for the thing you bought. If you know where the file is supposed to live, how to put plugins in After Effects gets a lot less frustrating.

Table of Contents

• Why Your Plugin Isn't Showing Up
• Installing Native AEX and Plugin Bundles Manually
  • The folder choice decides where the plug-in appears
• Using ZXP Installers and Adobe Exchange
  • What happens during a ZXP install
• Adding Scripts, Panels, and Extensions
  • Scripts are not plug-ins
• Checking Compatibility Before You Install
  • Three checks that save the most time
• Fixing the Most Common Installation Problems
  • Symptom to cause mapping
• A Sustainable Plugin Management Workflow
  • A quick reference for the three install paths

Why Your Plugin Isn't Showing Up

The first mistake is treating every download like it belongs in the same folder. After Effects routes native plug-ins, ZXP-installed extensions, and scripts or panels through different install paths, so a file can be copied somewhere, restart cleanly, and still never appear where you expect.

I see that happen constantly on team machines. One artist drops a .aex or .plugin bundle into a folder and waits for it to show up under Effects. Someone else installs a panel correctly enough for the file system, then keeps hunting for it in the Effects menu instead of Window. The file works fine. It's just in the wrong category.

Adobe's SDK guidance separates the app-specific Plug-ins folder from the shared MediaCore folder, depending on whether the tool is meant only for After Effects or shared across Adobe video apps, and those paths change by platform and version Adobe SDK plug-in install locations. That folder split still governs how many installs behave, which is why a lot of fixes still come down to closing After Effects, copying the right file to the right place, and relaunching. The same logic also explains why a plugin can behave like an unsupported app on another system, the same kind of problem you run into when you try to add unsupported apps to your LG TV.

Practical rule: check the package type before you copy anything. A native effect, a ZXP package, and a script all use different install routes.

Start by reading the file name and the package contents. If you see .aex on Windows or .plugin on Mac, you're usually dealing with a native plug-in. If the download is a .zxp, it belongs in an installer workflow. If the file is .jsx, .jsxbin, or a panel-style bundle, stop looking in the Effects menu and look for the scripts or panels path instead.

If the package still feels unclear after you unpack it, compare it with a troubleshooting walkthrough like Armox's After Effects troubleshooting guide. That saves time when a file is technically installed but still missing because it was placed for the wrong plug-in type.

Installing Native AEX and Plugin Bundles Manually

The manual route is the one that still catches people off guard. Native plug-ins and bundles do not all install the same way, and the folder you choose determines whether After Effects sees the effect at all. On Windows, Adobe documents an app-specific path under C:\Program Files\Adobe\Adobe After Effects\Support Files\Plug-ins, and it also separates that from the shared MediaCore location Adobe SDK plug-in install locations.

The folder choice decides where the plug-in appears

If the plug-in is meant only for After Effects, use the app-specific Plug-ins folder. If it is built to work across Adobe video apps, use the common MediaCore path. On macOS, Adobe documents the app-specific location as /Applications/Adobe After Effects [version]/Plug-ins/, and the shared path as /Library/Application Support/Adobe/Common/Plug-ins/[version]/MediaCore Adobe SDK plug-in install locations.

That split matters in real installs. Put a shared MediaCore plug-in in the After Effects-only folder, and you may still get it working in one app while breaking the intended app-to-app behavior. Put a private After Effects effect in MediaCore, and you expose it to other Adobe apps whether you meant to or not.

Close After Effects before you copy anything. Then move the .aex file on Windows, or the .plugin bundle on Mac, into the target Plug-ins folder and relaunch the app so it can scan and register the new effect manual plug-in install workflow. That restart is required. It is when After Effects scans the folder and adds the new effect to its list.

Keep a clean record of the installer, the exact folder path you used, and which machine it went on. That saves time when a client project moves from a studio workstation to a laptop, and it also makes it easier to spot a bad copy before it turns into a longer support mess.

For a useful parallel on file-based installs, the add unsupported apps to your LG TV guide shows the same folder discipline. Different product, same habit, put the right file in the right directory and do not expect the software to guess.

Put the plug-in where the software expects it, not where it feels convenient. After Effects is consistent, but it is not forgiving.

Using ZXP Installers and Adobe Exchange

ZXP files are a different animal. They're usually packaged for installer-based delivery, so After Effects itself doesn't open them directly. That's why a helper app is required, often Aescripts AeX ZXP Installer or Anastasiy's Extension Manager, both of which handle the actual install step for you.

What happens during a ZXP install

In practice, the workflow is straightforward. Install the helper first, then open or double-click the .zxp, confirm the install, and restart After Effects. If the extension is tied to Adobe Exchange or an account-based entitlement, sign in where prompted before you expect it to appear.

Under the hood, a ZXP is a packaged extension with a manifest that tells Adobe where the files belong. That's why this route often feels smoother than a manual copy. The installer is doing the path mapping for you, which means fewer chances to place a bundle in the wrong app folder.

If the installer says the plug-in is incompatible with your version of After Effects, treat that as a real blocker, not a suggestion. The package may be built for a newer or older release, or it may expect an architecture or licensing state your current install doesn't have. No amount of relaunching fixes a package built for the wrong target.

The cleanest habit is to keep the helper app updated, install one ZXP at a time, and verify the plug-in in After Effects before moving on. That way, if something fails, you know exactly which package did it. When you're managing multiple commercial tools, that separation matters more than speed.

Adding Scripts, Panels, and Extensions

A lot of “plugin not showing up” tickets are really script or panel problems. Those tools don't live in the Effects menu at all, so the first error is looking in the wrong place. JSX scripts run from File > Scripts, dockable panels show up under Window, and older CEP extensions may sit under Window > Extensions depending on how the tool was built.

Scripts are not plug-ins

If you're installing a .jsx or .jsxbin file, it usually goes in the After Effects Scripts folder, not the plug-ins folder. Adobe exposes that location through Edit > Preferences > Scripts & Expressions > Reveal in Explorer/Finder, which is the fastest way to find the right directory on the exact machine you're using.

If the tool is a ScriptUI panel, the folder is usually tied to the Scripts or Scripts/ScriptUI Panels path rather than Effects. That's why a tool like a motion helper, batch renamer, or utility panel can feel “missing” even when it's installed correctly. It was never meant to appear as an effect.

For CEP-based tools, look under the appropriate extension location and remember that they often need permissions enabled before they can write files or reach the network. If the panel opens but behaves strangely, the install may be correct while the permissions are not.

This is the moment where a lot of people lose time by forcing every file into the Plug-ins folder. Don't do that. A script copied into the wrong place doesn't become a plug-in, it just becomes clutter.

If you build your own tools or hand off custom utilities on teams, how to create video effects is a useful companion reference because it keeps the distinction between effects, scripts, and extensions clear before packaging starts.

If it lives under File, Window, or Extensions, you're probably not dealing with a plug-in at all.

Checking Compatibility Before You Install

Before you copy anything, check the version and architecture. That sounds tedious until a plug-in crashes on launch because it was built for the wrong After Effects release or the wrong CPU type. On newer Macs, an Apple Silicon-native build can matter just as much as the folder path.

Three checks that save the most time

First, verify the exact After Effects version and build you're running, then compare it with the plug-in's release notes. If the tool was compiled for a specific version range, that mismatch is the difference between a clean load and a blank menu entry.

Second, check whether you're on Intel or Apple Silicon. Mixed-environment studios still run into this constantly because one machine can load a package that another machine can't, even though both look “up to date” from the user's point of view.

Third, look at the license model. Some tools are tied to a single machine, some rely on a floating or server-based setup, and some want activation before they'll fully load. A simple file copy won't solve an entitlement problem.

For anyone comparing tools across editing ecosystems, the SubmitMySaas-2 editor comparison is a useful reminder that software choice and deployment method go together. The best tool on paper still fails if it doesn't fit the machine you're installing it on.

Keep this rule in mind. Compatibility first, installation second. It's faster to reject an incompatible build before copying files than to chase a crash after the fact.

Fixing the Most Common Installation Problems

When a plug-in fails, the symptom usually tells you what went wrong. A greyed-out effect, a missing menu item, or a startup crash each points to a different cause, so don't use the same fix for all of them.

Symptom to cause mapping

If the plug-in appears in the Effects list but is greyed out, the issue is often a bit-depth, project setting, or color pipeline mismatch. Check the plug-in's own requirements, then test it in a simple comp before assuming the install failed.

If it doesn't appear at all, go back to the folder path and version. The file may be in the wrong Plug-ins directory, or you may be launching a different After Effects version than the one you installed into. On shared machines, that happens more often than people think.

If After Effects crashes on launch after install, isolate the last file you added and remove it temporarily. Corrupted cache, a conflicting plug-in, or a mismatched build can all cause startup failure, and the quickest diagnostic step is to start clean and add items back one at a time.

On Mac, leftover files from older installs can also confuse the app. When a tool has been removed and reinstalled several times, stale preferences or cache artifacts can keep the new install from loading cleanly. Clear the disk cache, restart, and test again before reinstalling a third time.

Practical rule: close After Effects properly before copying any plug-in files. A surprising number of “broken installs” are just incomplete file updates.

If you only remember one diagnostic move, make it this one. Remove the last change, restart the app, and confirm whether the problem disappears. That tells you more than random reinstalling ever will.

A Sustainable Plugin Management Workflow

The easiest way to stay sane is to treat plug-ins like production assets, not disposable downloads. Keep installer archives in one place, track license keys and serial numbers in a password-protected note, and test new tools in a scratch project before trusting them on client work. For studios standardizing their setup, workflow standardization is the right mindset, because consistency beats improvisation when five machines need the same toolset.

A quick reference for the three install paths

When you build this into a repeatable habit, reinstalling after a wipe stops being a scavenger hunt. You know where the files live, which menu they should appear in, and what to check before you blame After Effects.

If your team is juggling plug-ins, scripts, and mixed machine setups, Armox Labs can help you turn that chaos into a repeatable creative workflow. Visit Armox Labs to see how a single visual workspace can support more organized production across tools, projects, and handoffs.