Env Variable Extractor

Choose the input and parsing options

Paste content in Paste .env content below, or use the file area labeled Drop a .env file here and browse files. The picker lists .env, .txt, and text/plain files.

• Leave Mask secret-looking values by default enabled to mask matching values when the table is first shown.
• Use Show blank/comment/unparsed lines in table to control whether non-entry rows appear. Hiding them changes the display, not the parsed data.

Parse and review the table

1. Enter or load the dotenv text.
2. The result updates automatically as soon as usable content is available.
3. Review the summary, table rows, and any parsing warnings.
4. Click Clear to remove the current input or result state.

Reveal all masked values is available for the parsed result. The copy and export controls remain disabled until parsing produces a result.

Understand supported dotenv syntax

The parser applies the dotenv dialect implemented on this page:

• Export prefix: an optional leading export before the key, common in shell-sourced env files.
• Keys: must start with a letter or underscore and contain only letters, digits, underscores, dots, or hyphens.
• Blank lines and comments: a line that's empty (or whitespace-only) is a blank row; a line whose first non-whitespace character is # is a comment row. Both are preserved as their own rows rather than discarded.
• Unquoted values: run to the end of the line. A space followed by # starts an inline comment, which is captured separately from the value. Unquoted values are always single-line - there is no line-continuation syntax.
• Single-quoted 'value' and backtick `value`: treated literally - no escape-sequence processing - and may span multiple lines up to the matching closing quote.
• Double-quoted "value": supports \n, \r, \t, \\, \", and \$ escape sequences, and may also span multiple lines.
• Duplicate keys: every occurrence is kept. The first occurrence of a key is marked "active," matching the common dotenv convention that the first definition wins and later ones are shadowed - but all are shown.

Raw vs. Parsed Values

Each entry row shows a parser-captured raw value and a parsed value. The raw field can include quote delimiters, but it is not a byte-for-byte copy of the source: the parser normalizes some whitespace. The parsed field applies the supported quote and escape rules, so "line1\nline2" becomes an actual two-line string.

Secret Masking and Reveal Controls

Keys that look secret-related - such as KEY, TOKEN, SECRET, PASSWORD, AUTH, or CREDENTIAL - can be masked in the raw and parsed columns. Longer masked values show edge characters; values of four characters or fewer may be fully masked. Reveal one row with its eye control, or use Reveal all masked values. This is a key-name heuristic, not a complete secret detector.

Copy or export parsed entries

After parsing, choose Masked or Unmasked from Export values:. Selecting unmasked values requires I want to export unmasked secret values. Then use Copy JSON, Copy CSV, Export JSON, or Export CSV.

These copied and downloaded results contain entry rows and their exported fields. Blank, comment, and unparsed display rows are excluded, even when Show blank/comment/unparsed lines in table is enabled.

What This Tool Does Not Do

This tool parses dotenv syntax; it does not resolve ${VAR} or $VAR interpolation, and it does not validate values against a schema. Lines it cannot confidently interpret can appear with inline warnings. Its parsing rules are specific to dotenv conventions such as quoting, export prefixes, and duplicate keys.

Privacy & Security

Parsing and masking use browser-local processing, and the page creates downloads in the browser. The implementation contains no upload calls. Account requirements and usage limits are not established by this page.

Frequently Asked Questions