.env Viewer
Inspect, sort, and mask .env files.
About .env Viewer
Every project accumulates a .env file that nobody has read end to end since the first sprint. Values get overridden further down the file, secrets sit in plain text while someone screen shares, and nobody remembers which variables are still used. This viewer reads the file and lays it out as a table: key on the left, value on the right, line number for reference. Keys whose names look sensitive, such as those containing PASSWORD, TOKEN, SECRET, or KEY, have their values covered by default until you reveal them. If the same key appears twice, the viewer counts the occurrences and points at every line, because in almost every runtime the last definition silently wins. The raw text stays editable on the left, so fixes can be made and downloaded on the spot. Parsing happens in the browser only.
How to Use .env Viewer
Open your .env file
Click Open .env file to load one from disk, or paste the contents into the left box. Comments and blank lines are ignored by the parser.
Read the parsed table
Each variable appears as a row with its key, value, and source line number. Values of keys with sensitive-sounding names are masked until you untick Mask secret values.
Check for duplicate keys
A red banner lists how many keys are defined more than once, and each duplicate row shows a count with the exact lines involved. Remove the stale definitions so the file behaves the same everywhere.
Sort, fix, and download
Tick Sort keys A to Z to alphabetize the table for review. Edit the raw text on the left to fix problems, then click Download .env to save the corrected file.
Why Use .env Viewer: Common Use Cases
Reviewing config before a release
Walk through every variable a service will load, confirm nothing surprising is set, and catch duplicated keys that would override your intended values at runtime.
Sharing config structure safely
Screenshot or present the table with masking on, so teammates see which variables exist without exposing live credentials during a call.
Migrating to a new server
Compare the variable list an old deployment uses against a fresh file, so nothing is forgotten when moving an app to a new host or container image. A quick YAML to JSON pass helps when the new host expects a different config format.
Onboarding a new developer
New team members can see which variables a project expects, which are secrets, and what a sensible structure looks like, before asking for real credentials.
.env Viewer Specifications
| Input Formats | .env text, dotenv-style files, Plain paste |
|---|---|
| Output Formats | Parsed key-value table, Edited .env download |
| File Size Limit | No strict limit (dependent on device memory) |
| Processing Engine | 100% Client-side (Runs locally in your browser) |
| Data Retention | Files never leave your device |
| Batch Processing | Single file processing |
Tips for .env Viewer
Values wrapped in single or double quotes have the quotes removed in the parsed view, which is what most dotenv libraries deliver to your application.
Inline comments after a value are stripped from the display. If you rely on
KEY=value # notestyle notes, remember the note is not part of the value.Masking is based on the key name, not the content. A credential stored under a bland name like
APP_SETTINGwill not be masked automatically, so rename sensitive keys to include SECRET or TOKEN.When a file is beyond repair, rebuild it clean and compare with Text Diff to make sure no variable went missing in the rewrite.
Pair this with .gitignore Generator to keep
.envout of version control, and add a committed.env.examplewith empty values instead.
Frequently Asked Questions
Is my .env file uploaded to a server?
No. The file is read in your browser and parsed by local JavaScript. Environment files are the most sensitive text in most projects, which is exactly why this tool was built to work entirely offline.
Which value wins when a key is duplicated?
In nearly every dotenv implementation, the last assignment in the file wins. That makes duplicates dangerous in a subtle way: the value you see at the top of the file may not be the value your app receives. The viewer flags every duplicate so you can decide which line to keep.
How are quotes in values handled?
Single and double quotes are stripped from the displayed value, matching common library behavior. This shows what your application will actually receive rather than what the file literally contains.
Does it support variable interpolation like ${OTHER_VAR}?
The text is shown as written and not expanded, so you can see the reference itself. Knowing that a value depends on another variable is usually the important part during a review.
Can I edit values in the table directly?
Editing happens in the raw text box on the left, and the table refreshes as you type. This keeps one source of truth, so the downloaded file is exactly the text you edited.
What file types can I open?
Anything text based: .env, .env.local, .env.production, or a pasted block from a terminal. The parser only cares about KEY=VALUE lines, comments, and blank lines.