Skip to main content
DevStackKit
All tools

.env Parser & Validator

Check a .env file for duplicates, bad names, missing quotes and committed secrets, and compare it with .env.example for missing keys. Private.

.env file

Stays in your browser

.env.example (optional)

Stays in your browser

Findings

Paste a .env file to see its findings.

    Shortcuts: Ctrl+Enter run · Ctrl+Shift+C copy result · / search (use ⌘ on Mac)

    Next steps

    Done here? Use the Send to… menu on the result to carry it on to .gitignore Generator.

    Free Online .env File Validator and Comparer

    Paste a .env file to find mistakes before they cause a confusing error. Add your .env.example to see which keys are missing or not documented. It gives developers a quick browser-based way to solve a focused .env parser & validator task before moving the result into a project.

    How to check a .env file

    Paste the file in the first box. Problems are listed with their line numbers, and the number of variables is shown.

    How to compare with .env.example

    Paste the example file in the second box. Missing keys are the ones a new teammate would forget to set.

    Common mistakes

    • Committing .env to git: add it to .gitignore and share .env.example instead.
    • Spaces around "=": many tools read the name with a trailing space and the variable is never found.

    Frequently asked questions

    What is checked?
    Lines without "=", invalid variable names, duplicate keys, spaces around "=", unquoted values with spaces, quotes that are never closed, empty values and values that look like real secrets.
    How does the comparison work?
    Paste your .env on the left and the .env.example on the right. You see keys the example needs that your .env lacks, keys you have that are not documented, and keys that are empty in your .env.
    Are my values uploaded?
    No. Everything is checked in your browser. Even so, avoid pasting production secrets into any website: remove or blank the values first.
    Does "Make .env.example" remove secrets?
    It keeps the names and comments and blanks values for keys that look like secrets. Plain settings such as PORT=3000 or NODE_ENV=production are kept as examples. Read the result before you commit it.
    How do I use this .env parser & validator tool?
    Use the interactive controls above; processing stays in your browser and the result is intended as a practical starting point for development work.

    More DevOps & Network

    Docker Compose BuilderBuild a Docker setup by picking servicesDockerfile LinterFind problems in a DockerfileKubernetes YAML ValidatorCheck Kubernetes files before deploying.gitignore GeneratorCreate a .gitignore for your projectNginx Config GeneratorCreate a web server config.htaccess GeneratorCreate redirects and HTTPS ruleschmod CalculatorWork out file permission numbersCrontab GeneratorBuild a schedule by picking times

    View all DevOps & Network tools →