.env editor

Parse .env files — list entries, spot duplicates, export prefixes, and invalid lines.

Values are never displayed — only key names, value lengths, and issue flags leave the parser. Duplicate keys are flagged with their line numbers (the last one wins in most loaders). Nothing is sent anywhere.

Everything runs in this browser.

How to use

  1. Paste .env text.
  2. Parse it.
  3. Review the entry table and warnings.

What it supports

KEY=value lines, # comments, blank lines, `export ` prefixes, and single/double-quoted values. Values are never shown — the report lists keys, value lengths, and issue flags only. Duplicate keys are flagged with line numbers (last wins). Input up to 1,000,000 characters / 20,000 lines. Variable expansion (${VAR}) and multiline values are not supported.

Related tools

Related guides