What JSON value replacement is
Change exact values without changing document structure
JSON value replacement searches selected leaf paths for one exact typed value and writes the replacement you choose. Property names, nesting, arrays, unmatched values, and record order remain intact.
API migration
Update legacy constants in request and response samples
Replace retired status strings, version labels, numeric identifiers, or feature flags across selected API fields. Exact typed matching prevents the text "1"from being confused with the number 1.
Data normalization
Standardize known values before downstream processing
Convert one known category label or sentinel value into the representation expected by an import, analytics pipeline, or internal dataset. Missing paths are skipped, while explicit null values can be matched intentionally.
Configuration updates
Change exact flags and settings with a reviewable preview
Update booleans, numbers, text, or nulls in selected configuration paths, then inspect every result before copying or downloading it. No patterns or conditional rules run behind the scenes.
Examples
Use explicit types for predictable replacements
| Selected field | Find | Replace with |
|---|---|---|
status | Text: pending | Text: active |
score | Number: 0 | Number: 10 |
verified | Boolean: false | Boolean: true |
note | Null | Text: unknown |
Modification utilities
Continue with related UtilityDock JSON workflows
FAQ
Questions about replacing JSON values
Does UtilityDock upload or store my JSON?
No. Your files never leave your computer. Validation, field detection, replacement, preview, copying, and download creation all happen locally inside your browser.
Which JSON values can I replace?
Version 1 matches exact text, numeric, boolean, or null values in the selected fields. Text matching is case-sensitive.
Are JSON types preserved?
You explicitly choose the find type and replacement type. A numeric 1 is different from the text "1", and replacements are written using the type you select.
Can I replace values in nested fields?
Yes. UtilityDock detects nested object and indexed array paths, then searches only the exact leaf paths you select.
What happens to missing fields and null values?
Missing paths are skipped and never counted. Only explicit JSON null values match when the find type is Null.
Does this tool support patterns or case-insensitive matching?
No. Version 1 performs exact, case-sensitive matching without regular expressions, wildcards, conditional rules, or APIs.