🔐

Rhad ac am ddim ENV File Validator

Lint a .env file for duplicate keys, bad spacing, and unquoted values — then get a cleaned, sorted version and a ready-to-commit .env.example. Runs in your browser.

Runs in your browserNo sign-up, no pop-upsNid oes angen mewngofnodiAm ddim am byth

.env contents

💡 Catches duplicate keys, spaces around =, unquoted values, and naming-convention issues — then gives you a cleaned, sorted file and a ready-to-commit .env.example. Your secrets are parsed entirely in your browser and never uploaded.

Optimize for your platform

Generate a .env.example Debug a Broken .env File Clean Up a Messy .env Enforce .env Naming Conventions Validate .env Before Deploying

Sut Mae'n Gweithio

A malformed .env file causes confusing config bugs — a duplicate key, a stray space around "=", an unquoted value with a space. This lints your file and cleans it up, all locally (important, since .env files hold secrets).

1
You paste your .env
Each line is parsed: comments and blanks are skipped, "export" prefixes handled.
2
It checks for problems
Duplicate keys, spaces around "=", invalid key names, non-uppercase keys, empty values, and unquoted values containing spaces or "#" are flagged with line numbers.
3
It produces a cleaned file
Keys are de-duplicated (last value wins), sorted alphabetically, and values are quoted where needed.
4
And a .env.example
The same keys with blank values — ready to commit so teammates know which variables to set, without leaking secrets.

.env files are full of secrets — API keys, database passwords. This tool parses everything in your browser and never uploads a thing, so it's safe to paste a real file.