# List

Show which environment variables exist, and where.

### Syntax

```
$ vela env list [-t <target>]
```

Without `-t`, every scope at once: the local `.env` by name, then one table per bound server with a column for the `all` layer, the `preview` layer and each target there. A public value is shown, a secret as `••••`, and an instance column that does not set a key itself names the layer its value comes from:

```
$ vela env list

  Environment (root@203.0.113.10)

                       all     preview    production  preview:feature-maps
    PUBLIC_CMS_URL     —       —          https://…   —
    STRIPE_SECRET_KEY  —       ••••       ••••        ↑ preview
    VELASTACK_API_KEY  ••••    —          ↑ all       ↑ all
    WHATSAPP_MODE      —       dev        velastack   ↑ preview
```

With a target, the environment as that copy of the app sees it, each key with the layer it comes from:

```
$ vela env list -t production
$ vela env list -t preview:feature/maps
$ vela env list -t all
```

`-t local` lists the names in `.env`, never their values, so the output is safe to paste wherever it came from.

See [env](/docs/env) for the full option list.