Saving and sharing
Capture stills and recordings, navigate version history, and publish public embeds.
A running sketch is a regular node, but it's also something you'll want to capture, ship, and revisit. This page covers three exits: saving the canvas as a Photo or Video asset, navigating prior versions of a sketch, and publishing the current sketch to a public /embed/cc/:id URL.
Saving the canvas
Click Save on the Creative Code node
The save asset modal opens with two paths.
Choose Photo or Video
- Photo — captures the current frame as a PNG. Fast, no waiting; the image arrives as a regular Image node connected downstream.
- Video — records the canvas as MP4 for up to two minutes. Recording runs in the background, so it doesn't tie up the canvas or the rest of your flow. The result arrives as a regular Video node downstream.
Both paths upload the captured asset to your media storage and emit a downstream node automatically — no manual reconnecting. From there, the asset is just like any other media in Fuser: you can pipe it into a compositor, share it from the project, or use it as input for another sketch.
Keyboard shortcuts
⌘/Ctrl+Shift+S— capture the current frame as a Photo without opening the modal.⌘/Ctrl+Shift+R— toggle Video recording. Press once to start, again to stop and save.
Version history
Every generation Fuser produces — every time you submit a prompt and the model writes — saves a snapshot of the sketch automatically. Clicking Save explicitly creates a named checkpoint alongside the auto-saves, marked as a user save in the chat panel.
You navigate prior versions from the chat panel — see Prompting and chat → Chat history and checkpoints. Click any prior generation or checkpoint and the editor and canvas jump back to that version. Prompting from a prior version drops the later ones (after a confirmation prompt), so jump back deliberately.
This is your safety net both ways: undo a bad prompt by jumping back, and pin a working version by saving it explicitly so it stands out in the chat panel.
Publishing to a public embed
The Publish button takes the current sketch — code, parameters, attachments, library — and pins it to a public URL of the form /embed/cc/:id. Anyone with the URL can view the sketch in a standalone page or drop it in an iframe.
Publishing pins the current version. The published URL points to the exact state of the sketch at the moment you published — later edits don't affect what visitors see. To update what's public, hit Publish again from a newer version; the URL stays the same, but the content updates.
The publish flow has three states:
- Unpublished — no public URL exists yet.
- Update — a public version exists, but the current sketch differs from it. Click to push the current version live.
- Done — the public URL matches the current sketch.
Once published, Copied to clipboard confirms when you grab the link.
The public page generates a social preview image from a snapshot of the sketch — what shows up when the link is shared on social or in chat. The iframe headers are intentionally permissive so the embed works on third-party pages.
Public embeds are public
Embeds aren't gated by workspace membership. Anyone with the URL gets in — there's no per-viewer share list, no workspace check. If a sketch contains client work, a private prompt, or anything you don't want loose on the internet, don't publish. Use workspace shares instead — they're gated by who's in the workspace and tied to specific people or teams.
Unpublishing
Unpublishing tears down the public URL. Existing iframes break; the social preview image stops resolving; the standalone page returns a not-found. There's no soft delete — once unpublished, the URL is gone, and re-publishing later may give you a different URL.
If you only want to update what's public, don't unpublish first — just hit Publish again from the newer version. Unpublish when you genuinely want the sketch off the internet.