JSON Blob

Share JSON with a link — no upload, no account

JSON Blob turns any JSON document into a link you can paste into Slack, Teams, an email, a pull request, or a support ticket. Whoever opens it sees exactly the JSON you shared, formatted and ready to read, with a tree view for exploring large payloads. There is no sign-up, no save button, and no expiry date to worry about.

What makes it different from a paste service is where the JSON lives. Paste services store your document in their database and hand you an ID that points at it. Here, the link itself holds the document, compressed, so there is no database at all — nothing to breach, nothing to delete later, and no third party keeping a copy.

How the link stores your JSON

When you type or paste, the JSON is compressed with DEFLATE — the algorithm inside ZIP and gzip — and encoded as URL-safe Base64. The result goes after the # in the link, in the part of a URL called the fragment. Browsers never include the fragment in the requests they send, so when someone opens a JSON Blob link, our server only ever sees a request for the /json-blob page. The page then reads the fragment in the visitor's browser and unpacks the JSON there.

Compression matters because JSON is repetitive: the same keys, quotes, and braces appear on every record. A typical config or API response shrinks to between a fifth and a third of its size, which is what lets realistic payloads fit in a link. Press Minify before sharing to strip indentation and make the link a little shorter still.

How long can a JSON link be?

Browsers accept very long links, but the places you paste them don't always. The tool shows the link's length as you type and tells you how far it will travel:

• Up to about 2,000 characters — safe to paste anywhere, including SMS and old email clients.
• Up to about 8,000 characters — fine in browsers and in most chat and email apps.
• Up to about 64,000 characters — browsers open it, but some chat and email apps cut long links, so open it once from where you paste it.
• Beyond that — likely to be cut off. Download the JSON and send the file, or trim what you share.

Who can see a shared blob?

Anyone who has the link can read the JSON, because the link is the JSON. Treat it the way you would treat the document itself: fine for configs, examples, and bug reports; not for API keys, passwords, or personal data. Remember that the app you paste the link into keeps the message, link included.

No one else can find it. Nothing is stored on a server, listed, or indexed by search engines, and when a shared link is opened the page removes the data from the address bar before any analytics script loads, so the JSON isn't recorded in page-view data either. A reload of the same tab still shows the document; use Copy link to share it onward.

What people share with JSON Blob

Anywhere a JSON payload needs to reach another person intact:

• Bug reports — attach the exact API response or request body that triggers the problem.
• Code review — link the example payload a change is meant to handle, instead of pasting a wall of text into a comment.
• Support tickets — send a customer's configuration to a colleague without emailing a file.
• Broken JSON — the link carries invalid JSON exactly as typed, so someone can help fix it, or open it straight in the JSON repair tool.
• Teaching and docs — link a runnable example that opens formatted, rather than a screenshot.

Opening, editing, and comparing shared JSON

A shared link opens in the editor with a note that it came from a link. Switch to Tree to fold the document open level by level, or edit it and copy a new link — every version gets its own link, and the original keeps showing the original. To see exactly what changed between two versions someone sent you, paste both into the JSON diff checker.

For a document you only need to read, the JSON viewer adds search and a table view, and the JSON formatter validates and pretty-prints JSON before you share it.