Your work stays in your browser.

ParamRig does not send a project to a ParamRig server. The application has no account and no cloud workspace today.

What the browser stores

Draft parameter values, snapshots and interface preferences use browser storage. Imported local resources may use IndexedDB. History, selection, track visibility and the keyframe clipboard are session state and go when the tab does.

Browser storage is specific to the browser profile and site origin. Clearing site data, using private browsing or changing devices can remove or isolate it.

Keep a portable copy

Use Export in a rig to copy or download the current values as JSON. That file records the parameter state. It is not a patch, and nothing applies it to your source for you.

Remove local data

Use the reset actions provided in the workbench or clear the site data for app.paramrig.com in your browser. This cannot remove files you previously downloaded.

Library metadata and optional modules

The library uses a lightweight index of titles, identifiers and domains. Documents remain the source of truth. The index is reconstructed when missing or corrupt, without regenerating Sound Labs patches or rewriting saved documents. It follows successful saves and changes from other tabs; a failed index write does not cancel a successful document save.

Thumbnails have a separate cache. Opening the library does not render sounds or initialize a scene. Full validation runs when a document opens in its domain. If that domain is absent from a selective build, the application identifies the required module and preserves the document.