Toolvore

JSON Redactor

Replace values at explicit JSON pointers, preserve other fields and inspect a shareable JSON result locally.

This tool processes its input contents in your browser instead of sending them to a processing service. Page, asset and fixed usage-measurement requests are described on the Privacy page.

Replace existing values at explicit RFC 6901 pointers with [REDACTED], failing when a selected path is missing instead of silently leaving it untouched.

How to use it

  1. 1Paste the JSON you want to prepare for sharing.
  2. 2Enter each exact path on a separate line and generate a result.
  3. 3Review every remaining field before copying or downloading the separate output.

Example

Input
{"token":"demo","name":"Mira"} Path:/token
Output
{ "token": "[REDACTED]", "name": "Mira" }

What happens to your data

Source data, selected paths and redacted output remain in tab memory. This is not automatic sensitive-data detection.

Last updated November 2026

Prepare a JSON example for a support ticket, documentation or a colleague by replacing selected values before sharing it. Paste the data, enter exact JSON pointers such as /account/token and /user/password, and generate a separate redacted result. The original remains in the source field; copy or download the result after reviewing it.

How it works

Each nonblank line identifies one existing JSON value using RFC 6901 syntax. A slash separates path segments. A slash inside a property name is written as ~1, and a tilde as ~0. Array positions are zero-based. The selected value may be a string, number, object, array, boolean or null; the entire value is replaced with the string [REDACTED]. Other values retain their meaning and exact numeric tokens.

A missing path stops the job rather than producing a reassuring result that leaves the intended secret in place. Duplicate selections are collapsed. If a selected parent already contains another selected value, replacing the parent also removes the child; the result explains this overlap. Objects with duplicate property names are rejected because their paths would otherwise be ambiguous.

This is an explicit-path editor, not automatic personal-data detection. It does not inspect the meaning of names, find every token in free text, sanitize arbitrary logs or guarantee that a document is safe to publish. A password repeated elsewhere remains unless its other path is also selected. Check the complete result and any surrounding files before sharing. Inputs stay in this browser tab, but anything you later paste into another service follows that service's handling rules. Inputs are limited to128 KiB and5,000 values; at most100 paths can be selected per job.

Common use cases

  • Replace known authorization fields in a JSON support fixture.
  • Remove a complete private nested object while retaining the remaining diagnostic structure.
  • Create a documentation example with an auditable list of explicit replacements.

Frequently asked questions

Will it automatically find every secret?+

No. You select the exact paths. Content in another field, embedded text or another file is untouched.

Does it delete the original input?+

No. It creates a separate result. Clear removes the current workspace values; the tool does not maintain a saved history.

Can I use wildcards?+

No. Paths are exact RFC 6901 pointers, including explicit array indexes. Unsupported or missing paths produce an error.

Can I replace an entire object?+

Yes. Selecting that object's path replaces its complete value. The result reports selections already covered by a parent.