Privacy: Processing happens locally in your browser. No input is uploaded.
JSON Redactor — Mask Sensitive Data
Create a safer copy of an API response, log payload or fixture before sharing it. Choose sensitive field names and optionally detect common secret-like values.
Redact JSON before sharing logs and API payloads
JSON often contains credentials, personal data and identifiers mixed with useful debugging context. This tool recursively checks property names and masks or removes matching fields. Optional value detection also looks for common email, payment-card and token-like strings.
What to check after redaction
Automated matching is a first pass. Read the complete output before sending it to support, pasting it into an issue, or using it as an AI prompt. Secrets may use unexpected field names, and some identifiers are sensitive only in your organization.
| Data type | Suggested treatment |
|---|---|
| Passwords and access tokens | Always remove or replace |
| Email addresses and phone numbers | Mask unless explicitly needed |
| Session IDs and request headers | Treat as sensitive until verified |
| Internal IDs | Assess whether they identify a person, account or system |
The transformation runs locally and does not upload the input. You can then use JSON Formatter, JSON Compare, or JSON Sample Generator for the next step.
How to use this tool
- Paste or upload the source into the left editor.
- Choose the relevant options and run the transformation.
- Review the right-hand output, then copy or download it.
Frequently asked questions
Does this tool upload my input?
No. Processing happens in the browser.
Can I download the output?
Yes. Use the Download button after generating the result.
Should I review the result?
Yes. Generated and transformed output should be checked against the requirements of the system that will consume it.