Securely parse, edit, and format your .env files directly in the browser. Sort keys
alphabetically, identify duplicates, and safely format your environment variables. No data is sent to a server.
Try:
ENV File Parser / Editor
Parse · edit · validate · diff ·
exportDev Tools
Raw .env
Paste a .env file or click Sample
Visual Editor
Parse a .env file to edit entries visually.
Total
0
Set
0
Empty
0
Duplicates
0
Secrets
0
File A
File B
Diff Result
■ Only in A■ Only in B■ Changed■ Same
Paste two .env files above to compare them.
Advertisement
Parsing
Paste any .env file into the left panel. Handles quoted values, inline
comments, blank lines, and section headers. The visual editor updates instantly.
Visual Editor
Click any key or value to edit inline. Changes sync back to the raw panel in real time.
Add rows with + Add, delete with ✕. Search to filter keys instantly.
Validation
Red border — duplicate key Amber border — empty value Purple badge — detected secret
Keys are linted for SCREAMING_SNAKE_CASE
Secret Masking
Fields with key names containing SECRET, KEY,
TOKEN, PASSWORD, PRIVATE are auto-masked. Click 👁 per row or Mask
all globally to toggle.
Export
Copy .env — copies raw file .env.example — all keys, values blanked Download — saves as .env
All exports preserve comments and order
Diff Mode
Paste two .env files to compare them. See keys only in A (red), only in B
(green), in both but changed (amber), or identical (grey).
Advertisement
How to use
Open the tool and enter your data or select options.
Adjust settings to see real-time updates.
Copy the generated result to your clipboard.
Frequently Asked Questions
Is my data safe?
Yes!
This tool runs entirely in your browser. Your environment variables and secrets are never sent to any server.
What is a .env file?
A
.env file is a simple text file used to define environment variables for a project, commonly used with the
dotenv library.
Can it handle multiline values?
Yes,
standard parsing rules apply. Values enclosed in quotes can contain newline characters.
Did you know?
The concept of environment variables dates back to 1979 with Version 7 Unix.
The Twelve-Factor App methodology heavily advocates storing configuration in the environment.
You should never commit a .env file to a version control system like Git.