Extensions
Extensions: what works, and what does not yet
Verso runs web extensions on WebKit, not on Chrome's engine, and installs them from the Chrome Web Store. Many run. Some do not start, and some start but show less than they should. This page says which, as far as we have checked.
01 Why some do not work
Extensions are written for Chrome, and Chrome's extension interface is larger than WebKit's. An extension that reaches for a part WebKit does not have can fail on its first line. Verso fills in the missing outline of that interface wherever that is safe, which brought several extensions back. It cannot add what WebKit really lacks, such as talking to a desktop app, running user scripts or recording the screen.
02 What we checked
On 5 November 2026 we loaded 52 popular extensions from the Chrome Web Store, 13 of them password managers, and looked at whether each starts and shows its first screen. We did not sign in, use a feature or visit the sites an extension is made for, so this is the best case and not a promise. The result:
- 25 started and showed their first screen with nothing in the way.
- 11 started, but something was broken or blank.
- 2 started but need a desktop app that Verso cannot reach.
- 14 did not start at all.
A prototype of the missing outline got 10 of those 14 to start, 7 of them with a working popup. Verso now has the real thing, and so far we have checked it again only on the password managers below.
03 What does not work yet
Whole kinds of extensions depend on something WebKit does not offer:
- Extensions that talk to a desktop app, such as the apps of some password managers.
- Managers for user scripts, which need an interface WebKit does not have.
- Extensions that record the screen or a tab, or that build on Chrome's side panel, tab groups or debugger.
- Notifications from extensions: Verso shows none, and extensions are told they are turned off.
- Extensions that need to stop requests themselves, as older ad blockers do. Verso has content blocking of its own.
04 Password managers
These matter most, so they have their own list. We loaded all 13 on 6 November 2026, signed out. Only a sign-in shows whether autofill works. We tried that by hand for 1Password, where it worked, and not for the others, so treat the rest as untested.
- Start and show their sign-in or welcome page: Bitwarden, LastPass, Zoho Vault, 1Password, Norton Password Manager.
- Start, but need their desktop app, which Verso cannot reach: Enpass and KeePassXC-Browser. The links of 1Password and Bitwarden to their apps, and Bitwarden's biometric unlock, do not work either.
- Start, but the popup stays blank, hangs or shows an error: Proton Pass, RoboForm, Dashlane, Keeper, NordPass.
- Do not start: iCloud Passwords, which needs Apple's own helper in any case.
Before you rely on one, sign in and fill a login you can easily recover.
05 What happens next
We run this check again after changes and update the page when the results change. Next we look at the hidden pages that extensions use for the clipboard and for reading data, which 22 of the 52 mention, and at the popups that stay blank. We give no dates.
06 If an extension does not work
Tell us which one and what you saw, in the issues of the releases repository. A broken extension does not affect the rest of Verso, and you can remove it in Settings → Extensions.