Workspaces & Sharing
JSONFiddle now treats your work as a workspace: a set of files, queries, layout choices, preferences, and share settings that belong together.
Use workspaces when you want to keep more than one payload open, return to a debugging session later, or share a stable snapshot with another person.
Local-first by default
Guest sessions stay local in your browser. Tabs and editor state are restored from session storage, and your source data is not uploaded simply because you opened the app.
If you are signed in, you can explicitly save a workspace to JSONFiddle cloud storage. Saving is an intentional action because workspace files may contain private API responses, customer payloads, or production logs.
What a workspace can contain
| Item | Included |
|---|---|
| Files | JSON, YAML, XML, CSV, Mermaid, JFDG, and imported files |
| Active tool | Editor, Graph, Explorer, Grid, Query, SQL, or tool page context |
| Queries | Saved SQL queries and query playground expressions |
| Layout | Editor/canvas split, collapsed editor state, and view preferences |
| Theme | App theme, diagram theme, accent, graph node style, and edge style |
| Sharing | Expiring snapshot links created from a saved workspace |
Save a workspace
- Sign in.
- Open the Workspace menu in the top bar.
- Choose Save workspace or Save workspace as.
- Confirm the workspace name.
If the workspace has never been saved, Save workspace opens the Save workspace as dialog first.
Privacy note: Saving uploads the selected workspace content to JSONFiddle cloud storage for your account. Guest sessions remain local.
Open a workspace
Use Workspace > Open workspace to browse saved workspaces. Opening a workspace restores its files, active tab, view state, queries, and preferences.
If you have unsaved local changes, save or export them first. Opening another workspace replaces the active workspace state.
Export a workspace package
Choose Workspace > Export workspace package to download a portable .jsonfiddle-workspace.json file.
This is useful for:
- Backing up a debugging session.
- Sending a workspace through a secure internal channel.
- Moving work between machines without cloud save.
- Preserving a local copy before trying major edits.
Share a secure snapshot
Use Share > Create share snapshot when you want another person to see a stable copy of your current work.
Snapshot sharing is different from copying the page URL:
| Action | What it does |
|---|---|
| Copy editor link | Copies the current editor route, without your data |
| Create share snapshot | Uploads a frozen snapshot and creates an expiring share link |
The snapshot modal asks what to include:
- Current file.
- Full workspace.
- Query plus result.
- Include or exclude source data.
- Expiry: 1 hour, 24 hours, or 7 days.
Security note: A share snapshot is immutable. If you change the original workspace later, the share link does not change.
Manage shared links
Shared links should be treated like short-lived debugging artifacts. Revoke links that are no longer needed, and prefer short expiry windows for production data.
Revoking a workspace share marks the link inactive and clears the stored snapshot content so the revoked link no longer retains source data. Expired snapshots are also eligible for the private retention cleanup job.
Future paid workspaces are expected to include team-level link management, audit history, and role-based workspace access.
Good sharing habits
- Exclude source data when the recipient only needs structure or screenshots.
- Use sample payloads when reporting UI bugs.
- Avoid uploading production secrets, credentials, tokens, or personal data.
- Use exported workspace packages for internal secure channels when cloud sharing is not appropriate.