Quick start
Projects, library and saved work
Know what a project, library item, preset, download and published version preserve.
Use your dashboard to return to account work and your library to find the content available to you. A project, a saved sound and a purchase can be related without being the same item.
Return to modules you liked
General settings includes Saved modules from your library favorites and Voted modules you have supported. Use these lists to return to a tool you want to play or explore. Saving a module as a favorite keeps a reference to it; it does not create an editable copy or purchase a release.
To build on an idea, open the module and follow Presets, remixes and sharing. Use Following to return to creators whose work interests you.
Know what you are saving
| Item | What it preserves |
|---|---|
| Project | Editable source, configuration or content in its editor |
| Revision | An identifiable saved state of that work |
| Preset | Settings for a particular instrument or effect, sometimes with referenced assets |
| Bank | Recordings and the mappings needed to play them |
| Rack | A composition of modules and their connections |
| Download | Files you can use outside the current workflow |
| Published release | A version prepared for other people, with its own visibility and supported destinations |
Saving settings alone may not preserve every recording or dependency. Keep the associated assets when exporting, and reopen the result to check that it is complete.
Hosted work and local folders
Web Studio works with hosted project data. Local tools work with folders on your computer. Signing in connects account services; it does not automatically synchronize every local file with Studio.
Use the supported project transfer or publication workflow when moving between them. Desktop tools and helpers explains the different local components.
Generated sounds and purchases
Generation results appear where the workflow saves them. A tool that returns a file may need a separate import; an in-platform generation flow may save a library take. See generation in your products.
For acquired products, use purchases and downloads. A purchase record, a downloaded installer and an installed plugin each answer a different question.
If you cannot find your work
Confirm that you are signed in to the account you used. Check Studio for an editable project, your library for collected content and downloads, or the original folder for local work. A downloaded bank or installer will not necessarily appear as a Studio project.
In Studio’s Creations catalog, open Archive history to check whether the item was archived. Archived items currently show Reopen unavailable; there is no restore button.
If it is still missing, contact support with the project or product name, any page link you kept and where you last worked on it. Do not include passwords or tokens.
Recover an earlier module version
Open the module’s Versions tab and select a saved revision. Choose Restore r… as a new revision to make that version current. This keeps the later saved revisions too. It cannot recover unsaved edits or work removed by Delete my creator data.
Keep a copy
For a module with saved files, open Share → Export and choose Download ZIP beside Source ZIP. Check the revision number shown there, and save any edits you want to include before downloading. Keep local project folders and downloaded content separately.
There is no whole-account export button. For a personal-data export request, use the contact details in the Privacy Policy.
Share deliberately
Before sharing, identify whether the recipient gets a listening example, an editable project or downloadable content. Content rights and visibility covers that choice. Keep an editable copy before publishing or replacing a release.