Paste the file
The whole .env, with comments and blank lines if you like.
Paste your .env file and see the mistakes that break configuration: repeated keys, invalid names, unclosed quotes, spaces where they should not be. You can also make a copy with the secrets hidden.
100% private — your text is processed in your browser and never sent to any server.
The whole .env, with comments and blank lines if you like.
Each problem comes with its line number.
Get a .env.example with names only, or a copy with hidden values.
A .env file stores configuration, such as database addresses, keys and feature flags, as simple NAME=value lines
that an application reads when it starts. The format looks trivial, but there is no official standard and every tool reads it
a little differently. A repeated name, a missing quote or a space in the wrong place can silently give you a wrong value, and the
result is a bug that only shows up on the server. Checking the file takes seconds.
A .env file usually holds secrets and must not go into version control. The tool lists the variables that look sensitive by their name, such as those with PASSWORD, SECRET, TOKEN or KEY. Its most useful trick is the .env.example option, which turns your file into a list of names with empty values, safe to commit so that others know which variables the project needs. You can also get a copy with the values replaced by asterisks to share for support.
The check follows the widely used conventions of dotenv-style libraries. Some tools have extra features, such as variable expansion
with ${OTHER}, that are not checked here. Because a .env file holds secrets, nothing you paste is sent anywhere: it is checked in your
browser and disappears when you close the page.
More utilities that also run without leaving your browser.