Remove JSON Property
Remove JSON Property parses the document and recursively rebuilds objects while excluding every property with the exact case-sensitive key; arrays retain length and order while their elements are traversed. The field names a key, not a dot path, so entering id removes id at every depth but a.b matches only a literal key named a.b. It cannot target one location, preview a count, undo, or prove sensitive data is gone from other values.
Runs locally — files stay on your deviceDoes it remove only the first matching key?
No. It removes exact matches from every object at every depth.
Global key removal differs from path deletion
A property name can repeat in unrelated subtrees. Removing by name has broader effects than deleting one JSON Pointer path.
How it works
Arrays map recursively; object entries with matching keys are filtered out; all other values are retained and output with two spaces.
Key concepts
Exact and case-sensitive
id does not remove ID.
Every depth
Unrelated objects lose the same-named key.
When to use it
- Strip one known metadata key everywhere.
- Create a reviewed derivative fixture.
- Remove repeated debug fields from a small object.
When not to use it
- Do not enter a path expecting location targeting.
- Do not treat it as certified data redaction.
- Do not forget case-sensitive variants or values containing the same information.
Worked examples
Nested IDs
- Input
{"id":1,"x":{"id":2}}; key id- Expected output
{"x":{}}
Both are removed.
Case
- Input
{"ID":1}; key id- Expected output
ID remains
Case differs.
Path-looking key
- Input
{"a":{"b":1}}; key a.b- Expected output
Unchanged
No path parsing.
Common mistakes
Expecting path semantics
Only literal key equality is used. Correction: Use JSON Pointer deletion.
Over-removing
Every subtree is affected. Correction: Review all occurrences first.
Calling it anonymization
Sensitive values may remain elsewhere. Correction: Perform a complete data-flow/privacy review.
Best practices
- Search all occurrences before removal.
- Retain an original.
- Validate the derivative against schema and privacy requirements.
Related operations and differences
Compare JSON
Choose Compare JSON when you need to show value differences between two JSON documents.; use Remove JSON Property specifically for json remove property.
CSV Column Extractor
Choose CSV Column Extractor when you need to extract one CSV column by header name.; use Remove JSON Property specifically for json remove property.
CSV Column Remover
Choose CSV Column Remover when you need to remove one CSV column by header name.; use Remove JSON Property specifically for json remove property.
CSV Duplicate Remover
Choose CSV Duplicate Remover when you need to remove completely duplicated CSV rows.; use Remove JSON Property specifically for json remove property.
CSV Formatter
Choose CSV Formatter when you need to normalize CSV quoting and row structure.; use Remove JSON Property specifically for json remove property.
CSV Row Filter
Choose CSV Row Filter when you need to keep rows whose selected column contains a value.; use Remove JSON Property specifically for json remove property.
Limitations and privacy
- Exact global key match only.
- No path targeting, case-insensitive mode, occurrence count, preview, schema, audit log, reversible patch, or privacy guarantee.
Input is processed locally in this browser and is not uploaded by the tool.
Frequently asked questions
Is matching case-sensitive?
Yes.
Are arrays traversed?
Yes.
Can I specify a.b?
Only as a literal key, not a path.
Does this guarantee anonymization?
No.