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.

I've been using this feature since its launch, and it is like a dream coming true. I'm hoping for great new improvements on that.Not having any secrets in plain text on my storage and principally not having to change each project/service to integrate with 1Password (like using packages or plugins) is just great.Here are my wishes:Reference existing 1Password items so they won't be duplicated inside 1Passport (TOKEN="{{op://vault/service/token}}").Reference other variables (U="user", P="password", DB="url://$U:$P").Sorting the environment variables (alphabetically, manually).Option to make the mount file read-only.Support for project environments (like production, staging, dev, …) so a variable can inherit its value from other environments (see Infisical ;).Better "project/environments" organization (folders, tags, sorting, description, …).Ability to programmatically specify and mount the file destinations locally.CLI full management.Use/select templates for the mounting files.Great job!

Sadia_A1P

1Password Employee

Question

Introducing new .env file support in 1Password

Forum|Forum|9 months ago
September 30, 2025
17 replies
2439 views

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

Show previous replies

mprofitl

This is excellent. Thank you for the new feature! Sharing Dotenv in the team over our file server is ending.

For production we still need Dotenv files on the website projects’ webservers. It would be great to have an export button that writes a file to a given destination. Otherwise we still need to keep a copy.

phildmno

You can use varlock in production (https://varlock.dev/plugins/1password/#loading-1password-environments ) or any server/service that doesn't currently have a destination and that way you're not writing plaintext env files on your servers either!

C

cussiol

I've been using this feature since its launch, and it is like a dream coming true. I'm hoping for great new improvements on that.

Not having any secrets in plain text on my storage and principally not having to change each project/service to integrate with 1Password (like using packages or plugins) is just great.

Here are my wishes:

Reference existing 1Password items so they won't be duplicated inside 1Passport (TOKEN="{{op://vault/service/token}}").
Reference other variables (U="user", P="password", DB="url://$U:$P").
Sorting the environment variables (alphabetically, manually).
Option to make the mount file read-only.
Support for project environments (like production, staging, dev, …) so a variable can inherit its value from other environments (see Infisical ;).
Better "project/environments" organization (folders, tags, sorting, description, …).
Ability to programmatically specify and mount the file destinations locally.
CLI full management.
Use/select templates for the mounting files.

Great job!

C

collinbentley1

Echoing:

Sorting the environment variables alphabetically --> annoyance when you have a large list of environments across the team

chris__hayes

Any plans on adding "Offline mode" to the CLI?

`op run` is still going down with 1Password outages as demonstrated today. This is like the 4th or 5th time I've been locked out of my env variables with 1Password due to an outage. As a dev, it's become a bit of a liability.

L

Lars

Great feature. Would love to see support for Docker (compose)!

J

jonashilmersson

I would like to have this feature on Windows.

J

jalaziz

Went to setup 1Password Environments only to realize I cannot share environments with groups :-(.

If it was "built for teams", how are we supposed to share environments across a team? Individual sharing doesn't scale and is difficult to manage.

T

tom_isaacson

When will it be released into the Linux CLI tool? Currently I can't use it on Github Actions because https://github.com/1password/load-secrets-action doesn't include environment support.

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded