Does Env Diff store my .env files?
No. Comparison runs in your browser. QASignoff does not send the file contents to a server or keep them after you close the tab.
Free tool · Env Diff
Compare .env Files OnlineMissing keys, secret drift, and prod risks in your browser.
We don’t store anything. This session only—close the tab and it’s gone.
PrivateJSON instead? JSON Formatter · JSON Diff · Compare · JWT Decoder
QASignoff Env Diff
Paste two env files. Keys are compared; secrets stay masked.
QASignoff Env Diff · browser only
Ctrl/Cmd + Enter to compare
Compare .env files in your browser
Use Env Diff to spot missing keys, secret drift, DEBUG in prod, and localhost in production config without leaving the page. It is meant for a quick QA check of two environments—not a vault, and not a desktop Studio workspace. For JSON payloads use JSON Formatter or JSON Diff; for XML, YAML, CSV, or text use Compare.
Why mask secrets
Env files often hold API keys and connection strings. Masking keeps those values off the screen during a review. The comparison still uses the real strings in memory so missing keys and changed secrets are accurate. Turn masking off only if you need the full value, then close the tab.
Dotenv vs JSON
Most teams paste dotenv: KEY=value, optional export, comments, and quotes. JSON and YAML work when they are a flat map of scalars. Nested objects, arrays, and Kubernetes or SSM secret stores are out of scope. Stage labels (Staging vs Prod) come from the toolbar, not from the file.
How to compare two env files
- 1Paste or upload two .env, JSON, or YAML config files. Set each side to Dev, Staging, Prod, or Other.
- 2Click Compare (or press Ctrl/Cmd+Enter). Keys are unioned and sorted; secrets stay masked.
- 3Review missing keys, changed values, and prod risks. Download Signoff Studio to keep environments in one workspace.
Why use this env diff
- Compare staging vs prod config in the browser with nothing stored on QASignoff servers.
- Secrets are masked by default; unmask is an explicit choice with a warning.
- Catch DEBUG in prod, localhost in production URLs, missing keys, and shared secrets.
- Works with dotenv, flat JSON, and flat YAML—no extra libraries to install.
- Use it free, with no account.
Frequently asked questions
Why are secrets masked by default?
Keys that look like secrets (API_KEY, PASSWORD, TOKEN, DATABASE_URL, and similar) are shown as dots plus the last four characters. Masking is display-only. Compare and risk rules still use the real values in memory. Unmask is an explicit toggle with a warning.
What is the difference between dotenv and JSON?
Dotenv is KEY=value lines, including export KEY=value, comments, and quotes. JSON must be a flat object of strings, numbers, or booleans—nested objects and arrays are rejected. YAML follows the same flat-map rule. Auto-detect picks a format; you can override it.
Does this tool upload my config or open Signoff Studio?
No. Nothing you paste is fetched or stored. There is no “open these environments in Studio” handoff. Download Signoff Studio if you want environments in one workspace.
What counts as a production risk?
When a pane is set to Prod, Env Diff flags DEBUG-style keys set to true and values that contain localhost or .local. Warnings cover missing keys, the same secret on both sides, weak values, NODE_ENV=development on Prod, and duplicate keys.
Is it safe to paste a production .env?
Prefer staging or example files. Secrets stay masked on screen unless you turn masking off. We do not store what you paste, but your screen, clipboard, and browser extensions still can. Close the tab when you are done.
How is this different from Compare?
Compare is a structural or line diff for JSON, XML, YAML, CSV, and text. Env Diff is a key matrix: missing keys, changed values, masked secrets, and staging-vs-prod risk rules. Use Env Diff for .env files. Open Compare
Do I need an account?
No. Env Diff is free, runs in the browser, and does not require signup or installation.
Signoff Studio
Catch env drift here. Keep environments in one workspace.
Staging vs prod checks, then Signoff Studio.