DevOps Generators

Env Validator

All tools

Lint a .env file, diff it against another environment, and convert it for the platform you deploy to.

How it works

Four simple steps

1

Paste a .env file

Add KEY=value lines, comments, and export prefixes.

2

Scan for issues

Catch duplicates, empty values, and secret-looking patterns.

3

Diff two env files

Compare staging vs production keys before you deploy.

4

Export for your stack

Generate Docker env, K8s Secret YAML, or GitHub Actions lists.

Env Validator

About Env Validator

The app boots on your laptop and crashes in staging with a missing variable. Somewhere between the two .env files a key was renamed, duplicated or left empty. Paste both here and the difference shows up right away.

Each line is parsed as KEY=value, with support for quotes, inline comments and an export prefix. The checklist fails duplicate keys, invalid names, unterminated quotes and lines without an equals sign, and warns on lowercase keys, empty values, unquoted spaces or shell characters, and ${VAR} references to undefined keys. Values are matched against credential formats such as AWS key IDs, GitHub, Slack, SendGrid and Stripe live keys, Google API keys, private key blocks and URLs with an embedded password, and matches are shown redacted.

Tick Compare with a second file to list keys missing from file B, keys only in B, and values that differ. The diff prints the first 40 characters of differing values in clear text, so keep it off shared screens. Exports cover a Docker env file, docker run flags, a compose environment block, a Kubernetes Secret (base64) or ConfigMap, gh secret set commands and shell exports. The gh commands embed the values, which then land in your shell history; gh secret set -f with a file avoids that.

Parsing and export run in the page. Going from YAML config to env lines is the job of YAML to ENV, the Base64 decoder reads encoded Secret values, and the pattern-based secrets scanner handles text that is not in .env format.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

No. The values are only base64 encoded, which anyone can reverse. Keep the generated manifest out of Git, or use a sealed or external secrets system for real credentials.

Shells accept export KEY=value, but docker-compose and several dotenv libraries read export as part of the key name. The warning helps you spot files that work with source but fail inside containers.

The AWS secret key pattern only runs when the key name looks like one, for example aws followed by secret, or secret followed by access. A random 40-character string under another name is too common to flag on its own.

View more FAQs

Related tools

View all

Kubernetes Manifest Studio

Generate Deployment, Service, and Ingress YAML with a drift checklist.

Open

K8s Inspector

Summarize Kubernetes YAML kinds, names, and labels.

Open

K8s Resource Diff

Diff two Kubernetes manifests locally.

Open

K8s Manifest Splitter

Split multi-document YAML into one file per resource.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools