/text local tool
.env Parser
Audit keys without executing shell syntax, then export redacted JSON or a scrubbed .env.example.
Local execution receiptinput path disclosedTool content stays out of MonoTools URLs and API requests.
- Working input
- Browser memory
- Cross-tool handoff
- Session only · 10 min
- URL payload
- Never
- Export
- Explicit action
Verify it: open DevTools Network, clear the log, use the tool, then inspect fetch/XHR requests. Page assets and optional aggregate analytics may use the network; tool input is not included.
Full privacy modelLoading tool...
01
How to use
- 01Paste dotenv text or open a local .env file up to 1 MiB.
- 02Review parse, duplicate-key and likely-secret diagnostics, then keep output redacted unless raw values are explicitly required.
- 03Export JSON or .env.example, compare keys against .env.example, or privately list changed keys across two real environments.
02
FAQ
- Does this execute shell commands or expand variables?
- No. Variable references and command-shaped text are preserved literally and reported; the browser never executes them or reads values from its environment.
- Which dotenv syntax is supported?
- The bounded parser supports comments, optional export prefixes, unquoted values, single or double quotes, safe double-quote escapes and quoted multiline values. Non-portable keys and unsupported escapes are reported explicitly.
- How are duplicate keys handled?
- Every assignment line is retained as evidence. Generated output uses the final assignment for a key and reports all shadowed lines.
- Can I inspect a file that contains secrets?
- Files are read locally and likely credentials are redacted in JSON and the inventory by default. Reports and .env.example output never contain source values; raw Secret Scanner handoff is explicit.
03