Skip to main content

​
Export

​
Current Editor Support

Motionly currently exposes MP4 export in the top toolbar.
  • Uses the project’s canvas resolution and FPS
  • Shows export progress in the toolbar
  • Downloads a file named after the current .motion project
  • Reports local server, FFmpeg, browser decoder, or asset failures clearly
The current path evaluates each project frame in the browser, synchronizes seekable animated assets, uploads JPEG frames to the local Motionly server, and uses FFmpeg for H.264/AAC output. Project audio defined with an audio block is mixed at its persisted timeline offset. Audio embedded in video clips remains muted; use the project audio track when sound must export. Video, Lottie, and supported GIF assets seek before each captured frame. Animated SVG and GIF fallback use real-time runtimes, so Motionly restarts them and captures in real time while displaying an explicit editor warning about seeking and CSS-animation limitations. WebM and GIF code exists internally but is not a supported editor workflow yet.

​
Near-Term Work

  • Visual 24, 30, and 60 FPS choices
  • Resolution and aspect-ratio presets
  • 720p, 1080p, 1440p, and 4K output choices
  • Clear cancellation and failure handling
  • WebM, GIF, PNG stills, and image-sequence export

​
Export Rules

  • Render from the same scene graph and animated-asset synchronizer as preview
  • Never mutate the source scene or loaded assets
  • Make output settings explicit
  • Report unsupported browsers and failures clearly
  • Prefer reliable output over a large format list