Dotenv Official installs statistics

<h1>dotenv-vscode <a href="https://marketplace.visualstudio.com/items?itemName=dotenv.dotenv-vscode"><img src="https://img.shields.io/badge/VS%20Marketplace-Install-blue" alt="Install from VS Marketplace"></a></h1> <img src="https://dotenvx.com/logo-original.png" alt="dotenv" align="right" width="200" />

Official Dotenv Extension – from the creator of dotenv.

• auto-cloaking
• auto-completion
• secret peeking
• syntax highlighting
• NEW: decryption peeking (for encrypted .env files)

<a href="https://marketplace.visualstudio.com/items?itemName=dotenv.dotenv-vscode"><img src="https://img.shields.io/badge/VS%20Marketplace-Install-blue" alt="Install from VS Marketplace"></a>

 

auto-cloaking

<img alt="auto-cloaking demo" src="https://github.com/user-attachments/assets/53d25529-ab04-4c5d-8a74-ae6cb39b93cf">

 

auto-completion

<img alt="auto-completion demo" src="https://github.com/user-attachments/assets/ad2b730e-d32f-4573-acd8-f7491bf48e25"/>

 

secret peeking

<img alt="secret peeking demo" src="https://github.com/user-attachments/assets/f4441d8d-8765-4849-b947-6ce36412ca03"/>

 

syntax highlighting

<img alt="syntax highlighting demo" src="https://github.com/user-attachments/assets/f276e078-c60e-4cb2-9664-f6750d8387c9"/>

 

decryption peeking

<img alt="decryption peeking demo" src="https://github.com/user-attachments/assets/ba5ec15b-1be8-40b1-902d-116fdbf81591"/>

 

FAQ

<details><summary>Does it automatically cloak my secrets? <strong>Yes.</strong></summary><br>

By default, open a .env file and its values start masked.

Click Toggle auto-cloaking at the top of the file or run Dotenv: Toggle auto-cloaking from the Command Palette to reveal or hide them.

Switching tabs hides them again in the Dotenv Editor when auto-cloaking is enabled. Set dotenv.enableAutocloaking to false to keep values visible, including after reopening files or switching tabs. This disables the cloaking feature and removes its toggle controls. Changes apply to open editors immediately.

 

</details> <details><summary>Does it support .env variants? <strong>Yes.</strong></summary><br>

.env, .env.example, .env.development, .env.staging, .env.production, other .env.* files, *.env, and .flaskenv are supported.

 

</details> <details><summary>Can I autocomplete environment variables? <strong>Yes.</strong></summary><br>

Start typing process.env. or your language's environment-variable expression.

Suggestions come from your dotenv files, with values masked and source filenames shown.

 

</details> <details><summary>Can I reveal a value inside an autocomplete popup? <strong>Yes.</strong></summary><br>

Open a suggestion's details and click Reveal value. Click Hide value to mask it again.

Only that source's value is revealed. The suggestion row stays masked, and your secret-peeking setting stays unchanged.

 

</details> <details><summary>Can I peek at secrets without opening my .env file? <strong>Yes.</strong></summary><br>

Hover over a reference such as process.env.SECRET_KEY or ENV["SECRET_KEY"].

Every new hover or expanded autocomplete peek starts cloaked. Click Reveal value to reveal that popup, or Hide value to cloak it again. Editor cloaking toggles never reveal peek values. Uncheck Dotenv: Enable Secretpeeking to disable dotenv hovers and in-code Reveal actions, including the expanded value details in autocomplete. Completion suggestions remain available with masked values.

 

</details> <details><summary>Can I peek at encrypted values with dotenvx? <strong>Yes.</strong></summary><br>

In the Dotenv Editor, hover over an encrypted: value and click Decrypt value. The file stays encrypted.

Click Hide value, leave the popup, or switch tabs to clear the displayed plaintext.

You'll need a saved file, a trusted workspace, and the dotenvx CLI installed locally. The CLI isn't bundled with this extension.

Install it using the dotenvx installation instructions.

dotenvx finds the matching private key through its usual lookup, such as .env.keys or its key store. A key stored only in GitHub Actions isn't available locally.

If dotenvx isn't on your PATH, set dotenv.dotenvxPath to its executable.

 

</details> <details><summary>Does it highlight .env syntax? <strong>Yes.</strong></summary><br>

Variable names, values, comments, and quoted strings have syntax highlighting. The Dotenv Editor also highlights numeric values.

 

</details> <details><summary>Does it support languages other than JavaScript? <strong>Yes.</strong></summary><br>

Auto-completion and secret peeking support JavaScript, TypeScript, Ruby, Python, PHP, Go, Java, .NET (C#, F#, Visual Basic), C/C++, Julia, Erlang, Perl, Swift, Clojure, Rust, Dart, Kotlin, and Elixir.

Values come from your dotenv files, rather than the running application's environment.

 

</details> <details><summary>Does it support importing env from node:process? <strong>Yes.</strong></summary><br>

Both node:process and process imports work, including named aliases and multiline imports.

import { env } from 'node:process'
console.log(env.SECRET_KEY)

import { env as environment } from 'node:process'
console.log(environment.SECRET_KEY)

 

</details> <details><summary>Does it support .NET? <strong>Yes.</strong></summary><br>

C#, F#, and Visual Basic support Environment.GetEnvironmentVariable, including System.Environment and the overload with an EnvironmentVariableTarget.

Type ( or " in the first argument, or request completion while typing a name. Hover over the name to peek at its value.

var secret = System.Environment.GetEnvironmentVariable("SECRET_KEY");
```…