JSON Anonymizer
Anonymize sensitive PII in JSON instantly. Detects and replaces emails, names, phones, passwords, IPs, and addresses. Runs 100% in your browser.
Anonymize JSON payloads before sharing in tickets, documentation, or with third parties.
The tool detects PII fields by key name and replaces values with realistic synthetic data —
emails become user_1234@example.com,
names become random names, passwords become random strings, and IP addresses become
private-range IPs. All processing runs entirely in your browser.
Related tools
Frequently asked questions
Which fields are automatically anonymized?
Detection is based on key names (case-insensitive, partial match): email/mail → fake email, firstName/lastName/name/username → random name, phone/tel/mobile → US-format phone, password/secret/token/apiKey/key → random 24-char string, address/street → numbered street, city → city name, zip/postal → 5-digit code, ip/ipAddress → 192.168.x.x, creditCard/card → test card number, ssn/social → formatted SSN.
Does my data leave the browser?
No. All JSON processing happens entirely in your browser using JavaScript. Nothing is sent to any server. You can verify this by opening DevTools and inspecting network requests — there are none for the anonymization operation.
What does "Preserve length" do?
When enabled, the anonymized replacement string is padded or trimmed to match the character length of the original value. This is useful when downstream systems validate field lengths or when you want to maintain consistent data shapes for testing.
What does "Blur numbers" do?
With "Blur numbers" off (default), numeric values like age: 34
or salary: 85000 are left unchanged.
When enabled, numeric values are replaced with a random number of the same order of magnitude,
which obscures potentially sensitive numeric data while keeping it realistic.
Will nested objects and arrays also be anonymized?
Yes. The anonymizer recursively processes the entire JSON tree — nested objects and every element in arrays are all checked against the key-name rules. The anonymized count shown reflects the total number of values replaced across the entire structure.
Is this a replacement for a proper data masking solution?
This tool is designed for developer convenience — quick cleanup before pasting into a Jira ticket or sharing with a colleague. For production-grade anonymization pipelines (GDPR/HIPAA compliance, database masking, CI anonymization), use a purpose-built solution like AWS Macie, Presidio, or your database's native masking features.