Enforce .env Naming Conventions

Check that environment variable names follow UPPER_SNAKE_CASE.

Nid oes angen mewngofnodi

.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.

conventions tips

📐

Lowercase or mixed-case keys are flagged so your config follows the UPPER_SNAKE_CASE convention.

🚫

Invalid key names (bad characters, leading digits) are reported as errors.

🤝

Consistent naming avoids subtle bugs when different tools read the same file.

🔒

Validated locally — your secrets stay put.

Sut Mae'n Gweithio

Ewch i mewn

Enter your data into the tool above. Everything stays local to your browser.

Proses

The tool processes your data instantly in your browser using JavaScript. No server, no waiting.

Lawrlwythwch

Get your result instantly. Nothing is stored after you leave the page — complete privacy.

Pam defnyddio ein un ni?

✓Hollol rhad ac am ddim - dim costau cudd, byth

✓Nid oes angen cyfrif, e-bost na mewngofnodi

✓Nid yw ffeiliau byth yn gadael eich dyfais

✓Dim cyfyngiadau maint ffeil o gwbl

✓Dim dyfrnodau ar unrhyw allbwn

Also check out…

📋

Generate a .env.example

Create a .env.example from your real .env so teamm

🐞

Debug a Broken .env File

Find why your environment variables aren't loading

🧹

Clean Up a Messy .env

Sort, de-duplicate, and normalise an .env file.

⚙️

Validate .env Before Deploying

Catch config mistakes before they reach production

Cwestiynau Cyffredin

Back to ENV File Validator