bitwarden-attachment-exporter VS BitwardenDecrypt

B) Bitwarden Attachment Exporter, which is a program that backups up your attachments alongside your data.json vault file.

There are third-party export tools to get your attachments out but I haven’t used them myself yet since I am not using attachments. One such option: https://github.com/ckabalan/bitwarden-attachment-exporter

GitHub - GurpreetKang/BitwardenDecrypt: Decrypts an encrypted Bitwarden data.json file.

That said, you can decrypt a bitwarden password encrypted backup without bitwarden. Aside from being able to run something like Vaultwarden locally, there are programs that can do that. Or you can use the local data.json file with https://github.com/GurpreetKang/BitwardenDecrypt

If you've exported as a password protected json, you can try to import it into a new account. Or you can use a third party tool such as https://github.com/GurpreetKang/BitwardenDecrypt

These files can be decrypted using the BitwardenDecrypt utility. In addition, the data.json file can be opened using a copy of the .exe for Bitwarden portable.

Use a third-party tool like BitwardenDecrypt to decrypt the JSON off-line, then condition the data to be compatible with KeePass.

Download and archive a copy of the third-party utility BitwardenDecrypt, version 1.6 or higher. This tool can decrypt password-protected JSON exports. The source code is a 5-KB Python file, which you can store on your backup media.

This depends crucially on what method you used to produce the encrypted JSON export. If you used the Web Vault or CLI to export a password-protected JSON, then you can either maintain an archive copy of the Portable Desktop App .exe file to use for opening the JSON, or you can use a third-party utility like BitwardenDecrypt.

The last sentence in the above quote is not accurate as it pertains to the password-protected JSON exports. These can not only be imported into a new Bitwarden account, but they can also be decrypted by third-party tools (such as BitwardenDecrypt).