How to merge user settings json with application defaults
- Step 1Prepare defaults.json — Paste the full application defaults JSON as the first input. This should include every possible setting key with its default value — it is the fallback for any key the user has not customized.
- Step 2Paste the user settings JSON — Paste the user's saved settings JSON as the second input. This is typically a sparse object — only the keys the user has changed from the default.
- Step 3Review the effective settings — The merged output shows every setting with the user's value where specified and the default value everywhere else. This is what the application sees at runtime.
- Step 4Test new defaults for existing users — When adding a new setting to defaults.json, paste the new defaults and an older user settings file. Verify the new setting appears in the merged output — confirming existing users will see the correct default for the new setting.
Frequently asked questions
What if a user's settings file has keys that no longer exist in the defaults?+
Stale user settings keys — from removed features or renamed settings — pass through the merge and appear in the effective settings. To clean stale keys, use the JSON Key Filter after merging to keep only keys that exist in the current defaults. This prevents stale settings from being processed by code that no longer handles them.
How do I handle settings migration — renaming a setting key across all users?+
Use the JSON Key Renamer to rename the old key in the user settings before merging with the new defaults. Run the renamer against all user settings files in bulk, then merge with the updated defaults that use the new key name.
Is user preference data transmitted to JAD Apps?+
No. Merging runs entirely in your browser. User settings and application preferences are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.