This needs the hosted vfrey service, which is not live yet. Everything on this page describes how it will work. Nothing here changes how vfrey works on your machine: local projects, rendering, and the dashboard stay free and need no account.
The console has an editor for the scenes in a cloud project. Open a project, then a scene, then Edit.

​
What you get

  • A file tree of the scene’s folder, and a code editor for HTML, CSS, JavaScript, JSON, and SVG files (up to 1 MB each). You can add new files.
  • A live preview that plays the scene. It shows your unsaved text too.
  • It is for HTML scenes. A Remotion scene shows a note instead.
A member, admin, or owner can save. A reviewer sees the scene read-only.

​
Saving and conflicts

Saving goes through the same checks as cloud push: allowed paths, size limits, and your storage quota. The editor remembers which version it opened. If the scene changed in the cloud since then, the save is refused and you can reload, see a line diff, or keep your version. Two people saving at once: one wins and the other is told. Run npx vfrey cloud pull to bring the saved files down to your machine.

​
The preview is sandboxed

The preview runs inside a locked frame with no cookies, no way to reach your account, and no outside network. It can load only the scene’s own files. Its address carries a signed token that expires after 4 hours, and your access is checked on every request.

​
Timing

The preview uses the scene’s real timing when a push carried it from a run. If not, it estimates the timing from the project’s script.

​
On your own machine

The same kind of editor ships with vfrey for local work. npx vfrey scene studio DIR opens a scene in the visual editor on your machine and saves edits back into the folder. See Scenes.