Your data file
Big Picture Money keeps your personal financial data in a local database encrypted with SQLCipher (an encrypted form of SQLite). The app reads and writes this file. The file is yours — you can back it up, move it to another computer, or inspect a copy with SQLCipher-compatible tools and your passphrase. You are not locked into Big Picture Money to read your own data.
Database file
| Item | Detail |
|---|---|
| Default file name | bigpicture.db |
| Format | SQLCipher-encrypted SQLite |
| Contents | Accounts, transactions, categories, budgets, reports, AI chat history, search index, and app settings — everything tied to your ledger |
The default name is bigpicture.db. You may use a different file name or location when you create or switch databases in Settings → General → Data file, or via Open existing… on the Unlock screen. Each file is an independent encrypted database with its own passphrase.
The file is not human-readable in a text editor. Without your passphrase, the bytes on disk do not reveal account names, amounts, or other financial details.
Data folder layout
Your data folder is where the active database file lives. It may match the default app location, or a folder you picked on the Welcome screen. The default database file name in that folder is bigpicture.db.
| File | Purpose |
|---|---|
bigpicture.db (default name) | Encrypted database for this data folder |
You may keep more than one database in the same folder. Each .db file is an independent ledger with its own passphrase.
Copy your .db file(s) when you back up. See Back up your data file.
Default locations
| Operating system | Default data folder |
|---|---|
| Windows | %LOCALAPPDATA%\BigPictureMoney |
| macOS | ~/Library/Application Support/BigPictureMoney |
| Linux | ~/.local/share/BigPictureMoney (or $XDG_DATA_HOME/BigPictureMoney if set) |
Custom location
If you chose a folder during setup, that path is your data folder. Big Picture Money also stores a small pointer file in the default app folder so it can find your data on the next launch.
What is not in your data folder
Some data ships with the application and is not part of your personal backup:
- Merchant recognition database — read-only reference data bundled with the app install (common merchant names and categorization hints). It is reinstalled with app updates; you do not need to back it up with your ledger.
- Bank sync tokens — stored in your operating system keychain, not inside
bigpicture.db. Reconnecting a bank after a restore may require signing in again.
Opening the database outside Big Picture Money
You own the file. You may inspect it with a SQL client, run ad hoc queries, or verify that it is encrypted. Use tools that support SQLCipher, not plain SQLite.
Before you open the file
- Quit or lock Big Picture Money — opening the same file while the app is writing can corrupt it.
- Work on a copy — duplicate the
.dbfile before experimenting. - Have your passphrase ready — external tools need the same passphrase you use to unlock the app.
Plain SQLite tools will not work
A standard sqlite3 install or DB Browser build without SQLCipher shows garbage or errors on an encrypted file. The file header is not the usual SQLite format 3 text. That is expected for SQLCipher — it does not mean your data is lost.
Compatible tools
These approaches support SQLCipher-encrypted databases when configured correctly:
| Tool | Notes |
|---|---|
| SQLCipher | Official project; includes a command-line shell |
| DB Browser for SQLite (SQLCipher build) | GUI for browsing tables and running queries — use a distribution that lists SQLCipher support |
| Other SQLCipher-aware clients | Any client that can set the encryption key before access |
Exact menus and commands depend on the tool version. Consult that tool's documentation for "SQLCipher" or "encryption key" setup.
Example: sqlcipher command line
sqlcipher /path/to/copy-of-bigpicture.db
PRAGMA key = 'your passphrase here';
.tables
If the passphrase is wrong, table listings and queries fail — the file is not damaged, but the key does not match.
Expected result: With the correct passphrase, you see your table list (or can run read-only queries) in the SQLCipher tool. With the wrong passphrase, the tool reports an error and leaves the file unchanged.
Risks of editing outside the app
Big Picture Money expects exclusive control of bigpicture.db while it is running. Manual edits can:
- Break referential integrity between accounts, transactions, and categories
- Leave the search index out of sync with table data
- Cause the app to refuse to open the file after a failed migration
Use external access for read-only inspection unless you fully understand SQL and accept the risk. Prefer changing data through the app UI.
Moving your data to another computer
- Back up your data file on the source machine.
- Install Big Picture Money on the new computer.
- Copy your backed-up data folder to the new machine (default path or a folder you will select).
- Launch the app and unlock with your existing passphrase.
The same encrypted file works across Windows, macOS, and Linux when you use the same passphrase and a current Big Picture Money install. Your data is not tied to a cloud account; the database file is your data.