What JSON field renaming is
Change property names without moving their values
Field renaming applies exact name mappings across every matching object in an array. Nested values remain in their existing parent, records stay ordered, and UtilityDock blocks any mapping that would overwrite a sibling field.
Preparing API payloads
Match the names expected by another system
Convert internal names such as account_status tostatus or rename nested response properties before using a payload in fixtures, imports, or integration testing.
Schema migration
Preview a naming change across saved records
Apply several exact mappings to representative data before a schema migration. Conflict detection exposes records where a destination name already exists, without overwriting either value.
Data normalization
Create consistent field names for downstream work
Normalize casing, terminology, and vendor-specific property names before analysis or conversion. Missing source paths are ignored, while every matching path receives the same name.
Examples
Map exact source paths to clearer names
| Source path | New name | Use |
|---|---|---|
id | recordId | Clarify a generic identifier |
profile.email | contactEmail | Normalize contact data |
account_status | status | Match API naming conventions |
Data Toolkit
Continue with related UtilityDock JSON workflows
FAQ
Questions about renaming JSON fields
Does UtilityDock upload or store my JSON?
No. Your files never leave your computer. Validation, field discovery, renaming, conflict detection, preview, copying, and download creation all happen locally inside your browser.
What JSON shape can I use?
Version 1 accepts a non-empty array of JSON objects at the document root.
Can I rename nested properties?
Yes. Enter a new terminal name for any detected object field path. The field stays inside its existing parent object.
Can I rename fields inside arrays?
Object properties inside indexed arrays can be renamed. Numeric array positions themselves are not field names and cannot be renamed.
What happens when a destination field already exists?
UtilityDock blocks the rename and identifies the affected array item. Existing values are never overwritten.
Does renaming change record or property order?
Records and arrays retain their order. Renamed object keys keep the original key position whenever JavaScript object ordering permits.
Can this tool rename fields conditionally?
No. Version 1 applies each exact mapping wherever its source path exists. It does not support conditions, regular expressions, calculated fields, or APIs.