CSV to .env Converter

Configuration that starts life in a spreadsheet rarely stays a spreadsheet for long. Vault exports, data-team handoffs and legacy config sheets all come out as CSV — and end up as a KEY=value file. Converting by hand or with a naive split is where data dies: a value containing a comma vanishes into an extra column, an exported quote survives intact, or a semicolon-delimited file produced by a European Excel export greets you with one giant row.

The CSV to .env Converter parses CSV properly. It understands quoted fields, escaped quotes, embedded delimiters and multi-line quoted values, and handles comma, semicolon or tab delimiters. Choose which column is the key and which carries the value — or flip on header-row mode and use the column names directly. Output highlights the first two columns by prefixing the value column with value= for clarity.

Everything runs in the browser: no uploads, no account, deterministic output you can review line by line before saving.

• Real CSV parsing: quoted fields, escaped quotes, embedded delimiters.
• Three delimiters: comma, semicolon or tab.
• Header-row mode: first row names the key/value columns.
• Manual column choice: pick any columns as key and value.
• Key validation: valid .env keys; bad rows flagged.
• Duplicate detection: repeated keys reported by row.
• Copy or download: clipboard or a .env file in one click.
• Private: all conversion happens in your browser.

1. Paste your CSV content into the input box, or load the sample.
2. Pick the delimiter used by the file.
3. Choose a mode. Header row uses the first row as column names; Manual selects key and value columns by number.
4. Click Convert. The .env output appears on the right.
5. Review flagged rows, then copy or download the file.

Example 1 — Secret sheet export. An ops team exports credentials from a shared sheet and converts the two-column CSV into a .env, with quoted values containing commas preserved exactly.

Example 2 — EU regional CSV. A developer receives a semicolon-delimited export from a French colleague and switches the delimiter to semicolon — everything parses on the first pass.

Example 3 — Large config table. A data team hands over 400 rows of key/value configuration; the header-row mode maps the VALUE column correctly and produces a clean .env.

Example 4 — CI migration. A platform engineer converts a legacy configuration sheet into a .env committed to the repo, replacing a fuzzy step-by-step wiki.

Example 5 — Vault batch import. An admin pulls vault keys as CSV and turns them into a .env for local development, flagging the two duplicate keys instantly.

• No data mangling: quoted commas and embedded quotes survive.
• Works with exports: comma, semicolon and tab all supported.
• Flexible mapping: header row or explicit column numbers.
• Clean keys: validation and duplicate detection built in.
• Deterministic: same CSV, same .env, easy to review.
• Private & free: browser-only, no account.