{"id":1410,"date":"2026-06-20T20:52:56","date_gmt":"2026-06-20T19:52:56","guid":{"rendered":"https:\/\/entertainmentnews.site\/index.php\/2026\/06\/20\/i-moved-my-passwords-2fa-and-passkeys-to-vaultwarden-and-it-became-more-useful\/"},"modified":"2026-06-20T20:53:02","modified_gmt":"2026-06-20T19:53:02","slug":"i-moved-my-passwords-2fa-and-passkeys-to-vaultwarden-and-it-became-more-useful","status":"publish","type":"post","link":"https:\/\/entertainmentnews.site\/index.php\/2026\/06\/20\/i-moved-my-passwords-2fa-and-passkeys-to-vaultwarden-and-it-became-more-useful\/","title":{"rendered":"I moved my passwords, 2FA, and passkeys to Vaultwarden, and it became more useful\u2026"},"content":{"rendered":"
\n

The topic I moved my passwords, 2FA, and passkeys to Vaultwarden, and it became more useful\u2026<\/strong> is currently the subject of lively discussion \u2014 readers and analysts are keeping a close eye on developments.<\/p>\n

This is taking place in a dynamic environment: companies\u2019 decisions and competitors\u2019 reactions can quickly change the picture.<\/p>\n

I used to store and manage my passwords the way most people do: simply relying on my browser. And that worked fine, honestly, Vivaldi is pretty solid and syncs my information across devices relatively easily. But when I got into self-hosting, the idea of storing my passwords on my own server seemed very tempting, so I decided to make the move to Vaultwarden.<\/p>\n

The transition was both easier and more useful than I was expecting, to the point where I don’t really want to live without Vaultwarden anymore. It even makes passkeys useful, which is more than I ever expected.<\/p>\n

\"\"<\/figure>\n

Like I said, I didn’t really have any problems with storing my passwords in the cloud. After all, these solutions are built with security in mind, so the chances that anyone would get access to my login details through the sync services are very low. But nothing feels quite as secure as having things in your home, so the idea of Vaultwarden paired with Bitwarden is very tempting.<\/p>\n

With this solution, all of my passwords and login details are stored on my own little server, an improvised NAS fashioned out of a mini PC. It never needs to leave my network, but if I do need to access it remotely, I can do it through Tailscale, which enables remote access without fully exposing my services to the internet. I’m always in control of where the data is stored, and always on control of who can access it. It’s nice to not be at the whim of a third party, even if they’re generally reliable. A solution like Tailscale and a reverse proxy is kind of required so you can enforce securo connections to the server, so remote access is just a bonus ou get from using it.<\/p>\n

Moving passwords from one service to another is not particularly hard. You can usually export your passwords as a CSV file and then import it into whatever service you’re going to use next, and Vaultwarden supports exactly that. Just keep in mind CSV files are completely plain text, so you want to delete them once you’re done.<\/p>\n

With Vaultwarden storing my passwords and the Bitwarden app connected to my self-hosted server, it was easy to start using the saved passwords from the internet. using Bitwarden comes with an additional benefit in that passwords are also saved for my phone apps. Typically, I couldn’t access passwords for a service if I used it on the web on my desktop but used an app on my phone. Since Bitwarden can store passwords from both sources, it made it easier to access these passwords across devices.<\/p>\n

\"\"<\/figure>\n

Two-factor authentication is a different beast, I can’t just export it from one service and import it into another, but it’s fairly easy to register a new 2FA app for a given service, and to be fair, I didn’t have that many services with app-based 2FA in the first place. I often used my email instead. As such, it was pretty easy to make the transition, and again, Bitwarden makes things extra easy because it can pull both the username and password for a given service, but once you’ve added a 2FA login to that same account, it also fills it in automatically when prompted. It makes the process of logging in this way so much easier.<\/p>\n

A popular trend in online security lately are passkeys, a kind of web authentication protocol that’s stored on your device and allows you to sign into websites using things like your fingerprint, facial recognition, or a security key, so you don’t have to expose your password. In concept, passkeys are great, but because they’re often tied to physical devices, which means if you use multiple devices, or reset your PC or phone, logging in can actually become more of a pain. I always avoided them, perhaps irrationally, because I worried that they would supersede passwords and make my accounts unusable.<\/p>\n

However, Vaultwarden also offers the ability to store passkeys on your server and access them with Bitwarden. This makes it so you can login on multiple devices using the same passkey, because you can always pull it remotely from the Vaultwarden server. You don’t need to create a passkey for each device you use, and it doesn’t become useless if you reset that device. It’s always the same one.<\/p>\n

Not every place may support a Bitwarden passkey, admittedly. I first tested this with Best Buy’s website and it didn’t work, but then I tried an online forum I’m a member of, and that worked without a hitch. Depending on what websites you use, your success rate may vary, but still, this makes passkeys far more appealing than they’ve ever been to me.<\/p>\n

Initially, I thought Vaultwarden would just be an alternative way to store my passwords, but the way it makes it easier to use two-factor authentication and passkeys on all my devices makes it clear that self-hosting is the way to go for managing all my login details. The transition was easy, but learning how capable it really is changed how I think about using it, and I highly recommend it to anyone who’s able to self-host services.<\/p>\n