Skip to content

Rendering and Quality

Motion State renders through the best available render path for your system.

For supported operating systems and hardware, see Platform Support.

Motion State uses different render paths depending on your system:

  • macOS: Metal GPU acceleration
  • Windows with supported NVIDIA graphics: CUDA GPU acceleration
  • Windows with AMD or Intel graphics: CPU fallback

Motion State does not currently provide Windows GPU acceleration for AMD or Intel graphics. Those systems use CPU fallback.

The CPU renderer lets Motion State run when a supported GPU render path is not available.

Motion State renders beyond the original source raster where needed for overshoot, shadows, glow, feathered crop edges, and sequence-space movement.

That means animated elements can move outside their original clip bounds instead of being prematurely clipped.

Sequence-space rendering applies when the source is smaller than the sequence. Footage that is larger than the sequence on any axis transforms only within its own frame.

The clearest example is a vertical clip in a horizontal sequence: Position moves the shot inside its own tall frame, but the clip cannot be moved across the wider sequence frame.

If you need that movement, scale the footage to fit the sequence first, or use Transfer Motion in the panel to keep native positioning while gaining Motion State’s crop, corners, and stroke. See Troubleshooting.

Motion State is designed so Premiere previews and exports use the same effect controls.

If a preview or export does not look right, check the sequence format, export settings, and whether the same Motion State settings are enabled in the clip.

For troubleshooting steps, see Troubleshooting.