Comparison
superjsonblob vs jsonblob
Both store JSON behind a URL. jsonblob.com has been the default for that since 2013 and we built superjsonblob a decade later, so naturally we layer extra things on top. Here's what is genuinely different — verified, no spin.
| Aspect | jsonblob.com | superjsonblob |
|---|---|---|
| Storage model | Single mutable blob per ID | Append-only versions; latest served at the same URL |
| API endpoints | POST / GET / PUT / DELETE /api/jsonBlob/{id} | Same four endpoints, identical request/response shapes |
| Version history | No | Every PUT recorded; history page per blob |
| Diff between versions | No | Semantic JSON diff (jsondiffpatch); side-by-side or unified |
| Named blobs | No (anonymous IDs only) | Yes for signed-in owners |
| Visibility | Public-by-URL only | Public-by-URL or private to owner |
| Accounts | None | Optional Firebase Auth (email/password + Google) |
| Editor | Plain textarea | Monaco + collapsible JSON tree side-by-side |
| Self-hosting | Apache-2.0 source on GitHub; bring your own infra | Docker image; Postgres-backed |
| Backend stack | Kotlin / Micronaut | Next.js / Node / Postgres |
| Last public release activity | See github.com/tburch/jsonblob commits | See this repository |
| License | Apache-2.0 | See repository LICENSE |
| Cost | Free | Free |
Last verified 2026-05-05. jsonblob.com data sourced from the public site and github.com/tburch/jsonblob.
When jsonblob is the right choice
jsonblob is the simpler, smaller dependency. If your blob never needs revision, you don't want an account, and you'd rather not introduce a new service to your stack, jsonblob is fine — it's been quietly running for over a decade.
The Apache-2.0 source is also a real advantage if you need to self-host on infra you already operate without setting up Postgres.
When superjsonblob is the right choice
Pick superjsonblob if your blob will be edited more than once and you ever want to know what changed. Mock-API fixtures, configuration payloads, sample requests for support tickets, and shared debug data all benefit from versioning. The semantic diff between any two versions is the real win.
Migration is one line
curl -X POST https://superjsonblob.com/api/jsonBlob \
-H 'content-type: application/json' \
-d '{"hello":"world"}'The response is a 201 with a Location header pointing at /api/jsonBlob/{id}. Same as jsonblob. See the full API reference.
superjsonblob is an independent project and is not affiliated with, sponsored by, or endorsed by jsonblob.com or its operator.