Env Studio
Parse, lint, compare, mask, and export .env files — spot duplicates, missing keys, and secrets, then ship a clean .env.example.
Paste, upload, drop a file, or type — everything is parsed live, entirely in your browser.
0 chars · 0 lines
Variables
0 vars · 0 groups · 0 secrets
No variables yet
Variables will appear here as you type.
Everything runs locally in your browser. Your variables and secrets never leave your device.
Env Studio FAQ
- Is my .env file uploaded anywhere?
- No. Parsing, linting, comparing, masking and exporting all run in your browser, so your variables and secrets never leave your device.
- What does the audit check?
- Duplicate keys, malformed lines, empty values, placeholder values such as changeme, weak secrets, and secrets behind client prefixes like NEXT_PUBLIC_ or VITE_ that would be shipped to the browser.
- How do I find keys missing from my .env.local?
- Put the reference file (for example .env.example) in the Editor tab, open Compare and paste the file to check. Keys are listed as missing, extra, different or identical, and you can copy all missing keys at once.
- Which export formats are supported?
- Raw, sorted or prefix-grouped .env, a keys-only .env.example, JSON, YAML, a docker-compose environment block, shell export lines and a Markdown table. Secrets are masked unless you choose to reveal them.
- Does it handle large .env files?
- Yes. Files up to 2 MB can be dropped or uploaded, parsing follows your typing without blocking it, and long lists render 200 rows at a time with a Show more button.