.env Editor

How to use it

1. Paste .env content into the input box and press Parse. Keys and values appear as editable rows, comment lines stay as comment rows.
2. Pick a mode: .env to JSON for config review, .env to .env to apply your edits, or JSON to .env to go the other way.
3. Use Add row and Add comment to extend the file; the trash button on each row removes it.
4. Press Mask values before sharing your screen — the dots replace what is displayed, not what is stored.
5. Copy the output, or download it as .env or env.json.

Quoting is handled both ways: double quotes may contain \n, \t and escaped quotes, single quotes are literal, and an unquoted value ends at an inline # comment.

Common use cases

• Cleaning up a messy env file — sort out keys that grew quoted values and stray inline comments over time.
• Preparing a deployment payload — convert the file to JSON when your platform takes config as an object.
• Reviewing config on a call — mask the values, walk through the keys, then reveal them again.
• Merging two environments — paste one file, edit rows by hand, and export a clean result for staging.

Why it stays private

Parsing and exporting happen in browser memory. Tokens, database URLs and API keys never leave your device, which is the whole point of editing secrets in a local tool.

FAQ

Q: Does masking remove the real values? A: No. Masking only changes what is displayed, and the value inputs become read-only while masked. The real values are still exported, so unmask before you edit a value.

Q: What happens to comment lines and blank lines? A: Comment lines are preserved and editable, and blank lines are kept as spacers so the section layout of your file survives a round trip.

Q: Are nested JSON values supported? A: In JSON to .env mode, non-string values are written as their JSON text, since .env files hold strings only. Flatten nested objects first if you want one key per field.