Redact sensitive fields from a JSON payload before pasting it anywhere, with each mode stating plainly whether the value is removed or only masked.
Waiting for a payload
Nothing is uploaded, logged or stored.
Waiting for a payload
Paste JSON and pick which fields to remove.
API Payload Redactor runs entirely on your device — nothing is uploaded, logged or stored, which is what makes it safe to paste a real response.
You’re on the Free plan. Compare plans
Pasting a real API response into a bug report is how credentials escape. This takes the payload apart and removes what should not travel with it.
Each mode states whether the original value is actually gone. Removing the key and replacing the value both remove it. Masking does not — it keeps the last few characters so you can still recognise a card or a key, and those characters are real. The tool says so where you pick it, because a mask that is mistaken for a redaction is worse than no redaction at all.
The stable-token mode is the one worth knowing about. Each distinct value becomes the same token everywhere it appears, so you can still see that two fields held the same value — a user id repeated across a payload stays traceable — without the value itself being in the output.
A built-in list covers the names that carry credentials: tokens, keys, secrets, passwords, cookies, card numbers, account numbers and national identifiers. You can add your own, and match on part of a key rather than the whole thing, since real payloads use `customerApiKey` as readily as `api_key`.
Nothing is uploaded, logged or written to browser storage. The payload lives in the page and is gone when the tab closes, which is the only reason it is safe to paste a real one here.
No, and the tool says so where you pick it. Masking keeps the last few real characters so you can recognise the value — useful for your own screen, not for an issue tracker. Use remove or replace for anything leaving your machine.
Replaces each distinct value with a token derived from it, so the same value gets the same token throughout. You keep the ability to see that two fields matched, without the value appearing. The token is not reversible from the output alone.
No. It matches field names, so a credential stored under an unremarkable key is missed. Read the output before sharing it — the tool narrows the problem rather than solving it.
No. It is processed in your browser, never logged, and never written to browser storage. That is what makes it reasonable to paste a real response.
Yes, and that is the trade-off. Removing the key hides that anything was there, which a consumer may notice; replacing the value keeps the shape and makes the redaction obvious. Both genuinely remove the value.