Current product boundaries
Known limitations
These are explicit product constraints, not promises hidden behind a successful-looking button. The editor performs readiness checks before export and surfaces missing media or storage failures.
Alpha stability
Save browser recovery snapshots and download .fivo copies during important work. UI and project capabilities may continue to change.
Tested export envelope
The documented profile is 1920x1080 or 1080x1920 at 15, 24, or 30 fps. Projects over two minutes and 60 fps exports can proceed after warnings, but have received less testing and may be unstable on some devices.
Browser support
MP4 export requires WebCodecs and a compatible H.264 encoder. Saving a .fivo project remains available when export is unsupported.
Media portability
.fivo files contain editing data and code, not original footage. Media must be retained separately and relinked on another browser or device.
Preview performance
Smoothness depends on the CPU/GPU, source codecs, resolution, layer count, preview quality, and custom-code workload. Export uses a separate offline path.
Custom code execution
Code runs in restricted, time-limited workers. DOM, network, storage, timers, and module imports are unavailable. Expensive drawing may be stopped.
Mobile editing
Mobile editing is in alpha. Basic editing and project saving are available, but real-device coverage is still expanding.
Local browser storage
Autosave, recovery history, preferences, and personal presets are browser-local and subject to browser storage limits or clearing. Storage failures are surfaced.
AI features need your own key
The built-in assistant, music and sound-effect sourcing, image requests, and script/subtitle attachments run against an AI provider you configure in Settings (Google, Groq, xAI, Agnes, or any OpenAI-compatible endpoint). Without a key these features stay disabled; nothing is sent anywhere until you enable them. Sound effects come from Freesound and require a server-side API key — without it the SFX store shows a clear notice instead of failing silently.
3D graphics envelope
Three.js layers render in a sandboxed WebGL worker: no module imports, custom renderers, DOM, or network access. Models must be local .glb/.gltf files attached in the studio (external URLs are blocked). Heavy scenes lower preview FPS; export quality follows the same tested profile as 2D.