JSON Tools

JSON tools handle the inspection and preparation work that happens before a payload goes into a ticket, a blog post, a log file, or a production code review. Four browser-based utilities: count keys and measure depth before you trust a blob is well-formed, decode Base64 wrappers from API responses, redact secrets and PII before sharing, and render a clean screenshot suitable for documentation. All client-side, all free, all fine with megabyte-sized payloads.
What you can do with JSON tools

Inspect the shape of a JSON document before using it: key count, nesting depth, type distribution, total bytes, and complexity signals with JSON Analyzer.
Decode Base64-wrapped JSON from API responses, JWT payloads, or webhook bodies into a pretty-printed structure: Base64 to JSON Decoder.
Redact passwords, tokens, and PII before sharing a JSON example in a Slack channel or a GitHub issue: JSON Censor & Redactor.
Turn a JSON document into a syntax-highlighted PNG for a blog post, a design doc, or a slide: JSON Screenshot Generator.

Reach for JSON tools when the payload itself is the subject: you need to understand it, hide part of it, or ship it somewhere as a visual. If the job is converting tabular data between JSON and CSV, the CSV tools are closer. For general encoding work (Base64, hex, URL-encoding) that does not end in JSON, the developer category has the low-level converters.
The JSON toolkit

Tool
What it does
When to use

JSON Analyzer
Parses a JSON document and reports depth, key count, type distribution, byte size, largest array, deepest nesting, and complexity warnings.
Auditing an API response before integration, spotting unexpected deep nesting in a webhook payload, or sizing up a 5 MB config dump before deciding how to parse it.

Base64 to JSON Decoder
Decodes a Base64 string, parses the result as JSON, pretty-prints with a chosen indent (2, 4, tab, or minified), and offers key sorting. Handles URL-safe Base64.
Reading a JWT payload after splitting on dots, inspecting a webhook body that wrapped JSON in Base64, or decoding the config blob from an environment variable.

JSON Censor & Redactor
Replaces values for sensitive keys (password, token, secret, email, etc.) with [REDACTED], asterisks, or custom text. Supports whole-word and key-name matching.
Sanitizing a JSON sample before pasting into a GitHub issue, scrubbing PII from a customer support log, or preparing a training example that cannot include the real auth header.

JSON Screenshot Generator
Renders pretty-printed JSON as a syntax-highlighted PNG with dark or light theme, configurable width and font size.
Embedding a JSON example in a blog post where code blocks look plain, preparing a slide for a tech talk, or generating a thumbnail for API documentation.

How to choose the right JSON tool

If you have a raw Base64 blob and do not know whether it is JSON, start with Base64 to JSON Decoder. If parsing fails, the blob is not JSON (it might be a PDF, an image, or some binary format). In that case, try a generic Base64 decoder in the developer category.
If the document is clearly JSON and you want to understand its shape before processing, run JSON Analyzer first. A 50 KB response with depth 12 and 2,000 keys needs different handling than a 50 KB response with depth 3 and 80 keys.
If you are about to paste JSON publicly (GitHub issue, Stack Overflow, blog post), run Censor JSON first. The default redact list catches the common sensitive keys but you can add custom ones for your own schema.
If the destination is a visual (slide, blog image, doc thumbnail), go directly to JSON Screenshot Generator. It produces a PNG that is readable at thumbnail size and legible at full size.

Frequently asked questions
Q: Can these tools handle large JSON files?
Yes, up to what the browser can hold in memory. A 20 MB payload analyzes in a few seconds on a modern laptop. Past about 50 MB, browser responsiveness drops; for very large datasets, a local tool like jq or a Python script is faster.
Q: Will censor-json catch every sensitive field in my payload?
It catches the common ones (password, token, api_key, secret, access_token, authorization, email, ssn, and similar) by key name. If your schema uses custom key names like clientSecret or internal_code, add them to the custom-redact list before processing. Visual review afterward is still recommended for high-stakes redaction.
Q: What is the difference between JSON Analyzer and just opening the file?
JSON Analyzer gives you quantitative signals: depth, key count, type mix, complexity warnings. Opening the file shows you the content. Use the analyzer when you are dealing with an unfamiliar payload and want to know what to expect before you scroll through it.
Q: Does the screenshot generator support syntax highlighting themes?
Yes. Dark mode (default) and light mode, both with standard JSON token colors (strings, numbers, keys, booleans, null). Font size and canvas width are configurable. Output is PNG at 1x display resolution.
Q: Are my JSON payloads uploaded anywhere?
No. All four tools process JSON entirely client-side. Nothing is sent over the network. Safe to paste production API responses, JWT payloads, or webhook bodies. The browser network tab confirms zero requests during analysis, decoding, or rendering.
Related categories
JSON work often pairs with adjacent toolkits. The developer category covers hashing, encoding, and decoding utilities (HMAC, SHA, URL encoding, hex dumping) that sit upstream or downstream of JSON processing. The CSV tools handle tabular data when your JSON is effectively a flat array of records. For cleaning up whitespace, line endings, or character encoding in JSON strings that arrive messy, the text category has the right formatting tools.