How to explore complex json configuration files in a tree view
- Step 1Paste the full configuration JSON — Copy the complete JSON configuration file content and paste into the tree viewer. Large configuration files with hundreds of keys are particularly well-suited to tree navigation.
- Step 2Collapse sections to orient yourself — Collapse all root-level nodes first to see the top-level structure. Then expand only the sections relevant to your current task — database config, feature flags, external service endpoints.
- Step 3Search for specific settings — Use the search bar to jump to a specific key like logLevel, maxRetries, or connectionTimeout. The matching key highlights and the tree expands to show its parent context.
- Step 4Verify value types for boolean and numeric settings — The tree viewer shows explicit types alongside values: true (boolean) vs 'true' (string). This catches configuration bugs where a boolean flag is accidentally stored as a string.
Frequently asked questions
How do I compare two configuration files using the tree viewer?+
The tree viewer is for exploration, not comparison. Use the JSON Diff tool to compare two configuration files and highlight the differences. Use the tree viewer to explore each file's structure independently.
Can I use the tree viewer for YAML Kubernetes manifests?+
The tree viewer handles JSON. For YAML manifests, first convert to JSON using the YAML to JSON tool, then explore the result in the tree viewer. The structure is identical — only the syntax differs.
Are configuration values transmitted to JAD Apps?+
No. Tree rendering runs entirely in your browser. Configuration file content including private settings 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.