JSON rename keys with map

Client

Bulk key migration with an explicit mapping table.

Learn more: key maps

Unmapped keys are kept; map applies recursively to nested objects.

Local processing

Parsing and output formatting run entirely in your browser—nothing is uploaded for this transform.

Input

?
Paste JSON, then read transformed output below.

Nearby workflows on Toolcore

  • JSON rename one key — Rename a single property name at every object level—local rename helper. once JSON text parses on this page.
  • 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 prefix keys — Prepend the same string to all object keys recursively—client-side rename helper. 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 key migration with an explicit mapping table.

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.