About
Last updated 20 November 2026
A .env file is the most copied and least read file in a project. It starts as three lines on someone's laptop, grows a database URL and two API keys, gets pasted into a chat window when a teammate cannot start the app, and ends up in a commit as a file called .env.example that nobody opens. This page is about reading that file before any of those steps.
What it does
- The audit. Every line is read the way a dotenv parser reads it, and sixteen kinds of problem are reported by line number: a duplicate key, a space around the equals sign, a quote that never closes, a name a parser would reject, an empty value, a line with no equals sign, the export prefix, a value shaped like a live credential, a placeholder, a
${VAR}with nothing behind it, an inline comment, a trailing space, text after a closing quote, a byte order mark, Windows line endings, and a line that starts with a space. - The example file. The same keys with the secrets taken out: a recognisable prefix stays, everything else becomes blank with a note about its length. This is the file a team can commit, and the keys mode empties every value for teams that keep even their ports out of git.
- The comparison. Two files go in, and the answer is three lists: keys only on the left, keys only on the right, and keys whose value differs. Values are hidden until asked for, because the useful part of a diff is usually which key, not what secret.
- The writers. The same keys as JSON, a TypeScript
Envtype, a Zod schema, a Docker Compose services block, a Kubernetes ConfigMap and a Secret. Each one is written in the tab and downloaded from it.
How a line is read
The parser follows the conventions dotenv readers share, in this order. A line is skipped when it is blank or starts with #. An optional export is noted and removed from the name. Everything before the first = is the name. Leading spaces around the name and the value are noted. A value that starts with a single or double quote runs to its closing quote, and the rest of the line is checked for text that a reader would ignore. Any other value ends at a # that follows a space.
Names are checked against letters, digits and underscore, and the last definition of a name wins. That last rule is why a duplicate is an error and not a note: the file says one thing and the process sees another.
What it deliberately does not do
- It does not expand
${VAR}. A reference with nothing behind it in the same file is reported, and the text is left as written. Shells, dotenv libraries and docker each expand in their own way; one confident expansion would be wrong for somebody. - It does not check whether a value works. A Stripe key is checked for the shape of a Stripe key, not by asking Stripe. Nothing leaves the tab, so nothing can be validated against a service.
- It does not rotate anything. If a file was already shared somewhere you are unsure about, this page can tell you what was in it. Only the service that issued the key can retire it.
- It does not keep the file. Not in local storage, not in a session, not in a cache. Reload the page and the text is gone, which is inconvenient and on purpose.
Where the values go
Nowhere. The page is static files, the parsing happens in the tab, and the content policy sets connect-src 'none', so no request could leave it even if a script tried. Downloads are built in the page as a blob and handed to the browser; no copy is kept. The only things written to storage are your language and theme choices, under pikkola.env.lang and pikkola.env.theme.
Why it is free
There is no server behind it and nothing to bill for. No account, no ads, no analytics, no mail. The other Pikkola tools work the same way: one page, one job.
Contact
Write to hello@pikkola.com with a line that was read wrong, or a rule worth adding.