Help Centre

Last updated: August 26, 2026

Getting started

Jsonreveal is a JSON diagnostic tool with two modes:

Paste JSON — paste any JSON blob into the text area and click "Parse JSON". The tool parses it in your browser using the standard JSON.parse() function. If parsing fails, you see the exact line and column where the error occurred and what character was expected there. If parsing succeeds, you see a confirmation that the JSON is valid. Your pasted content never leaves your browser.
Fetch URL — enter a URL and click "Fetch". The tool fetches the URL server-side and reports the HTTP status code, the response content-type, whether the body is valid JSON, and — if the body is JSON — a pretty-printed preview. It also flags common red flags: a JSON error object returned with a 200 status, or an HTML response labelled as JSON.

No account, no sign-up, no email required. Everything in the Free tier works today.

Frequently Asked Questions

1. What does "Unexpected token at position 4471" actually mean?

This is the default JavaScript error message, and it is frustratingly vague — it tells you the byte offset but not what was expected or where that offset falls in terms of lines. Jsonreveal translates this into a line-and-column location and gives you the token the parser was expecting (for example: expected ',' or '}' at line 47, column 12). It also shows the surrounding context so you can see what the JSON looked like at the failure point. Try pasting your JSON into the tool to see the difference.

2. My fetch says "Could not reach host" — is the tool broken?

The most common cause is that the API you are trying to reach is hosted behind Cloudflare. Cloudflare blocks requests from Cloudflare Workers (which Jsonreveal uses for server-side fetches). The tool warns about this next to the URL input. If the host is not behind Cloudflare, the fetch failure could be a DNS issue, a network timeout, or the server rejecting the connection. Try pasting a sample JSON response from the API's documentation into the Paste JSON tab instead.

3. Is my pasted JSON sent to your server?

No. When you use the Paste JSON tab, the JSON is parsed entirely in your own browser using JavaScript's built-in JSON.parse(). The text you paste never traverses the network. This is stated on the tool page and in the privacy policy. The Fetch URL tab does send the URL you type to the server, so the server can make the outbound request on your behalf, but the URL and response are not logged or stored.

4. The API returned 200 OK but the body makes no sense — why?

A surprisingly common pattern: an API returns a 200 status code but the body is an HTML error page, a login redirect page, or a plain-text error message with a Content-Type: application/json header. Jsonreveal's Fetch URL mode helps here by showing you the actual content-type, the raw body preview, and whether the body is valid JSON at all. If the body is JSON but contains an error or errors field alongside a 200 status, the tool flags it as a potential error-masked-as-success.

5. Is there a size limit on what I can paste or fetch?

Paste JSON: The Free tier processes pasted content up to 50 KB. (This is a client-side limit — the tool runs in your browser's memory.) Pro will raise this to 5 MB when the feature is built.

Fetch URL: The server reads up to 50 KB of the response body to avoid memory issues with large responses. The body preview shown in the results is capped at 1,000 characters. If the response is larger, only the first 50 KB are available for analysis.

6. How do I get the Pro plan? What features are planned?

The Pro tier is listed at $9/month on the pricing page, but no payment processor is connected yet. The checkout form on the site is a demonstration — no money moves through it, no subscription is created, and no user currently has a paid plan. When a payment processor is connected (a future step), subscribing will become available.

The following Pro features are planned but not yet built:

Larger payload limit (5 MB)
JSON schema validation against a user-supplied schema
Multi-endpoint response comparison
Export results as JSON or Markdown
Saved analysis history (requires accounts)

Until these are built and a payment processor is connected, all features, including those listed as Pro, are available at no cost on a best-effort basis.

Known limitations

Honesty over hype. These are genuine gaps in the current product. We list them because a tool that pretends to do everything is less useful than one that says what it cannot do.

Cloudflare-hosted APIs are unreachable. Jsonreveal runs on Cloudflare Workers, and Workers cannot reach other Cloudflare-fronted hosts. If the API you are debugging uses Cloudflare, the fetch will always fail with a connection error. Use the Paste JSON tab instead with a saved sample response.
No user accounts. There is no way to log in, save analysis history, bookmark results, or associate data with a profile. Every visit is a fresh session.
No email, alerts, or notifications. The tool cannot send you emails, digests, reminders, or scheduled re-checks. There is no email sender configured anywhere in the fleet.
No payment processor connected. The Pro checkout is a demo. No real money is accepted, no subscriptions exist, and no billing relationship is formed when the demo form is submitted.
No legal entity registered. The service is operated without a registered company, address, or governing jurisdiction. The terms of service and privacy policy note this explicitly.
Planned features are not yet built. Items on the pricing page marked "Planned" — including JSON schema validation, multi-endpoint comparison, export, and analysis history — do not exist yet and should not be relied upon.

Contact us

A customer support email address or other contact mechanism has not yet been established for this service. The owner has not supplied a way to reach them.

If you have found a bug, have a feature request, or need help that the FAQ above does not address, please note this gap — the operator is aware that a contact method is needed.

Note to the operator: This page names no email address because there is no mailbox configured on any domain in this fleet. A support page that lists an unreachable address is worse than one that honestly states contact has not been set up. Please supply a contact method and update this page.