> For the complete documentation index, see [llms.txt](https://docs.winga.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.winga.me/import-guides/importing-from-dotenv.md).

# Importing from a .env file

The fastest way to get a batch of flags into Winga is to import a `.env` file. There's nothing to connect — you paste or drop the file straight into the import wizard.

***

### 1. Open the import wizard

The import wizard lives on a project's **Flags** page. Open the project you want to import into, go to its **Flags** page, and start an import. Choose **Import from .env**.

***

### 2. Paste or upload the file

Paste the contents of your `.env` file into the box, or drop the file onto it. Winga parses it line by line — every `KEY=value` line becomes a candidate flag. The wizard shows a live preview of the keys it found so you can pick which rows to import before continuing.

***

### 3. There is no "secured" concept for .env files

Unlike the provider importers (GitHub, GitLab, Bitbucket, Vercel), a `.env` file has no notion of secured or sensitive variables — it's plain text, and Winga reads every value. So when you import from `.env`, **all values are available to import**, and the **Import values too** option in the configure step is always enabled.

Because the file may contain real secrets, importing values is still **off by default**. Only turn it on when the file holds test or example values — a `.env` full of production API keys should not have its values seeded as flag defaults.

***

### 4. Configure and import

In the configure step you can:

* choose which environments the imported flags are enabled in,
* optionally import the parsed values as flag defaults (off by default), and
* optionally convert the imported keys to the project's flag-key naming format.

Press **Import** to create the flags.