Why convert BCUP to JSON?
A .bcup vault is Buttercup's encrypted database, and developers export to .JSON when they want to inspect, back up, or programmatically process their credentials outside the app. Buttercup's own facades are literally built to convert vaults to and from plain JSON objects.
How to convert BCUP to JSON
buttercup-core (Node.js) OPEN-SOURCE
In an ESM Node project, load the .bcup with a TextDatasource/Credentials, then call createVaultFacade(vault) and write JSON.stringify(facade) to a .json file.
buttercup-exporter (Node.js) OPEN-SOURCE
The official buttercup-exporter CLI unlocks a vault and emits its contents; capture the object output and save it as .json.
About these formats
A .bcup file is an encrypted password vault created by Buttercup, a free open-source password manager. It holds logins, notes, and other secrets protected by AES-256 encryption and a master…
Open .BCUP details →A JSON file is a plain-text data file in JavaScript Object Notation format, used by web APIs, app configurations, and data exports. Any text editor opens it - Notepad on Windows, TextEdit…
Open .JSON details →Quality & what to watch
- The facade JSON is unencrypted - it exposes every password in clear text, so store and delete it carefully.
- buttercup-core is ESM-only and needs Node 14+, so you must run it in a matching project or bundler rather than a plain
requirescript. - The JSON follows Buttercup's internal facade shape (groups, entries, fields), not a generic password-manager schema, so other apps won't import it directly.
Frequently asked questions
Does Buttercup have a JSON export button?
buttercup-core and its createVaultFacade serialisation helper.Is the JSON structure documented?
Can I edit the JSON and load it back?
Why can't I just require() it?
import in an ESM project or a bundler like Webpack, not CommonJS require.