Paste .env content into an editable table, diff it against a .env.example template, and export normalized files; everything stays in local memory
FAQ
Is my .env content stored or uploaded?
No. Everything is parsed and edited in browser memory only, never written to disk or sent to a server, and it is cleared on refresh. Still, avoid pasting real production secrets.
What does the invalid name warning mean?
Keys must start with an uppercase letter and contain only uppercase letters, digits and underscores. Invalid ones are flagged in the table and can be fixed before export. Comment lines and unrecognized lines are skipped when parsing.
All data is processed locally in your browser. Nothing is uploaded.