Recursive exact matching
Walk nested objects and arrays while changing only values whose complete field name matches.
JSON Bulk Editor
Batch edit values across nested JSON: multiply prices or other numbers, control decimal precision, and safely rename keys.
Processed locally in your browserNested objects and arrays supportedOriginal input stays available
Calculation rules
Match numeric values by exact field name. Multiplication runs first, then results are rounded to optional decimal places; JSON numbers do not retain trailing zeroes.
Rename keys
When enabled, safely replace matching keys at every nested level.
Processed locally in your browser
Input JSON
Processed output
What changes and what stays intact
Controlled numeric rounding
Handle numbers and strict numeric strings with rounding from 0 to 100 decimal places; practical precision is limited by JavaScript number representation.
Collision-safe processing
Calculate before renaming, and stop without partial output when rules duplicate or keys collide.
Common use cases
Cents-to-currency conversion
Multiply integer prices in nested product data by 0.01 and round to at most two decimal places; JSON numbers do not retain trailing zeroes.
Price or rate multiplier adjustment
Adjust prices, tax rates, percentages, or other numeric fields while controlling rounding.
Schema key migration
Replace an old API key throughout a JSON payload when a schema changes.
Nested export cleanup
Normalize deep arrays and objects before sending exported data to another system.
How to batch edit JSON
- 1
Set your rules
Enter a field, multiplier, and optional rounding decimals. Enable renaming only when you need to change keys.
- 2
Add your JSON
Paste the source, upload one local .json file, or load the example to check the default rule.
- 3
Process and export
Run the editor, review the summary and output, then copy or download the formatted JSON.
Frequently asked questions
Is my JSON uploaded to a server?
No. The transformation runs in this browser and does not require a Toop processing API call.
Can it process nested arrays and objects?
Yes. It recursively walks arrays and objects and matches complete field names at every level.
Are numeric strings calculated too?
Yes. Strict numeric strings such as "1299" or "12.5" become JSON numbers. Values such as "12px", empty strings, booleans, and null are skipped. JSON numbers do not retain trailing zeroes, and practical precision is limited by JavaScript number representation.
Does calculation or renaming run first?
Calculation runs against the original key first, then that key is renamed, so both rules can work together in one pass.
Why can a rename be blocked?
If the new key would overwrite another field in the same object, processing stops to prevent silent data loss.