Code-Driven Motion Modules for SVGator PresetsCode-Driven Motion Modules for SVGator Presets
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Motion Modules for SVGator: a preset can be code:
What if a SVGator preset could be code?
Motion Modules: SVGator owns the timeline, a module owns the physics inside one layer. Keyframe its parameters like any property, and it renders as a pure function of the playhead, so scrubbing, looping and export keep working.
01 Bake. The module runs once and writes ordinary SVGator keyframes. Proof: HALO Water, 1,521 keyframes written by a solver and pushed into SVGator through the MCP, plus three physics logo presets: Gather, Heartbeat, Radiant.
02 Live. A real SVGator export with one empty slot layer. The HALO engine draws 1,500 strokes inside it, synced only through the public Player API. Deterministic: scrub backwards and every stroke lands exactly where it was.
Every keyframe was built through the SVGator MCP. None set by hand.
Serhii's avatar
SVGator baked HALO animation from "Motion Modules Engine": https://app.svgator.com/editor#/9433b477be314d278c40a34f2f9fa39b
Timothy's avatar
SVGator owns the timeline, a module owns the physics is an elegant architecture, Serhii. Baking 1,521 keyframes from a solver straight into ordinary SVGator keyframes through the MCP is the kind of thing that makes motion designers' eyes widen. Deterministic scrubbing with 1,500 strokes is seriously impressive.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started