Compare & Diff
Tool data stays in browser
Compare Environments
Diff two environments — or three, to catch the value only staging has — across .env, ConfigMap, YAML, JSON, headers, OpenAPI, CSV, and DB columns. Locally, nothing uploaded.
Auto-runs as you type. Ctrl+Enter to re-run.
How to use Compare Environments
Detect configuration drift between dev, UAT, staging, and production environments without uploading anything. Paste two configs side-by-side and get a clear breakdown of keys that are only in A, only in B, or differ in value. Supports eight common config formats used across modern stacks.
Supported modes
- .env — Compare dotenv files key-by-key. Detects missing keys and value drift between environments.
- Kubernetes ConfigMap — Paste two ConfigMap YAMLs and diff only the
data:entries. - YAML — Deep-diff arbitrary YAML config trees. Optionally match list items by
namefield. - JSON — Deep-diff JSON objects. Useful for app config, feature flags, and API responses.
- HTTP Headers — Paste two sets of raw HTTP response headers and find missing or changed headers.
- OpenAPI — Compare two OpenAPI 3.x specs and surface added, removed, or changed paths and operations.
- CSV — Diff two CSV exports row-by-row using a key column to align rows.
- DB columns — Paste two lists of column names and find schema drift between database tables or environments.
When to use it
- Before a production release — verify staging config matches production.
- During an incident — quickly check whether a config change caused drift.
- When onboarding a new environment — make sure all required keys are present.
- During API contract reviews — compare OpenAPI specs across service versions.
- For database migrations — confirm schema changes are applied consistently.
How to use it
- Select the mode that matches your config format.
- Paste environment A (e.g. dev) in the left panel and environment B (e.g. prod) in the right panel.
- Optionally name each environment using the label inputs.
- Click Compare to see the diff grouped by: only in A, only in B, and different values.
- Use Mask secrets to hide values whose keys look sensitive before sharing a screenshot or report.
- Copy or download any result bucket for your runbook, ticket, or post-mortem.
Tips & pitfalls
- For .env files, comments and blank lines are ignored during comparison — only key/value pairs are diffed.
- For YAML and JSON, nested objects are deep-diffed. Enable Match list items by name when your lists contain objects with a
namefield (e.g. Kubernetes containers). - For CSV, specify the key column so rows can be aligned — without it, rows are compared positionally.
- Mask is a heuristic — keys containing
SECRET,TOKEN,PASSWORD,KEY,PRIVATEare masked. Custom secret names may not be caught. - The tool never sends your data anywhere. Safe to use with production config values.
FAQ
- Can I compare more than two environments? Run the tool twice — A vs B, then B vs C.
- Is my config uploaded? No. All processing runs in your browser.
- What counts as a "difference"? A key present in one env but not the other, or a key present in both but with different values.
- How do I compare Kubernetes Secrets? Use the YAML mode — paste the full Secret manifest and the tool diffs the
data:orstringData:block. - Can I diff OpenAPI specs from different API versions? Yes — paste the full JSON or YAML spec for each version and review added/removed/changed paths.
Runs locally in your browser. No uploads. Mask secrets before sharing results with teammates.