Readable JSON is not automatically valid for the job—or safe to share

Syntax validation is the first gate

A JSON parser checks quotes, commas, brackets, and supported value types. It does not know whether a date is possible, an identifier has the right length, or a required business field is missing.

Treat successful parsing as permission to inspect structure, not proof of correctness. Use a schema validator when the receiving system defines a schema.

Formatting and minification preserve meaning only within JSON rules

Indentation and insignificant whitespace can change without changing parsed values. Key order may be preserved by an implementation but should not be used as semantic meaning unless a separate protocol says otherwise.

Numbers can also be a concern. JavaScript represents ordinary JSON numbers with IEEE-754 behavior, so very large integers can lose exactness in downstream processing.

Scrub values, not only familiar labels

A key rule can remove email or token fields when names are predictable. The same value may remain under another key, inside a log message, in a URL, or encoded within a nested string.

After scrubbing, search for the original values and inspect arrays and deeply nested objects. Anonymization requires a broader data-risk analysis than deleting a few properties.

Remember local persistence and clipboard history

The formatter stores current input and preferences in localStorage. On a shared profile, another user can reopen that state until it is cleared.

Copying output may place it in operating-system or clipboard-manager history. Clear the tool, avoid real secrets in demonstrations, and use purpose-built secret handling for credentials.

Define the sharing threat before choosing scrub rules

A useful scrub begins with the recipient and the reason for sharing. Support staff may need an error code and timestamp but not an access token, customer email, internal host name, or full request body. Write down the fields that are required, fields that must be removed, and values that need partial masking. Run the scrubber, then search for both known keys and recognizable sample values. Remember that identifiers can appear inside free text, arrays, encoded strings, or unfamiliar property names. When the stakes are high, create a minimal JSON example by hand instead of sending a reduced production record.

What the browser does

The browser parses the input with JavaScript JSON handling, recursively applies configured key rules, and serializes the result with or without indentation.

Current input and scrub preferences are stored in localStorage for convenience. That persistence is useful on a personal device but inappropriate for confidential data on a shared browser profile.

Inputs and outputs

• Input: one valid JSON value, including an object, array, string, number, boolean, or null.
• Output: formatted, minified, or scrubbed JSON text.
• Comments, trailing commas, NaN, Infinity, and JavaScript object syntax are not standard JSON.

Verification checklist

• Parse the final output in a second JSON parser.
• Search for every original sensitive value, not only the expected key name.
• Compare counts and required fields with the source schema before using the result.

Troubleshooting

• Use the reported position near a parse error and inspect the preceding comma, quote, or bracket.
• If a rule changes too much, narrow the field-name match and rerun from the original.
• If the editor becomes slow, use a file-oriented or streaming workflow rather than pasting multi-megabyte data.