Table of Contents Show
For those who don’t know the tool: Command Frame is a floating search-and-command interface for After Effects developed by motion designer and plugin developer Scott Black. Version 1.5 is available free through aescripts + aeplugins and exposes more than 1,300 actions covering effects, presets, layers, compositions, properties, scripts, panels, workspaces and supported plugin actions.
A command line for After Effects
The basic interaction is simple. Open Command Frame with a shortcut, start typing and execute the matching action. That includes the obvious launcher jobs – plugins and so forth. Effects and presets can be found through fuzzy search, layers and compositions can be searched directly, workspaces can be opened and installed scripts or panels can appear alongside regular After Effects commands.
Basics first: (Bear with us) Properties can also be addressed directly. The examples include commands as: opacity 50; scale kf 120; rotation -15. Relative values are supported too, so a command such as: scale *0.5 halves the current scale rather than replacing it with a fixed value.
This is technically neat, but it is not automatically faster. If three selected layers need to be scaled to 50%, pressing S and entering 50 is already a remarkably efficient piece of 1990s user-interface technology. The more interesting part starts when there is more than one operation.
The ampersand is where it gets useful
Command Frame chains actions with &. Now we are getting somewhere:
center anchor & center layer
set work area to selected layers & trim comp to work area
and:
duplicate & shift 12f & rename suffix _echo & opacity /2
The latter duplicates selected layers, offsets them by twelve frames, adds _echo to their names and halves their opacity. Chains can be saved, named and assigned custom shortcuts. Those shortcuts can then execute the complete sequence without opening the Command Frame interface. At that point the comparison with an effect launcher becomes less useful. Command Frame starts behaving more like a lightweight macro system built from readable After Effects commands.
Bring on the repetitive work
Plenty of After Effects jobs aren’t bottlenecked by creativity. Social campaigns may require large numbers of aspect-ratio, duration, language and content variants. Commercial work can involve repeated adaptation of an approved master. Broadcast packages, lower thirds, end cards and templated motion graphics can involve the same preparation operations dozens or hundreds of times. Those are much stronger candidates for Command Frame than a one-off hero composition.
A finishing artist who performs a familiar sequence ten times a day will probably already know where everything lives. The question is whether the sequence itself can be reduced to one reusable command. The more repetitive the job becomes, the stronger that proposition gets. And if you think all your jobs are repetitive: Have you ever thought of learning Connected Conform within Autodesk Flame?
Copy, paste, pretend you have experience
There is another useful consequence of Command Frame using readable text queries: the command itself can be passed around. A working sequence does not have to begin life as an ExtendScript file or a custom panel. It can be copied from an internal document, production wiki or message and pasted into Command Frame.
That makes a very simple form of internal command library possible without requiring a dedicated library feature in Command Frame itself. A senior artist could establish the approved sequence for a recurring task and document the exact command. Another operator can then reuse it rather than reconstructing the workflow from written instructions. In suitably repetitive work, that creates the entertaining possibility of letting the intern impersonate the finishing artist. Only operationally, of course. Salary negotiations remain outside the current feature set.
This should not be confused with a centrally managed automation system. Command Frame does not document a shared studio command database, access control or automatic synchronisation of team recipes. The library can simply be a collection of known commands stored wherever the production already keeps workflow documentation. For smaller teams, that may actually be enough.
The useful middle ground before scripting
After Effects already has efficient keyboard controls for many common tasks, and proper scripting remains the better solution when a workflow requires conditions, loops, validation, project-specific logic or a maintained production tool. But there is a large collection of smaller jobs that are too repetitive to enjoy and too trivial to justify building software around. Command Frame can package supported operations into a named chain without the user having to write code. That is particularly useful when the operation changes more often than anyone wants to maintain the corresponding script. Edit the command string, save the new version and continue. It also makes these procedures easier to inspect. A command such as:
duplicate & shift 12f & rename suffix _echo & opacity /2
does not require opening somebody else’s JavaScript to determine what will happen. For production documentation, readability is not a bad feature.
Scripts are not excluded
Command Frame does not try to replace an existing After Effects scripting setup either. Installed user scripts can be surfaced as searchable actions. Script folders can be watched, with supported files added or removed from the action list when the folder contents change. ScriptUI panels and regular After Effects panels can also be opened through the same interface. Imported toolbar buttons can become actions, and Command Frame provides an API through which other tools can expose their own commands. Scott Black currently lists integrations with his Control Groups, Compstronaut and Select Every Other Layer extensions.
Individual scripts, plugin actions and complete multi-step chains can then receive their own free-form shortcuts. So the same command can potentially combine native After Effects operations with functionality coming from the surrounding toolset.
Better than FX Console? Wrong question
Command Frame inevitably invites comparison with effect launchers such as FX Console and Adobe’s own Quick Apply. Black makes that comparison himself, and effect and preset search is certainly part of Command Frame. But that is also its least interesting reason to exist.
If the requirement is simply finding an effect quickly, established solutions already cover that problem. Typing a property value instead of using a familiar After Effects shortcut is similarly dependent on personal workflow and may save nothing at all.
The differentiator is the ability to combine operations, retain them as readable commands and turn them into reusable shortcuts. For bespoke animation where every operation is different, Command Frame may just provide another route to controls an experienced artist already knows. For commercial finishing, localisation, social versions and other production lines where the same operations return again and again, it starts looking considerably more practical. In other words: the duller the job, the better Command Frame gets.
Command Frame requires After Effects 2024 or later. On Windows it requires Windows 10 64-bit or newer. Mac users need macOS 13 Ventura or later, with Intel and Apple Silicon supported.
And the price is difficult to argue with: $0.
Command Frame on aescripts + aeplugins
Command Frame press release, Scott Black
| Product | Command Frame |
| Developer | Scott Black |
| Type | Search, command and lightweight automation utility |
| Host environment | Adobe After Effects 2024 or later |
| Current version | 1.5.1 |
| Release date | 19 August 2026 |
| Initial release | 11 May 2026 |
| Price | Free, listed at $0.00 |
| Action catalogue | More than 1,300 actions |
| Search | Effects, presets, layers, compositions, menu commands, panels, workspaces, scripts and supported plugin actions |
| Properties | Opacity, Scale, Rotation, Position, Anchor Point and Orientation, including absolute and relative values |
| Multi-step commands | Actions can be chained with &, saved and named |
| Shortcuts | Individual actions, scripts and saved command chains can receive custom shortcuts |
| Command reuse | Text queries can be reused; saved queries are retained inside Command Frame |
| Script integration | Installed scripts, individually imported scripts and watched script folders |
| Panel integration | After Effects panels and ScriptUI panels |
| Plugin integration | Imported toolbar actions plus API-based integrations |
| Current first-party integrations | Control Groups, Compstronaut, Select Every Other Layer |
| History | Persistent query and execution history |
| Windows | Windows 10 64-bit or later |
| macOS | macOS 13 Ventura or later |
| Mac hardware | Intel and Apple Silicon |
| Downloads | Developer reports more than 3,000 since launch |
| Availability | aescripts + aeplugins |
