sade.dev
TR EN
Tool

.env Parser

Splits dotenv-format content into a key/value table. Masks sensitive fields.

This tool runs in your browser. No data leaves your device.

Caution: Think twice before pasting .env contents with sensitive values here. Everything runs in your browser, but it is not a good habit.

How It Works

.env files look “simple,” but there are meaningful differences between parser implementations. This tool runs a parser that follows the common conventions (php-dotenv, node-dotenv, godotenv).

Supported patterns

  • KEY=value — the basic form.
  • KEY="value with spaces" — double-quoted; resolves \n, \t, \\, \" escapes.
  • KEY='value' — single-quoted; raw, no escapes.
  • export KEY=value — the export prefix is dropped for bash compatibility.
  • # comment line or KEY=value # inline comment (only for unquoted values).
  • KEY= — empty value.

Common mistakes

  • Spaces around =: KEY = value — some parsers (godotenv) accept this, most reject it. Stay on the safe side: no spaces around =.
  • Unquoted spaces: KEY=hello world — is it hello world or hello? It depends on the parser. Always use quotes.
  • Multi-line values: done with \n escapes inside double quotes; real line breaks are not supported by most parsers.

Masking sensitive values

The tool masks the values of keys containing one of the words key, secret, token, password, auth, credential. This is for appearance only — not real protection. Pasting .env content into a browser exposes sensitive values to:

  • Browser history,
  • The clipboard,
  • Screen sharing,
  • Browser extensions.

This tool does not send sensitive values anywhere, but even so, don’t paste your production secrets here. Work with dummy/test data.

Privacy

All parsing happens in your browser. Your data never leaves it.