.env File Parser
Paste your .env content and convert to JSON, YAML, bash export statements, or a JS object. Filter keys, copy values, and add variables manually.
| Key | Value | |
|---|---|---|
| NODE_ENV | production | |
| APP_NAME | My Awesome App | |
| APP_PORT | 3000 | |
| DATABASE_URL | postgresql://user:pass@localhost:5432/mydb | |
| DB_POOL_SIZE | 10 | |
| JWT_SECRET | super_secret_key_here | |
| JWT_EXPIRY | 7d | |
| FEATURE_DARK_MODE | true | |
| FEATURE_ANALYTICS | false |
Add Variable
Frequently Asked Questions
What .env syntax does this parser support?
The parser handles all common .env patterns: KEY=value, KEY="quoted value", KEY='single quoted', inline comments after values (KEY=val # comment), blank lines, and full-line comments starting with #. It correctly strips quotes and ignores inline comments.
Can I convert my .env file to JSON?
Yes. Switch to the JSON tab after pasting your .env content and you will see a formatted JSON object with all your key/value pairs. You can copy the entire JSON with one click or filter down to specific keys using the search box.
What is the Export Statements view?
The Export tab generates bash export commands in the format `export KEY="value"` for every variable. This is useful for sourcing environment variables into your shell session or CI/CD pipeline scripts.
Is my .env data sent to a server?
No. All parsing and conversion happens entirely in your browser. Your environment variables — including secrets like API keys and database passwords — never leave your machine. The tool is safe for use with sensitive configuration files.
Can I add variables manually without editing the raw .env content?
Yes. Use the "Add Variable" section at the bottom of the tool. Enter the key and value, then click Add (or press Enter). The variable is appended to the raw .env content and immediately appears in all output views.