Wiki · Plugins / OpenFX / Workflow

Autograph OpenFX plugin compatibility note

Published 2026-06-29 · Checked 2026-06-29

This page is a practical compatibility note for artists testing third-party effects in Autograph. It is not a certification list. A product page can show that a plugin family is offered for Autograph, but a real production still needs a small local test with the exact plugin version, license state, GPU, OS, media type, bit depth, color management, and render path.

What is confirmed publicly

• Maxon describes Autograph as a free motion graphics and VFX/compositing application with access to Universe Plugins and Red Giant OFX tools where a license is required.
• Maxon says Autograph supports OpenFX plugins, Shadertoy, multi-channel EXR, Photoshop layers, ProRes, ACES, and OCIO workflows.
• Maxon says Universe and Red Giant OFX tools can be accessed from Autograph's Modifier list or the integrated Maxon Studio plugin page.
• Maxon names RE:Vision Effects, BorisFX, and Digital Anarchy as examples of third-party OpenFX plugin vendors for Autograph.
• RE:Vision Effects publishes Autograph-specific product pages for at least Twixtor and ReelSmart Motion Blur.

How to read "OpenFX support"

OpenFX is a plugin API, not a guarantee that every OFX plugin behaves identically in every host. The useful question is narrower: which plugin version loads, which parameters expose correctly, whether GPU processing and previews behave, whether alpha and high-bit-depth images survive, whether color-managed inputs are handled as expected, and whether renders match the interactive view.

Minimum test before trusting a plugin in Autograph

1. Install the current Autograph build, current Maxon App, and the exact plugin build intended for the job.
2. Confirm the plugin appears in Autograph where expected: Modifier list, Maxon Studio plugin page, or the vendor's documented install path.
3. Test one short clip, one still sequence, one alpha-bearing element, and one high-dynamic-range or EXR element if the job uses them.
4. Check preview and final render against a reference frame from another host when possible, such as After Effects, Nuke, Resolve/Fusion, Flame, or the vendor's known-good host.
5. Record plugin version, Autograph version, OS, GPU driver, project color settings, source format, output format, and any workaround used.

Common failure modes

• A plugin loads but exposes fewer controls than expected.
• Interactive preview and final render do not match.
• Motion-vector, retiming, denoise, or blur tools behave differently on interlaced, variable-frame-rate, or heavily compressed sources.
• Alpha premultiplication, color-management, or HDR values are changed by the handoff rather than by the intended effect.
• A license is valid for one host or package tier but not for the Autograph/OFX build being tested.

Autograph-specific read

Autograph's plugin story is important because the application is positioned as a free host while its higher-end effects ecosystem depends partly on paid Red Giant OFX tools and third-party vendors. That makes compatibility a workflow question, not only a feature-list question. Treat vendor pages as starting points, then validate with the exact shot types and color pipeline used by the project.

Sources checked

• Maxon Autograph product page - OpenFX, Red Giant OFX, Universe, ACES/OCIO, and named third-party plugin vendor claims, checked 2026-06-29.
• RE:Vision Effects Twixtor for Autograph - Autograph-specific Twixtor product page, checked 2026-06-29.
• RE:Vision Effects ReelSmart Motion Blur for Autograph - Autograph-specific RSMB product page, checked 2026-06-29.
• Open Effects Association - OpenFX standard context, checked 2026-06-29.

Back to Wiki