Share .env Files Securely
Transmit .env file contents to teammates through encrypted links instead of committing secrets to repositories.
The problem
Environment files contain API keys, database URLs, and service tokens all in one place. Sharing them over Slack or committing them to a repository — even a private one — creates a concentrated target. A single .env leak can compromise every external service your application connects to.
How Vaulted helps
Paste your .env contents into Vaulted and share an encrypted link that auto-expires. AES-256-GCM encryption runs entirely in your browser, and the decryption key never touches the server. This eliminates the risk of .env secrets sitting in message histories or version control.
How to do it
- Paste your .env file contents into Vaulted
- Configure a view limit and expiration period
- Send the encrypted link to the developer who needs the config
- They open the link, copy the variables, and the link is destroyed
Share .env files from the terminal
Developers can skip the browser entirely with the Vaulted CLI. Pipe your .env file directly: cat .env.production | npx vaulted-cli --views 1 — or pass a file path: npx vaulted-cli --file .env.local --expires 24h. Same encryption, same self-destructing links. Install from npm: npm install -g vaulted-cli.
Share .env files in GitHub Actions
Use the Vaulted GitHub Action to share environment configs in CI/CD: uses: vaulted-fyi/share-secret@v1 with your .env contents as the secret. The action encrypts locally and outputs a shareable link. Available on GitHub Marketplace.