What configuration formats are supported?

The tool supports JSON, YAML, TOML, and ENV formats. You can mix and match formats across different environments in the same comparison.

How do I separate different environments in the input?

Use a header format like === environment-name (format) === before each block, such as === dev (json) === or === prod (env) ===.

Are my API keys and passwords safe?

Yes. By default, the 'Mask Secret Values' option is enabled, which automatically hides the values of secret-like keys (e.g., tokens, passwords) in the output report.

How does the tool handle nested JSON or YAML objects?

Nested objects and arrays are flattened into dot-path keys, such as services[0].url or database.credentials.user, making it easy to compare deep structures.

Can I compare more than two environments at once?

Yes, you can paste as many environment blocks as you need. The visualizer will compare all of them side-by-side to highlight drift across your entire infrastructure.

Elysia Tools

Navigation

Development

Environment Config Diff Visualizer

Compare dev, staging, and production configuration bundles across JSON, YAML, TOML, or ENV formats and highlight drift, missing keys, and cleanup suggestions

Details

What this tool helps you do

Paste multiple config blocks into "Configuration Bundle" and separate them with headers in the form of === environment-name (format) ===.

Supported header examples:

=== dev (json) ===
=== staging (yaml) ===
=== prod (toml) ===
=== worker (env) ===

Supported formats:

JSON: use a normal JSON object such as {"PORT":3000,"feature":{"beta":true}}
YAML: use indented key/value pairs such as PORT: 3000 and feature:
beta: true
TOML: use key/value syntax such as port = 3000 with tables like [feature]
ENV: use dotenv style lines such as PORT=3000 and API_URL=https://api.example.com

Tips:

Add at least two blocks so the diff can compare environments.
Keep the same logical keys across environments when possible.
Secret-like keys are masked by default when "Mask Secret Values" is enabled.
Arrays and nested objects are flattened into dot-path keys in the report, for example database.host or services[0].url.

Execution

Run this tool

Fill in the form, run the tool, and review the result in one place.

Result

Ready for a run

Run the tool to preview files, text, structured data, or streamed output here.

Samples

Environment Config Diff Visualizer

What this tool helps you do

Run this tool

Prepared example runs

Inputs

Result

Examples that match this tool

Continue with connected tools and hubs

Prepared example runs

Inputs

Result

Learn when to use this tool, what it supports, and how real users apply it.

Key facts

Overview

When to use

How it works

Use cases

Examples

1. Pre-deployment Environment Check

2. Migrating JSON to YAML

FAQ

Distributed Tracing Samples

OpenAPI/Swagger Samples

Parcel Bundler Samples

pnpm Package Manager Samples

JSONata Query & Transform Studio

BOM Character Remover

YAML-JSON Converter

OpenAPI to TypeScript Generator

JSON Formatting, Diff, and Normalization Tools

Configuration File Conversion and Environment Diff Tools

JSON Interchange and Format Translation Tools

JSON Inspection, Diff, and Transformation Tools