JSON Redactor & Sensitive Data Masker Online
About JSON Redactor
The JSON Redactor masks selected values before you paste a payload into a ticket, chat, document or test fixture. Enter key names such as password and token to match them wherever they occur, or enter an exact dot path such as user.email when only one location should be hidden.
Redaction runs locally and starts by parsing the input as JSON. It walks objects and arrays without changing the original field layout, value types outside matched fields or key order. The resulting document can be copied as readable JSON while sensitive values are replaced with a visible marker.
This is a sharing aid rather than an automated compliance classifier. The tool only masks selectors you provide and cannot know every field that your organization considers personal or confidential. Review the output, especially free-form strings and unexpectedly named fields, before publishing it outside its intended audience.
How it works
Match a key anywhere
A one-part selector such as secret matches that key at any object depth, including objects nested inside arrays. Matching is case-insensitive, so Secret and secret are treated consistently.
Target an exact dot path
A selector containing dots matches the full path from the root. Use user.email to redact that field without hiding billing.email. An asterisk can stand in for one path segment when several objects share the same layout.
Choose a marker and optional visible suffix
Use [REDACTED], three asterisks or a text null marker as the replacement. The Keep last option can preserve the final four or eight characters of string values when operators need a limited identifier for troubleshooting.
Review before sharing
The output remains valid, pretty-printed JSON. Search the result for emails, authorization headers, access keys and customer identifiers that may use names outside your selector list before you send it onward.
Frequently asked questions
Can I redact the same key at every level?
Yes. Enter a single key such as token and every property with that name is replaced, regardless of its nesting depth.
How do exact paths and wildcards work?
Dot paths start at the document root. For example, users.*.email can match one path segment represented by the asterisk; array positions can also be written as path segments when an exact index matters.
Does this detect sensitive information automatically?
No. It follows the selectors you enter. That avoids hidden guesses but means you must include every key or path that should be masked and review the final output.
Is keeping the last four characters always safe?
No. It is useful for correlating opaque identifiers, but any retained characters reveal information. Use a complete replacement when the suffix is itself sensitive or the value is short.