JSON replace values
ClientBulk status or enum rewrites without a full jq pipeline.
Learn more: replacing values
Matches by JSON.stringify equality; parses from|to segments as JSON when valid.
Local processing
Parsing and output formatting run entirely in your browser—nothing is uploaded for this transform.
Input
?
Nearby workflows on Toolcore
- JSON rename keys — Map old property names to new—deep rename at every object level; local only. once JSON text parses on this page.
- JSON set field on rows — Set one field on every object in a JSON array—field=value, value may be JSON. once JSON text parses on this page.
- JSON filter by field — Keep objects in a JSON array where one field equals a value—client-side row filter. once JSON text parses on this page.
- JSON formatter — JSON format online: pretty-print, minify, validate, escape, download . once JSON text parses on this page.
Common use cases
- Bulk status or enum rewrites without a full jq pipeline.
Common mistakes to avoid
Invalid JSON
Fix parse errors before expecting output.
FAQ
Is data uploaded?
No—all parsing and transforms run locally.
How is this different from jq?
This page focuses on one deterministic task without a filter language.
More tools
Related utilities you can open in another tab—mostly client-side.
JSON rename keys
ClientMap old property names to new—deep rename at every object level; local only.
JSON set field on rows
ClientSet one field on every object in a JSON array—field=value, value may be JSON.
JSON filter by field
ClientKeep objects in a JSON array where one field equals a value—client-side row filter.
JSON formatter
ClientJSON format online: pretty-print, minify, validate, escape, download .json.