Sign up and get Pro free for 3 months — no card required.Claim it →
Storage
Every namespace JSONZen stores — in this browser and (where applicable) in your cloud account. Click clear on any card to wipe just that namespace; cloud-synced data stays safe and re-downloads.
How cloud sync works
Quick reference covering every cloud-sync question. Per-card details below repeat these numbers in context.
Who can cloud-sync
Pro plan only. Free users keep everything in this browser (no opt-in switch will turn sync on without an active Pro pass). See /pricing.
What data syncs
Saved snippets only (encrypted blobs). Tool preferences (indent, sort, etc.) never sync — they are deliberately scoped to one browser.
How to sync
Sign in (magic link) and unlock the vault with your passphrase. Cross-device pull happens automatically on /account/snippets. To push a local snippet to the cloud, click the cloud-upload icon on its row and confirm.
Sync trigger
Pull: vault unlock + mount of /account/snippets. Push: explicit per-row click on the Sync icon next to each snippet. Unsync removes only the cloud copy. No background polling.
CLI cloud sync
The jsonzen CLI does not sync anything to the cloud. It has no auth, no network, no vault — it is a pure local pipeline tool. Use the web app on a signed-in Pro account for sync.
Sync limits
Snippets are uncapped in count on Pro; each ciphertext ≤ 2 MiB. Free users save up to 3 locally per browser — the 4th save is blocked. /api/* payloads inherit Vercel's 4.5 MB body limit. There is no per-day quota and no rate-limit beyond the underlying Supabase free-tier baseline.
Shared links
Stateless — the (optionally encrypted) payload lives in the URL fragment, not on a server. JSONZen has no list of links you have created and no way to revoke one. For sensitive payloads use the password-protected variant (Pro): even if the URL leaks, the payload stays unreadable without the 4–8 character password.
How to remove cloud data
Per-snippet from /account/snippets. The lapsed-Pro banner also offers an “Export & delete cloud sync” button that downloads a JSON of every cloud snippet then bulk-deletes them. To nuke everything (snippets + account + billing) in one shot:/account → Delete account. That cascade-deletes every cloud row scoped to your account.
Per-tool defaults the tool's Settings popover writes — indent width, sort behaviour, schema mode, JWT timezone, diff options. Lives in this browser only; never synced anywhere on either tier.
Encrypted blobs from the Save Snippet button on any tool page. The vault meta (salt + wrapped master key) stays in this browser; the ciphertexts also sync to your account on Pro. Server never sees plaintext.
Who can sync
Pro only. Free users can save up to 3 snippets locally per device; nothing is uploaded.
Auto-sync
Manual per snippet (Pro). Cross-device pull is automatic on /account/snippets after vault unlock. Push is opt-in via the cloud icon next to each row; Unsync removes only the cloud copy. Logout drops cloud rows from view without touching your local copy.
Limits
Free: up to 3 snippets per browser — the 4th save is blocked with an Upgrade / Manage prompt. Pro: unlimited count · ciphertext ≤ 2 MiB per snippet (~1.5 MB plaintext).
Each snippet row lives under your account in public.snippets — scoped by RLS to you. Manage / delete individually from /account/snippets, or wipe everything via "Delete account" in /account (cascades through every cloud table).
Wipe ALL cloud data
Want to remove every encrypted blob the server holds for you — snippets, subscriptions, account row, everything? The Delete account action on /account is the single switch. Cascade deletes follow every FK, so no orphan row survives.
You're not signed in, so there's no cloud data scoped to you to remove.