Envarsa
One place for all your .env files
Envarsa keeps a copy of each project’s .env file on your computer. You can find a value
months later, see which projects share a key, and write a working .env.local for a fresh
checkout. Nothing is uploaded anywhere.
Free and open source, for Windows 10/11 and Linux.
# the problem
.env files aren’t in git, so nothing backs them up
Every project has its own, on every machine you’ve used. Delete the folder and the values are gone. The same database URL ends up in several projects, and when you change it in one, the others go stale without anything telling you.
# what it does
What Envarsa does
Every project’s variables, in one library
Add a project by picking its .env file, pasting it, or dropping it on the window. Envarsa
keeps the file exactly as it was, comments included. Each time you add it again, the old version is
kept, so you can look back or restore it.
See where a key is shared, and whether it matches
When the same key appears in more than one project, Envarsa marks it and tells you whether the values match. If you rotate a database password in one project, you can see which others still have the old one.
Set up a fresh checkout from its .env.example
Point Envarsa at a project’s .env.example and it writes a .env.local
beside it, filling in every value it has and leaving the rest blank for you. You see a preview
first. It never writes to the example file itself.
# privacy
Your values stay on your computer
Nothing is uploaded
There’s no account and no server. Envarsa works entirely offline.
The only network request it can make is a check for new versions, and only the portable
downloads from GitHub (the Windows exe and the AppImage) have it. It runs when you click Check for
updates in Settings, or by itself if you turn that on there.
It asks GitHub (api.github.com) for the latest version number and sends nothing else,
and nothing downloads or installs itself. The Microsoft Store and Flatpak versions make no network
requests at all; the Store and Flatpak fetch their updates themselves.
Values stay hidden on screen
You see the keys. Each value stays hidden until you choose to show it.
You show values one by one, and each hides again after 30 seconds or when the window loses focus.
Every value is hidden, even ones that look harmless like PORT, because Envarsa
doesn’t guess which ones are secret. Copying a single value sends it to the clipboard without
showing it.
Copied values clear themselves
The clipboard is wiped 30 seconds after you copy a value.
On Windows, copies also skip clipboard history (Win+V) and the cloud clipboard. Linux has no equivalent, so a clipboard manager such as Klipper or CopyQ keeps its own copy; clear it after copying a secret.
Your library is one file you can read
Plain JSON on your disk, with an optional passphrase.
The portable downloads keep the file in an Envarsa Data folder beside the program, so
the library travels with it. The Microsoft Store version keeps it in
%APPDATA%\com.envarsa.app\, the Flatpak in
~/.var/app/io.github.terminalis.Envarsa/data/. Every save writes a temporary file and
swaps it in, keeping the previous version beside it as a .bak. If the file is ever
damaged, Envarsa offers to restore that previous version.
You can protect it with a passphrase in the standard
age format, which the age
command-line tool can also open. A lost passphrase can’t be recovered, which is why it’s
optional.
# faq
Questions
Does Envarsa change files in my projects?
Only when you ask it to write a .env.local, and only after showing you the file’s
path and a preview. It can merge values into an existing file or replace it. It never writes to
example files (.env.example, .sample, .template,
.dist) and never sets environment variables for running programs.
Can I use it without a .env file?
.env file?Yes. Create a project by hand and type keys, values and # comments into the editor.
Editing a project saves a new version and keeps the old one.
How do I move my library to another machine?
In Settings, export a copy, optionally protected with a passphrase, and import it on the other machine. Its projects are added to the library there; if a name already exists, you choose to replace, rename or skip it.
I installed the Flatpak bundle. How do I get updates?
The .flatpak file doesn’t update. Run
flatpak uninstall --user io.github.terminalis.Envarsa, then the Linux install command
under Download. Your library stays, and new versions then arrive through
flatpak update and your software center.
Is it free?
Yes. Envarsa is MIT-licensed and the source is on GitHub. It’s built with Rust and Tauri 2.
# download
Download Envarsa
Windows 10/11
The Microsoft Store version is signed and updates itself. The portable exe needs no installing and
keeps your library in an Envarsa Data folder beside it, so you can carry both on a USB
stick. It doesn’t update itself; turn on the update check in Settings to hear about new
versions, and save each new one into the same folder.
Linux
Install the Flatpak with this command, or open the Flatpak button’s file in your software center; it then updates with your other apps. Or take the portable AppImage, which keeps your library beside it.
flatpak install --user https://terminalis.github.io/packages/flatpak/envarsa.flatpakrefWarning: Always remember to export a copy of your library before uninstalling the program or deleting its folder.