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

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

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.

Back to the workbench