1Password v8 migration preparation

Hi wagnerone.

We don't have a specific support page for comparing the "1Password in the browser" and the "classic plug-in". I'm sorry about the inconvenience. I will list the major differences between them here:

1. Desktop app dependency:
2. The "classic plug-in" requires the desktop app to be functional.

3. "1Password in the browser" can work independently. When its integration feature is turned on and working with the desktop app, it can share the same locked state as the desktop app and use the desktop app shortcuts, for example, the "cmd + \".

4. Product development:

5. The "classic plug-in" didn't receive any updates since 2019.

6. "1Password in the browser" will receive continuous development and improve its functionality.

7. Vault access:

8. The "classic plug-in" can access local/standalone vaults, and its primary purpose is for our license users to achieve that.

9. "1Password in the browser" cannot access local/standalone vaults, and it is designed for our membership users. Plus, 1Password 8 will not access local/standalone vaults.

10. Functionalities in the browser:

11. The "classic plug-in" will prompt you to save the login (autosave) after submission.

12. "1Password in the browser" currently doesn't support autosave. But we have an existing feature request, and our development team is dedicated to providing the solution. Meanwhile, it introduced the inline menu suggestion and more features compared to the classic version.

In addition, we can find more support articles for the 1Password classic extension: 1Password classic extension support

Here is a helpful guide, and it includes all the functions and features for 1Password in the browser:
- Get started with 1Password in your browser

I hope the above explanations find you well.