Env file inspector

Parse .env files without exposing secrets

Paste a small .env snippet, inspect final key values, duplicate overrides, quoted hashes, multiline values and safety diagnostics. The parser runs locally and masks secret-like values by default.

  • No backend lookup
  • Masked copy by default
  • Quotes and duplicate keys visible

A review surface for configuration text

dotenv.parse turns text into key value pairs. This playground focuses on the parse step: comments, quotes, empty values, export prefixes, duplicate keys and multiline values.

The page does not load .env files, resolve project config, expand variables, decrypt vault data or write to a runtime environment. Treat every real secret as sensitive and use the masked output for sharing.

Parser workbench

Start from a preset, edit the text and compare the masked JSON preview with the final value table.

Clean

URL, feature flag, empty value and port examples without secret-like values.

.env input

Parse result

Final keys4
Masked values0
Duplicate keys0
Duration3 ms

Parsed entries

1APP_HOSTexample.testnone
2FEATURE_CHECKOUTtruenone
3EMPTY_VALUEnoneempty
4PORT4306none

JSON preview

{
  "APP_HOST": "example.test",
  "FEATURE_CHECKOUT": "true",
  "EMPTY_VALUE": "",
  "PORT": "4306"
}

dotenv parsing notes

parse is not config

parse reads text and returns key value pairs. config loads files and populate writes values into a trusted runtime. This public route stays on the parse side only.

Quotes change comment rules

Unquoted # text is treated as a comment, while single, double and backtick quoted values keep # as part of the value.

Mask before sharing

Key names and credential-like values are masked by default. Revealing is only a local UI state for the current page session.

Use these routes when configuration text becomes schema, YAML, dependency policy or browser support policy.