duplicate-key
Duplicate key
The same name twice. The later line wins and the earlier value vanishes without a word.
PORT=3000 PORT=8080
Pikkola Env Studio, tool No. 46
Paste a file and four things come back: each line checked, a .env.example with the secrets taken out, a key by key comparison of two environments, and the same keys as JSON, TypeScript, Zod, Compose or Kubernetes. Nothing is uploaded and nothing is kept.
The workbench
The audit, the example file and the converters all follow the one file below. Compare takes two of its own.
Keys, comments and blank lines are counted, then every line is read the way a dotenv parser reads it. Problems come back in line order.
| Line | Level | Key | What | Rule |
|---|
An error breaks a parser, a warning is worth a look, a note is information.
Secrets are cut back to their prefix or left empty with a note; every other value keeps its own. The keys mode empties every value instead.
Download it as .env.example, commit that, and keep the real .env in .gitignore. A masked value that keeps its prefix still shows a teammate which service it belongs to.
Keys only on the left, keys only on the right, and keys whose value differs. Values are hidden until you ask for them.
Values are compared with the quotes removed, so "3000" and 3000 count as the same.
Types are inferred from the value. A secret value is never copied into a draft unless you tick the box on the Secret tab.
A plain object, with numbers and booleans typed instead of quoted.
The audit
Each rule is a line someone shipped once: a duplicate that silently won, a quote that swallowed the rest of the file, a key that only worked in one shell.
duplicate-key
The same name twice. The later line wins and the earlier value vanishes without a word.
PORT=3000 PORT=8080
space-around-equals
PORT = 3000 is read by some parsers with the space kept, so the value is not what it looks like.
PORT = 3000
unclosed-quote
One missing quote turns the rest of the line into the value, and can pull the next lines in with it.
GREETING="hello
invalid-key
Letters, digits and underscore only, and the first character cannot be a digit.
1ST_KEY=value
empty-value
The key exists and holds nothing. Some tools treat that as missing, others as an empty string.
SMTP_PASSWORD=
no-equals
A pasted sentence, or a key without a value, reads as nothing at all.
DATABASE_URL postgres://…
export-prefix
export works in a shell. A dotenv reader that does not strip it sees a key called export NODE_ENV.
export NODE_ENV=production
secret-value
Stripe, GitHub, AWS, Slack, Google or SendGrid keys, a JWT, a bearer token, or a password inside a URL.
STRIPE_SECRET_KEY=sk_live_***
placeholder-value
changeme, your_key_here or a value in angle brackets. It works until the first request arrives.
SMTP_PASSWORD=changeme
undefined-reference
${VAR} that is not defined in this file. It expands to an empty string, quietly.
API_BASE_URL=${PUBLIC_ORIGIN}/v1inline-comment
Everything from # on is dropped, even when it was written as part of the value.
PORT=3000 # the dev port
trailing-space
Invisible in an editor, and part of the value in most readers.
CACHE_DIR=./tmp␠
tail-after-quote
The quote ends the value. Anything after it that is not a comment is ignored.
MODE="strict" now
bom
An editor saved the file with one. Some readers attach it to the first key, and that key is never found.
EF BB BF 41 50 50
crlf
Most readers cope, and a few keep a carriage return at the end of the last value.
PORT=3000␍␊APP_ENV=prod␍␊
indent
The name picks the space up. A lookup by the name you meant finds nothing.
SPACED=1
The writers
Every format is written in the tab and downloaded from it. None of them carries a value you did not ask it to carry.
| Output | What it writes | Where it goes |
|---|---|---|
| JSON | A JSON object with the values in it, numbers and booleans typed | A config file for a script, or a value to compare in review |
| TS | An Env type, keys only, no values | env.d.ts, so a misspelled key fails at build time |
| Zod | z.object with coercion for numbers and booleans, .url() and .email() where the value allows | Reading process.env once, at start up |
| Compose | A services block with ${KEY} references and env_file | docker compose up, with the values left in .env |
| ConfigMap | A ConfigMap with the keys that are not secret, as strings | Settings that can live in git and in a cluster |
| Secret | A Secret with the secret keys, empty values by default | kubectl apply, once the values are filled from your store |
No. The page parses, masks, compares and formats in the tab, and the content policy sets connect-src 'none', so a request could not leave even if a bug tried. It also keeps nothing in local storage: the file is gone when the tab closes, on purpose.
It never leaves this tab and nothing is kept. Still, the careful path is a copy of the file, and if a file has already been shared somewhere you are unsure about, rotating the keys is the step that does not depend on any tool.
Sixteen things: duplicate keys, spaces around the equals sign, quotes that open and never close, names a parser would reject, empty values, lines with no equals sign, the export prefix, values that look like a live credential, placeholder values, ${VAR} references with nothing behind them, inline comments, trailing spaces, characters after a closing quote, a byte order mark, Windows line endings and a line that starts with a space.
Because the shape is the useful part. A teammate needs to know the key exists, roughly how long the value is and which service it belongs to. The prefix keeps that hint while the value stays on your machine.
The conventions dotenv readers share: KEY=VALUE, # for comments, single or double quotes, an optional export, and ${VAR} for a reference. Where libraries disagree, the audit stays quiet instead of guessing.
No. A reference with nothing behind it in the same file is reported, and the text is left as written. Shells, dotenv and docker each expand differently, and a wrong expansion in a shared example is worse than none.
JSON and the ConfigMap do carry values: JSON because a config file without values is not a config file, and the ConfigMap only the values that do not look secret. TypeScript, Zod and Compose carry keys and types. The Secret draft holds empty values until you tick the box.
It is one page of static files with no server behind it, so there is nothing to bill for. No account, no ads, no analytics, no mail.