Skip to content
Jake In Motion Docs

Bake to Native Effects

Bake recreates a clip’s Motion State animation using native Premiere effects, keyframed per frame.

Once a clip is baked, the motion plays without Motion State installed. That makes it the way to hand a project to an editor, client, or facility that does not own the plugin.

Unbake reverses it, restoring the live Motion State effect.

Bake and Unbake live in the Clip actions section of the Manage tab.

Requirements

Section titled “Requirements”

Bake requires a selection. To bake a whole sequence, select all. Unbake does not require a selection.

Bake also requires an activated license, because a baked clip renders without the Motion State watermark. See Installation and Activation. Unbake is never gated — if a license lapses, you can always restore your clips to editable Motion State.

How to bake

Section titled “How to bake”
  1. Select one or more clips with Motion State applied.
  2. In the Manage tab, open Clip actions.
  3. Click Bake.

Motion State stays on the clip with its Bypass checkbox switched on, so the effect stops rendering but all of its settings survive for a later Unbake.

To reverse it, select the clips and click Unbake.

Which effects Bake uses

Section titled “Which effects Bake uses”

Bake builds a stack of native Premiere effects above the clip, and only creates the ones that clip actually needs.

Keyframes are written across the transition window, and every key is linear. A property that never changes is written as a single static value instead of a keyframe run. A Hold A or Hold B clip bakes to one static pose.

What Bake cannot carry

Section titled “What Bake cannot carry”

These features have no native equivalent and are dropped. The bake report names them per clip:

  • Stroke
  • Glow
  • Corner Smoothness — baked corners are rounded, not squircle-shaped

If a clip depends on any of these, bake it only if you are willing to lose them, or keep an unbaked copy of the sequence.

What Bake approximates

Section titled “What Bake approximates”

These are carried over, but not pixel-exact. The report flags them:

  • Edge Feather — Motion State measures feather in source pixels, Rounded Crop as a percentage. The conversion is close, and the two also differ slightly in character.
  • Motion blur — the Transform’s shutter angle matches, but Transform has no sample-count control, so the blur is close rather than identical.
  • 3D perspective — with Basic 3D, the rotation angles match exactly, but the foreshortening strength is whatever Basic 3D provides rather than your Perspective value.
  • Content Offset combined with 3D — the compensation is exact for a flat clip, and approximate under perspective.

When Bake refuses

Section titled “When Bake refuses”

Bake declines a clip outright, rather than baking something wrong, in these cases:

  • Manual mode — the animation is driven by your own keyframes, so there is no automatic A to B ramp to sample.
  • Time-remapped, speed-changed, or reversed clips — the retimed clock cannot be sampled accurately.
  • Extend to Transitions is on and the clip’s track carries a transition — the timing is then anchored to the transition’s bounds, which Premiere does not expose to the panel. Turn Extend to Transitions off to bake the clip. If the track has no transitions, Extend changes nothing and the clip bakes normally.
  • Adjustment layers.
  • Basic 3D with an off-center Anchor Point — Motion State pivots its 3D around the anchor, but Basic 3D always pivots around the clip’s center. Center the anchor to bake it.
  • Clips whose native Motion or Opacity is already keyframed, or that use native crop or genuine non-uniform scale.
Section titled “Related”