Choose a composition range and delivery format, understand native versus Flowgen Render paths, preserve portable projects, and inspect the generated file.
Where: Native Video Editor → Export; or connect Editable Composition to Flowgen Video Render.
Key ideas
- Editor export and Render node are related paths: The editor exports the open composition directly. Flowgen Video Render accepts an editable native composition and adds an explicit Browser/Electron/Cloud target for flow delivery and reusable output.
- Composition finishing travels with the document: Caption layers and motion blur belong to the native composition and follow every target. Native-composition renders intentionally do not offer conflicting encoder-side caption or motion-blur overrides.
- Portable JSON is editable state, not video: Portable composition/project JSON preserves native structure for reopen/import. MP4/WebM are encoded playback; PNG sequence is zipped still frames.
Steps
- Set and play the work area if only a bounded range should be delivered; otherwise confirm the full composition duration.
- Open Export and choose MP4 video, WebM video, PNG image sequence, or Portable JSON.
- Choose Full composition or Work area and start Export file.
- For a native video through Flowgen, connect composition_out to Video Render composition_in. Choose Browser, Electron, or Cloud only when that runtime is available.
- Set output format, quality, FPS, and source/preset/custom resolution on the Render node. Use scrub optimization only when the downstream use requires frequent seeking.
- Edit native caption layers and motion-blur settings in Video Editor; clear incompatible legacy export overrides when the Render card offers that repair.
- Wait for encoding to complete. Keep the browser tab/desktop/cloud job available according to the chosen target.
- Open the post-export review, confirm filename, frame count, duration, FPS, image orientation, precomps, effects, audio, captions, and motion.
- Use Download again if the browser result must be saved another time, or reopen portable JSON to verify editability.
Direct editor formats
- MP4 video
- WebM video
- PNG image sequence (zip)
- Portable JSON
- Full composition or Work area
Render targets
- Browser — always available for supported native compositions
- Electron — requires the f0 desktop app/native local compositor
- Cloud — requires configured authenticated render worker
- Persisted target is not silently changed when its runtime is unavailable
Flowgen native render settings
- MP4 (H.264) or WebM (VP9)
- 24, 25, 30, 50, or 60 FPS from the shared card/sidebar UI
- Source, 480p, 720p, 1080p, 1440p, 4K, or Custom resolution
- Estimated output dimensions/size
- Include audio and gain where supported
- Scrub optimization; native captions/motion blur remain composition-owned
Tips
- Use Work area for review exports and Full composition for final delivery.
- Save portable JSON before risky interchange or large revisions, and keep project backups separate from encoded outputs.
Limitations and important notes
- Electron and Cloud are disabled when their runtime/configuration is absent.
- PNG sequence and portable JSON are not playable video files.
- Browser file saving and long exports depend on browser capabilities and available storage.
- Native compositor targets intentionally ignore incompatible legacy encoder overrides.
Troubleshooting
Electron or Cloud is disabled.
Use Browser or open the desktop app/configure the authenticated cloud renderer; the saved target is not silently substituted.
The rendered file differs from the canvas.
Confirm the selected composition/range/target and inspect precomps, source relinks, font embedding, effect support, and native caption/motion-blur settings.
An old Render node shows incompatible overrides.
Use Clear incompatible export overrides and author those finishing choices in Video Editor.