Environment Toolkit
Validate, diff, resolve, and convert .env files — five tools for the dotenv format's real parsing rules and the gotchas that fail silently. All run entirely in your browser.
How these fit together
.env Validator checks a .env file against real dotenv parsing rules — the unquoted # truncation gotcha, duplicate keys, unclosed quotes — bugs that fail silently instead of throwing. Environment Variable Diff compares two .env files (or a .env.example template against a real one) using their actually-resolved values, not raw text. .env to YAML and YAML to .env convert between the two formats in either direction, with every value safely quoted so it round-trips as a string regardless of what it looks like. And where .env Validator only flags a ${VAR} reference as something plain dotenv won't expand, Environment Variable Resolver actually expands it — chained across any number of hops, with circular references caught instead of silently breaking.
.env Validator
Check a .env file for the dotenv parsing gotchas that silently corrupt values — # truncation, duplicate keys, unclosed quotes.
Environment Variable Diff
Compare two .env files — catch a variable your template declares that never got set, or a value that quietly drifted.
Environment Variable Resolver
Expand ${VAR} references between variables in the same .env-style set, chained across hops.
.env to YAML
Convert a .env file to a YAML mapping, with every value safely quoted so it round-trips as a string.
YAML to .env
Convert a YAML mapping (or a Compose-style KEY=VALUE list) to a .env file, with every value safely quoted.