JSON Workspace: Save JSON Snippets Locally

A private JSON scratchpad that saves named snippets in this browser with IndexedDB. Nothing is uploaded.

Saved snippets

A JSON workspace that lives in your browser

The JSON Workspace is a small local notebook for JSON. Give a snippet a name, paste the JSON, press Save locally, and it appears as a button in the Saved snippets list. Click that button any time later, on the same browser, to load the name and the JSON back into the editor. There is no account and no server: snippets are written to an IndexedDB database called neatjson-workspace that belongs to this site inside your browser profile.

It is built for the JSON you keep re-pasting while you work: a known-good API response to compare against, a request body you send from curl every morning, a feature-flag config you are tweaking, or a fixture you are about to turn into a unit test.

How to use the workspace

  1. Type a descriptive name in Snippet name. If you leave it empty the snippet is saved as Untitled JSON.
  2. Paste or type JSON into the JSON box.
  3. Press Save locally. The text is parsed first; if it is not valid JSON the parser error is shown and nothing is stored.
  4. To reopen a snippet, click its name in Saved snippets. Both fields are filled with the stored copy.
  5. Press New snippet to empty both fields and start another one. This only clears the editor; it does not delete anything you saved.

What gets stored, exactly

Each save adds one record to the snippets object store with four fields: an auto-incremented id, the name, the json text, and a created timestamp in milliseconds. The JSON is stored as the exact text you typed, not a re-serialized copy, so your indentation, key order and number formatting are kept. Validation only checks that the text parses.

Saving never overwrites. If you load orders v1, edit it and press Save again, you get a second entry, which makes the list a simple version history. Give each version a distinct name (for example append a date or v2) so the buttons stay easy to tell apart.

Worked examples

1. Keep a baseline API response

Name the snippet GET /orders?status=paid (staging, 2026-10-10) and paste the response body:

{
  "page": 1,
  "total": 2,
  "orders": [
    { "id": "o-1", "status": "paid", "amount": 1299 },
    { "id": "o-2", "status": "paid", "amount": 450 }
  ]
}

After the next deploy, load this baseline and paste it next to the new response in the JSON diff checker to see which fields changed.

2. A rejected save

A trailing comma is the most common reason a save fails:

{ "feature": "dark-mode", "enabled": true, }

In Chrome the message reads Expected double-quoted property name in JSON at position 43 (Firefox and Safari word it differently). Remove the comma, or paste the text into the JSON formatter and use its repair option, then save again.

3. Export every snippet as a backup

The page has no export button, but the data is ordinary IndexedDB. Open the browser console on this page and run:

const req = indexedDB.open('neatjson-workspace', 1);
req.onsuccess = () => {
  const all = req.result.transaction('snippets')
    .objectStore('snippets').getAll();
  all.onsuccess = () => console.log(JSON.stringify(all.result, null, 2));
};

The output is an array of { "id", "name", "json", "created" } records you can copy into a file or a repository. To remove one snippet, run req.result.transaction('snippets', 'readwrite').objectStore('snippets').delete(3) with its id.

Storage limits and things to watch

When to use another tool instead

The workspace is for keeping JSON, not for transforming it. To edit a document with a tree view and live validation, use the online JSON editor. To compare two saved versions, use the JSON diff checker. To shrink a snippet before you store it, run it through the JSON minifier, and to pull a single value out of a saved response, try the JSONPath tester. For a snippet you need on every device, a Git repository or a gist is the right home.

Frequently asked questions

Where are my JSON snippets saved?

In your browser's IndexedDB storage for neatjson.com, in a database named neatjson-workspace. They never leave the device and are not sent to any server.

Why do I see the same snippet name twice?

Every press of Save locally adds a new record; it never overwrites an existing one. Loading a snippet, editing it and saving again creates a second entry with the same name unless you change the name.

How do I delete a saved snippet?

The page has no delete button. Remove a single record from the browser console with the IndexedDB delete call shown above, or clear this site's storage in your browser settings to remove all of them at once.

Can I open my workspace on another computer?

No. Storage is local to one browser profile and is not synchronized. Export the snippets with the console snippet and copy the result to the other machine, or keep shared fixtures in a repository.

Does saving change my formatting?

No. The JSON is checked with a parser but stored exactly as typed, so indentation, key order and number formatting are preserved.