System requirements
The app runs in the browser, with nothing to install.
Browser
Use a recent version of a major browser: Chrome, Edge, Firefox, or Safari. Keeping your browser up to date gives you the best performance and the full feature set.
Some features rely on newer browser capabilities and work best, or only, in a Chromium-based browser, such as Chrome or Edge:
| Feature | Chromium (Chrome, Edge) | Firefox, Safari |
|---|---|---|
| Core editor, chat, image and video generation | Full support | Full support |
| Connecting a local folder for storage | Supported | Not available, this uses the File System Access capability, which these browsers don't implement |
| Video export | Fast, hardware-accelerated encoding where available | Falls back to a slower in-browser path, export still completes |
Hardware
Any modern computer runs the app. Large video projects and heavy scenes with many frames or objects benefit from more memory and a faster machine, video encoding in particular is CPU and memory intensive since it all happens on your device.
Screen size
The editor is a canvas-and-panels layout designed for a desktop-sized screen. It's usable on a tablet, but a small phone screen makes precise object placement and the multi-panel layout cramped, the workspace side, browsing and managing your projects, adapts to a narrow screen far better than the editor's canvas does.
Browser extensions
Ad blockers and privacy extensions occasionally interfere with AI requests or media loading if they block a request the app makes to your provider or to stock media search. If something that should work silently fails, that's worth checking before assuming the app itself is broken.
Storage on your device
Beyond an optional connected local folder, the browser itself keeps a small amount of local state for you, your most recent autosave history and any in-progress work before you sign in. Clearing your browser's site data for the app removes this, so avoid doing that while something unsaved matters.
Account and network
- You need an account to save your work to the cloud and to use AI. See Sign up and sign in.
- AI features call your provider over the network, using your own key, so a working connection to that provider's API is required whenever you chat or generate. See Bring your own AI key.
- Working offline without an account is possible for a single session, but nothing is saved beyond that browser's local storage. See Where your work lives.
When in doubt, use Chrome or Edge
If a feature seems to be missing, check whether it's one of the Chromium-only ones above before assuming something is broken.
How to use it: checking your own setup
- Confirm your browser is Chrome, Edge, Firefox, or Safari, and update it if you're not sure it's recent, an outdated browser is the most common cause of a feature behaving oddly.
- If you plan to connect a local folder for storage, or want the fastest video export, switch to Chrome or Edge specifically, Firefox and Safari cannot offer either.
- Before a long editing session with heavy video or a large scene, close other demanding browser tabs and apps, encoding and large-canvas work both lean on your device's own memory and CPU since everything runs locally.
- If AI generation or stock media search fails silently, temporarily disable ad blockers or privacy extensions for the app's domain and try again, before assuming the app itself is broken.
Common tasks
Work on a small screen without fighting the editor. Use the workspace side, browsing, organizing, and reviewing your projects, on a phone or small tablet, and switch to a laptop or desktop for actual canvas editing, the editor's multi-panel layout needs the room.
Diagnose a feature that "isn't there." Check this page's Chromium-versus-Firefox/Safari table first, a missing local-folder option or a slow video export is very often just the browser you're using, not a bug.
Recover unsaved work after closing a tab by accident, before you'd signed in. Reopen the app in the same browser, the same profile, without clearing site data in between, your most recent autosave history for that session is kept in that browser's own local storage.
Troubleshooting
- The local folder option never appears. It depends on the File System Access capability, present only in Chromium-based browsers. Firefox and Safari cannot offer it no matter how recent the version.
- Video export is much slower than expected. Without hardware-accelerated encoding available, which depends on both your browser and your device, export falls back to a slower in-browser path. It still completes, just not as quickly, a Chromium browser on capable hardware gives you the fast path.
- AI requests or stock image search silently fail. An ad blocker or privacy extension may be blocking the request before it leaves your browser. Test with extensions disabled for the app's domain to confirm.
- Local state disappeared after clearing browser data. Clearing your browser's site data for the app removes its locally kept autosave history and any pre-sign-in work, this is expected behavior, not a bug, avoid clearing site data while something unsaved matters.