Env

The Env editor opens dotenv files and starts in Form. It claims the conventional .env name and its variants — .env.local, .env.production, and any .env.<suffix> — as well as named files that use the .env extension, like config.env.

Interactive Env editorEdit keys and values as a form, keep secrets masked, or drop to the raw file. Nothing here is saved to a tray.

Try the editor

Views

• Form lists every KEY=VALUE assignment as an editable row. Rename a key, edit its value, copy either side, or delete the row. Add variable appends a new entry to fill in.
• Raw exposes the file’s source directly, including comments, blank lines, export prefixes, and quoting.

Pending edits are flushed before the view switches, so each view always reflects the latest content.

Hiding values

A .env file usually holds secrets, so values start hidden behind dots. Toggle Show values / Hide values in the toolbar to reveal or re-mask every value at once. Copying a value always copies the real text, masked or not.

What is preserved

Comments (# …), blank lines, export prefixes, and the file’s line endings are kept. Only the specific line you edit is rewritten — quoting it as needed when a value gains spaces, #, or quotes — so every assignment you leave untouched round-trips byte-for-byte. Double-quoted values honor \n and \t escapes; single-quoted values are treated literally.

Undo and redo

Cmd/Ctrl+Z and Cmd/Ctrl+Shift+Z undo and redo across both views. See Getting started for the full model.