Sanitize JSON before sending it to an AI

Config objects and API responses are secret goldmines: api_key fields, nested token values, user emails. Scan the whole structure and redact — locally, with the JSON shape intact.

Where secrets hide in JSON

• Top-level config keys — api_key, secret, token, password.
• Nested objects — user.session.refresh_token, integrations.slack.webhook.
• String values inside arrays — a notes array carrying an Authorization header.
• Emails and PII — customer addresses pasted for "example data".

Why the structure is kept

The AI still needs to see that a key existed — removing fields breaks schemas and confuses debugging. Replacing values with <REDACTED> keeps every path intact while the secret itself stays on your machine.

Is my JSON uploaded anywhere?

No. This page is a single static HTML file — scanning runs entirely in your browser. Disconnect from the internet after it loads.

Need the full toolbox?

This page is one tool from LocalDevToolbox — 15+ local developer tools: context optimizer, log doctor, stack trace analyzer, cURL converter and more.