Inspect and format a .env file with secret values masked by default, duplicate keys and dangling references reported, and nothing uploaded, logged or stored.
Waiting for a .env file
Nothing is uploaded, logged or stored. Values are masked until you ask to see them.
The variables appear here
Each variable with its value masked, what kind of credential it looks like, and anything wrong with the line.
Masking is not encryption. A masked value still shows its length and its first characters, which is enough to recognise a key you already know — it is a defence against someone reading your screen, not a guarantee of secrecy. Secret detection works from the name, the value's shape and its entropy, so a credential with an ordinary name and a short value can slip past it. And if a secret has ever been committed, removing it from the file does not remove it from the history: rotate it.
.env Inspector runs entirely on your device — nothing is uploaded, logged or stored.
You’re on the Free plan. Compare plans
A .env is the single most likely file a developer will paste into a web page without thinking, and the one most likely to hold a live database password or an API key with billing attached. That shapes every decision in this tool: values are masked by default, unmasking is a deliberate click, and nothing is written to browser storage of any kind — not localStorage, not sessionStorage, not IndexedDB.
Nothing is uploaded and nothing is logged. The site's analytics schema has no free-text parameter at all, so there is no field a value could be put into even by mistake. The input lives in React state and is gone when the tab closes.
Masking is not encryption, and the page says so where the masking is. A masked value still shows its length and its first characters, which is enough to recognise a key you already know. It is a defence against someone reading your screen, not a guarantee of secrecy.
Secret detection uses three signals — the variable's name, the value's shape against known credential formats, and its entropy. All three can miss: a credential with an ordinary name and a short value gets past every one of them. The page reports which signal fired rather than claiming a verdict.
Frameworks genuinely disagree about .env syntax. Quoting, escapes, multi-line values and variable expansion have all changed at least once in dotenv, Next.js and Vite. The findings say where a line is ambiguous rather than implying there is one correct answer.
Nothing is uploaded, logged, or written to browser storage, and the analytics schema has no field that could carry a value. The remaining risk is your own screen: anything visible is visible in a screen share, which is why values are masked until you ask.
No. A masked value still shows its length and first characters, which is often enough to recognise a key somebody already knows. It is a shoulder-surfing defence, not secrecy.
It depends on the loader, which is why this reports the duplicate rather than resolving it. Most keep the last; plain dotenv keeps the first unless told otherwise. Two definitions is one too many whichever way it goes.
Sometimes. Plain dotenv does not expand variables without a plugin; Next.js and Vite do. A reference to something this file does not define is reported as a note rather than an error, because it may come from the real environment.
Detection works from the name, the value's shape and its entropy. A credential with an innocuous name and a short value gets past all three. The flag is a help, not a guarantee.