After Effects Essential Properties: Designing a Reusable .mogrt Control Surface
Essential Properties turn an After Effects composition into a reusable Motion Graphics template. Expose a minimal, well-named control surface and let expressions handle the rest.
01 Feb 2026, 20:58 UTC

You spend an hour perfecting a lower-third in After Effects—custom easing, a clean accent bar, a type treatment that matches the brand. Then the editor messages you: “Can you make the bar 20 percent wider and swap the blue for orange?” Without a plan, you either render a dozen variants or open the timeline and start dragging properties into the Essential Graphics panel until the editor has forty sliders to wrestle with. The useful takeaway is that Essential Properties work best when you treat them like an API, not a settings dump. Expose a small, well-named set of upstream controls, drive everything else with expressions, and the template stays predictable long after you close the project.
Why exposing every property breaks the handoff
The Essential Graphics panel lets you promote almost any timeline property into a custom control list. That flexibility is the trap. When an editor opens a .mogrt and sees separate controls for position, scale, rotation, opacity, and every keyframe-able parameter, the cognitive load is worse than rebuilding the graphic from scratch. The editor does not care that the accent bar has independent X and Y scale; they care that it is too short. Your job is to decide what the editor should change, not to expose everything that is technically possible.
Treat the promoted list as the template’s public interface. A short list with clear names—“Accent Color,” “Bar Width,” “Duration”—reduces support messages more effectively than any documentation you could write.
The single-control pattern: one effect, many expressions
The robust pattern is to add a single control effect—typically a Slider Control or Color Control applied to an Adjustment Layer or Null—and drag that effect’s properties into the Essential Graphics panel. You then use expressions to map that one value onto the actual animated properties. This keeps the public surface small and predictable.
There is a wiring detail that matters: expressions reference the control effect by its actual name in the Effects panel, not by the friendly label you assign in Essential Graphics. If you rename the effect itself from “Slider Control” to “BarWidth,” expressions that use effect("BarWidth")("Slider") keep working. If you rename the Essential Properties label to “Bar Width,” the expression still works because it points at the underlying effect. Relabeling the exposed control is safe; renaming the effect is not, unless you update every expression that references it.
Worked example: a lower-third with three exposed controls
Imagine a composition named LowerThird_Main containing a text layer, a shape layer for the accent bar, and a Null layer named Controls. On the Null, apply a Color Control effect named AccentColor and two Slider Control effects named BarWidth and AnimDuration.
Open Window > Essential Graphics. Drag AccentColor, BarWidth, and AnimDuration from the timeline into the Essential Graphics panel. Rename the promoted entries to “Accent Color,” “Bar Width,” and “Duration.” Reorder them so the most frequently changed control appears first.
Now wire the internals. Select the accent bar’s Scale property and add an expression that reads the slider. If the bar’s base width is 200 pixels and you want the slider to act as a percentage, the expression might be:
var base = 200;
var pct = thisComp.layer("Controls").effect("BarWidth")("Slider");
[base * pct / 100, 100]
This assumes the bar’s anchor point is set so it scales from the left edge; adjust the expression or the anchor if it grows from the center. For the text layer’s Opacity, drive a fade-in from the duration control, treating the slider value as seconds:
var dur = thisComp.layer("Controls").effect("AnimDuration")("Slider");
linear(time, 0, dur, 0, 100)
These expressions point at BarWidth and AnimDuration, the actual effect names. If you later change the Essential Properties label from “Bar Width” to “Width,” the expression does not break.
To verify locally, change the BarWidth slider in After Effects and confirm the bar’s scale updates. Change AnimDuration and confirm the text fade stretches or compresses. If nothing moves, check that the expression references the effect name, not the panel label.
Exporting to Premiere Pro and the version trap
When the comp behaves correctly, export it as a Motion Graphics template. In After Effects, use File > Export > Motion Graphics Template or the export option in the Essential Graphics panel. The resulting .mogrt file carries the promoted controls into Premiere Pro. The editor drops it on a timeline, opens the Essential Graphics panel, and edits “Accent Color,” “Bar Width,” and “Duration.” The expression logic stays locked inside the composition.
The trade-off is version sensitivity. Property types that can be promoted, panel layout details, and how older Premiere Pro builds interpret a .mogrt can differ. A template authored in a newer After Effects may not expose the same controls in an older Premiere Pro, or may render with unexpected defaults. Deeply nested precomps and cross-comp property links make the problem worse because they increase maintenance cost and are more likely to behave differently across versions. Before you ship a template to a team, import a minimal test comp into the exact Premiere Pro version your audience uses and confirm the renamed controls appear and drive the graphic.
An actionable checklist
- Open Window > Essential Graphics and decide on two to four controls the editor truly needs.
- Add one control effect per parameter to a Null or Adjustment Layer; name the effects descriptively.
- Drag the effects into the Essential Graphics panel, then rename and reorder the promoted entries for the editor.
- Write expressions that reference the effect names, not the friendly labels.
- Export a test
.mogrtand verify it in the target Premiere Pro version before distributing it.
A template is not a collection of exposed properties; it is a decision about what the next person should be able to change. Keep that surface small, name it clearly, and the handoff stops being a negotiation.
0 replies
A thoughtful contribution can make all the difference. Be the first to share one.