Today, we’re introducing a first-of-its-kind feature available in the 1Password Desktop app. With the new local .env file destination in 1Password Environments, you can securely use and share .env files across your team, without rewriting how your app loads credentials. Here’s why it matters: Zero plaintext secrets on disk: Secrets are loaded into applications on demand. You can’t accidentally commit them. No cumbersome sharing of secrets: Teammates get instant access - no DMs or copying secrets. Built for teams: Version history, access control, and automatic updates - all in one place. Offline access: No more internet connection required to load secrets from 1Password. Secrets are sourced directly from the desktop app's local cache. Now available in beta on Mac and Linux. Interested to see it in action? Watch the demo video below. Video not displaying? Watch it here. 💬 Share feedback, get swag We want your input on what to build next: CI/CD integrations? Docker support? Something else? 📖 Read the docs to get started 👉 Join the discussion in the 1Password Developer Community 🧢 The first 10 developers to start a discussion on the 1Password Developer Community Hub to share feedback by October 31st will get exclusive 1Password swag. Be sure to tag your post with beta-environments.

Nice feature! It would be even smoother if it supported pasting template files that include 1Password Secret References like:SAMPLE_ENV_VARIABLE="op://sample-vault/sample_item/sample-field"and have them automatically resolved. I know I can manually create a .env file with the resolved values, but having this built-in would make the experience even better. Great work!

ok thanks, we'll test and let you know! It should be an easy update on our end

This is great! If you have docs on library compatibility we're happy to make varlock.dev work with this!

confirmed that it works with varlock.dev, it will load the your `.env.*` files in as overrides and validate it with our `.env.schema`. So a sample integration would like something like this: - 1Pass Env local file destination: `.env.local`- `.env.schema` checked into source control

This is an amazing feature so far, thanks to everyone who made this a reality 👏 ! Here is my feedback.it should be able to pull secrets using secret references from the vault (eg op://something-prod/github-client-id/credential)all my projects now have to live in environments without any sorting capabilityI was using separate vaults before to separate projects the mounted `.env` file is generated but probably should haveenv it was loaded fromtimestamp when it was updatedany other relevant metadata that I am not aware ofoffline access now solves this one i've requested in the past!regarding git, it's probably worth mentioning that they won't be seen because git doesn't support named pipes in the docslocking of your vault and the env file getting removed from disk is just chefs kissfuture looking but if you could support "stages" in environments like alpha/beta/prod (make prod scary and red 😂) Simple demo I spun up for this! 🫶

Sadia_A1P

1Password Team

5 months ago

Introducing new .env file support in 1Password

Today, we’re introducing a first-of-its-kind feature available in the 1Password Desktop app.

With the new local .env file destination in 1Password Environments, you can securely use and share .env files across your team, without rewriting how your app loads credentials.

Here’s why it matters:

Zero plaintext secrets on disk: Secrets are loaded into applications on demand. You can’t accidentally commit them.
No cumbersome sharing of secrets: Teammates get instant access - no DMs or copying secrets.
Built for teams: Version history, access control, and automatic updates - all in one place.
Offline access: No more internet connection required to load secrets from 1Password. Secrets are sourced directly from the desktop app's local cache.

Now available in beta on Mac and Linux. Interested to see it in action? Watch the demo video below.

Video not displaying? Watch it here.

💬 Share feedback, get swag

We want your input on what to build next: CI/CD integrations? Docker support? Something else?

📖 Read the docs to get started

👉 Join the discussion in the 1Password Developer Community

🧢 The first 10 developers to start a discussion on the 1Password Developer Community Hub to share feedback by October 31st will get exclusive 1Password swag. Be sure to tag your post with beta-environments.

beta environments

Forum Discussion

Introducing new .env file support in 1Password

21 Replies

Featured discussions

Meet the 1Password team at KubeCon Europe

Recent discussions

op CLI hangs on macOS Tahoe

How do I use the SSH agent in headless Linux?

Sudo support

the "open" balloon doesn't do anything

Getting rid of my individual account. I have a family account now.