Saving Work and Managing Your Cloud Library
How saves, uploads and storage limits work, and how to organise a library you can actually reuse.
In This Tutorial
What a Save Contains
A save stores the full configuration of a simulation: mode, every physics value, every visual setting, the selected song and the audio setup. It does not store a video. Reloading a save puts the Studio back exactly where you left it, so you can re-record the same setup at a different resolution, in a different aspect ratio, or with one setting changed. That is why saving before experimenting matters: the configuration is the asset, the video is just one render of it.
- •Alt+S saves without leaving the canvas.
- •Save before switching mode. Mode changes rewrite mode-specific settings.
The Cloud Tab
The Cloud tab holds your saves and your uploaded media. Saves sync to your account, so signing in on another device gives you the same library. This is also where you see your storage usage against your plan limit. Usage is the total across everything you have uploaded, including MIDI files, audio tracks, custom bounce sounds and image textures, not just saved configurations.
- •Storage counts uploads, not saves. A large audio library will fill a plan faster than hundreds of configurations.
Local Saves vs Cloud Saves
There are two places a save can live. A local save is stored in this browser on this device: instant, always available, and free, but tied to this machine and lost if you clear your browser data. A cloud save, on a paid plan, is stored against your account and reachable from any device you sign in on, and it survives a cleared browser. Use local saves for fast iteration while you work, and promote anything you want to keep to a cloud save so it is genuinely backed up.
- •Treat a local save as a working draft and a cloud save as the master copy. A local-only setup you care about is one cleared cache away from gone.
Uploaded Media
The Media Library, reachable from the Audio tab under Sound, MIDI and Audio Hub, is where MIDI files, audio tracks and custom sounds are uploaded and listed. Uploads become available in the relevant dropdowns across the Studio: MIDI files appear under MIDI Files (Cloud) in the song selector, custom sounds appear in the sound source pickers, and image textures appear in the ball texture picker. Name files clearly at upload time, because the dropdowns show the filename.
- •Prefix related files with a common name so they group together alphabetically in the dropdowns.
Building a Reusable Base
The most efficient way to work is to keep a small set of base configurations rather than starting fresh each time. Get one Rhythmic setup and one Escape setup looking the way you want, save each with a clear name, and start every new clip by loading one and changing the song or the colours. This keeps your output visually consistent, which helps a channel read as deliberate, and it removes the setup time that otherwise stops you posting regularly.
- •Name saves by what they are for, not what they contain. "Vertical rhythmic base" beats "test7".
Maximize Your Creation Potential
Ready to dive deeper? Check out our guides, pricing options, community showcases, and help center.