EffectCraftAfter Effects plugins in EffectCraft: what runs, what to rebuild
Short answer: After Effects SDK plugins do not run in EffectCraft. The project is a clean-room reimplementation with its own native effects and preset format, so a plugin-dependent look must be rebuilt and checked on the footage and output you plan to use. If you have not decided yet, start with the full comparison, then come back here for the plug-in detail.
The three things people mean by “plugin”
When people ask whether After Effects plugins run in EffectCraft, the question usually means one of three different things, and the answers are not the same.
- Third-party After Effects plug-ins. These are compiled extensions built for After Effects through Adobe’s SDK, such as Trapcode Particular, Element 3D and Sapphire. They do not run in EffectCraft, and the current documentation describes no import path.
- After Effects presets and templates. These include
.ffxanimation presets and.mogrtMotion Graphics templates. Reading.ffxis outside the project’s stated clean-room scope: it is excluded, rather than merely late..mogrthas no direct import path either. - EffectCraft’s own extensions. The app has its own WebAssembly extension path and its own preset files (
.ecpreset, EffectCraft’s own preset format). This is a separate mechanism, not compatibility with Adobe plug-ins. The ecosystem and plug-ins area is graded at 20% in the roadmap (last updated 5 November 2026, checked 11 November 2026).
If your question is mainly about files — .aep, .ffx or .mogrt — see templates and preset compatibility. This guide focuses on the work a plug-in does inside a composition and how to plan a rebuild when it cannot come along.
Check your plug-ins one at a time
Three plug-ins come up often in switching questions. For each one, identify the job it performs, check the documented native tools, and test the result on your own footage. A similarly named built-in effect does not guarantee identical frames.
| Plug-in | What it is usually used for | What the current project docs say | What to do next |
|---|---|---|---|
| Trapcode Particular | Particle systems: smoke, dust, sparks and trails built from emitters. | No import path for the plug-in. Rebuild the shot with native effects. A similarly named built-in effect is not claimed to reproduce Particular’s settings or frames. Native particle effects to start from: Particle Emitter 3D and Particle Playground. | Record the emitter, particle and physics settings for the shot. Rebuild a short sample with native effects and compare the key frames. |
| Element 3D | Placing and rendering 3D models inside a composition. | No import path for the plug-in. The core workflow includes 3D cameras and lights. The current gap assessment lists glTF, OBJ, STL and FBX 7.x model import, with limits on FBX animation and skinning. | Check the model format and material features your shot needs. Import a sample model, then test its lighting and render before planning the full scene. |
| Sapphire | An effect suite for looks such as glows, flares, blurs and damage. | No import path for the suite. EffectCraft documents native Glow, blur and sharpening effects, but each Sapphire look needs its own visual comparison. | List the two or three Sapphire effects actually used in the project and rebuild those looks individually. |
| Any other After Effects plug-in | A specialised effect, generator or workflow inside an After Effects composition. | After Effects SDK plug-ins do not run in EffectCraft. | Use the three-step check below for the specific composition and delivery format. |
Format limits above are from the current gap assessment. The ecosystem grade is at 20% in the roadmap (last updated 5 November 2026, checked 11 November 2026). These are the project’s own grades, not a frame-for-frame match with any third-party product. The downloadable release checked 12 November 2026 is v0.24.1.
What has to be rebuilt
A plug-in is not one feature: it is whatever your composition uses it for. When After Effects plugins cannot come along, these three steps take a project from “which plug-ins does this need?” to “what will the rebuild cost?”
List every plug-in and preset the composition depends on
Why: You cannot estimate a rebuild you have not counted. Missed plug-ins often surface at delivery, when there is least time to respond.
How: Open the original project in After Effects and inspect the effect stack on each layer. Record each plug-in name and version, plus any
.ffxpreset applied to a layer. Note 3D layers and effects on adjustment layers.Checkpoint: Every layer that uses a plug-in is accounted for, and each entry on your list has a name and version.
Rebuild the same look on one small sample
Why: A four-second shot is cheaper to rebuild and easier to judge than a three-minute edit with forty layers.
How: Choose the shot that carries the plug-in look. Recreate it in EffectCraft with native effects, keeping the footage, font, duration and output settings the same so the comparison is meaningful.
Checkpoint: The sample plays for the right duration, and you can identify where the frames match and where they differ.
Compare preview and export on your own machine
Why: The viewer and the exported file are separate checks. A completed render may still differ from the image you intended to deliver.
How: Export an H.264 MP4 of the sample, play it outside EffectCraft, and inspect the exact frames, colour and motion that matter to the job.
Checkpoint: You can name each remaining difference, or state that none appears on your footage and output. Make this check before committing to a deadline.
What EffectCraft uses instead
EffectCraft 0.24.1 offers a native workflow for new compositions. These are building blocks for a tested rebuild, not drop-in replacements for a purchased plug-in.
- Built-in effects, with panels, menus and shortcuts designed to follow After Effects, including a Keying category; see green screen keying in EffectCraft.
- Original preset files in its own
.ecpresetformat; it reads only that preset format. - Editable
.ecprojproject files stored as versioned JSON, so their changes can be inspected in version control. - Its own extension path, separate from After Effects SDK plug-in compatibility; for automation from scripts and AI agents, see the EffectCraft MCP and command-line guide.
- Lottie export built in, where After Effects usually relies on a third-party plug-in; see how to make Lottie without After Effects.
For a first sample, follow the beginner tutorial. The download guide lists the verified 0.24.1 installers.
Frequently asked questions
Short answers about After Effects plugins, presets and project files in EffectCraft.
Can I install Trapcode Particular or Element 3D in EffectCraft?
No. Both are After Effects plug-ins, and EffectCraft does not load After Effects plug-ins. The project grades its own plug-in ecosystem at 20% in the roadmap (last updated 5 November 2026, checked 11 November 2026) — its lowest-graded area — and states plainly that After Effects plug-ins do not run.
Is there a free Trapcode Particular alternative in EffectCraft?
Not a drop-in one. EffectCraft's built-in Simulation effects include Particle Emitter 3D, Particle Emitter 2D and Particle Playground, all marked implemented in the project's effect list, and the effects parity notes say Particle Playground still lacks Particle Exploder and text particles. None of them reads Particular presets or claims to match its frames, so rebuild one short shot and compare it.
What replaces Deep Glow and Flow in EffectCraft?
Neither plug-in runs, but there are native starting points. For glows, use the built-in Glow effect: the effects parity notes say its halo and blur width match After Effects 2026 renders in the project's tests, which is a comparison with After Effects' own Glow, not with Deep Glow. For easing curves kept by name, the bundled Ease Presets panel, an optional ScriptUI extension that ships with the app, covers what ease-curve plug-ins are used for, according to the gap list.
I already paid for my plug-ins. Do they become useless?
Not in After Effects: your licences and the plug-ins stay where they are. What changes is that a composition depending on them cannot move to EffectCraft as an editable timeline. The look is rebuilt with native tools, and the result is a new look you check on your own footage — not the original plug-in’s frames. If plug-ins decide your choice, compare free After Effects alternatives.
Can EffectCraft read .ffx presets or .mogrt templates?
No. Reading .ffx is outside the project’s clean-room scope, so this is not a delayed feature but an excluded one. .mogrt templates have no direct import path either. EffectCraft’s own presets use a separate format.
Does EffectCraft have its own plug-ins or extensions?
Yes. EffectCraft has its own plug-in API for effects written as WebAssembly modules or in Rust, documented in the project's plug-ins guide, and it runs .jsx scripts and ScriptUI panels. The Plug-in Library in the app's settings installs community WebAssembly effects from one reviewed catalog, which the gap list says is still empty. Native plug-in formats, OpenFX first, are planned to run only in separate external helpers. None of this makes an After Effects plug-in work: it is a different mechanism, not a compatibility layer.
Will a later version support After Effects plug-ins?
Nothing here promises a date. The project documents them as not running and grades the ecosystem at 20% in the roadmap (last updated 5 November 2026, checked 11 November 2026); check its current gap list and roadmap for any change. The gap list says hosting the After Effects SDK would need an owner decision, and a maintainer replied in issue #322 that binary After Effects plug-ins can't run in a clean-room, pure-Rust app; native formats such as OpenFX are planned only as separate helpers.