Format, sort, and validate .env files. Auto-detects secrets and generates a safe .env.example template. 100% browser-based, nothing uploaded.
No. Parsing, formatting, and secret detection all happen in your browser using plain JavaScript regexes. Nothing is sent to a server. You can verify by opening DevTools → Network tab while you paste.
Any key whose name matches KEY, TOKEN, SECRET, PASSWORD, PWD, API, PRIVATE, DSN, or AUTH (case-insensitive). The tool highlights these and replaces their values with placeholders in the generated .env.example. Treat the heuristic as a starting point, not a guarantee — review manually.
Committing .env to git leaks production secrets. The standard practice is to commit .env.example (with empty or placeholder values) so teammates know which variables they need to define locally — without exposing real credentials.
Most .env parsers treat values literally — VAR=hello world keeps the space. But values containing #, \n, or quotes need to be wrapped in double quotes for safe parsing across dotenv libraries. The 'quote when needed' option handles this automatically.
Not yet. This formatter focuses on the common case: KEY=value pairs, one per line, with optional comments. For advanced syntax (multiline, ${'