Bitwarden Desktop App Extremely Slow on MacBook Air M1 (macOS 26.0.1)

Hi everyone,
I’m experiencing major performance issues with the Bitwarden desktop app on my MacBook Air M1 running the latest macOS 26.0.1. The app takes around 5 minutes to load both before and after signing in. Scrolling through items is painfully slow—almost unusable due to constant loading delays.

I’ve already tried uninstalling and reinstalling the app (downloaded from the Mac App Store) a few times, but the issue persists.

Has anyone else run into this? Any suggestions on how to fix or troubleshoot it?

Thanks in advance!

Not a mac user, so guessing a bit here….

Have you changed your encryption settings to values greater than Bitwarden’s default? If so, that will impact how long the decryption takes, which is one of the primary activities that happens during load time.

Did you make sure that the local data of the app was deleted between deinstalling and reinstalling it?

1 Like

A helpful tip to clear the cache improved things significantly! thanks to @Nail1684!

However, the app is still quite slow after biometric login, taking around 45 seconds to unlock. My current KDF settings are:

  • KDF algorithm: Argon2id

  • Iterations: 4

  • Memory: 64 MB

  • Parallelism: 5

These settings work flawlessly and quickly on my mobile devices (iOS 26) and browser extensions on chrome, but the desktop app remains noticeably slower.

Has anyone else experienced this? Any tips for improving the speed on the desktop app?

Thanks in advance!

1 Like

Could your problem related to MacOS 26 and electron libraries? Shamelectron - Electron Apps macOS Tahoe GPU Performance Tracker

@Keanen If I see it correctly, this PR would solve that (–> upgrades to electron version 36.9.3) and this one also (–> upgrades electron to version 37.7.0, as currently declared – BTW a bit hidden in “files changed” you can see that version), as those versions seem to be fine according to that site you linked:

Yeah, I saw those go through but I don’t know which release they are tied to!?

Well, the PR from my second link is not even merged – the first one was merged two weeks ago, so that could be included in the 2025.10.x releases.

Yeah, makes sense. Nice, I see the App Store has 2025.10.0. :crossed_fingers:

@Keanen As I wrote before, it could be implemented… could also be the case, that that pull request was merged, but it will only be “activated” in one of the next releases.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.