Skip to content

Backing up application data

About this page1 migration check
Original wiki wording
rev 4058 · 3 Aug 2025
1 migration check
Checked 8 Nov 2026
Automated source comparison, not reviewed by a maintainer
Show checks

Added during migration, not part of the original. Each check identifies a specific difference or review need; none is a review of the whole procedure.

Wallet seed and application data have different scopes Checked against pinned source

Bisq 1 v1.10.11 explicitly says the same seed serves BTC and BSQ, but seed words do not replace the database and keys needed to restore application state. The application backup warning also says the copy is not encrypted. Restoring wallet funds is not evidence that payment accounts, signing identity, messages or trade state have been recovered.

Checked 8 Nov 2026

Backing up your Bisq data is crucial to ensure you can retain control over trades, disputes, payment accounts, and funds in case of issues with your machine (e.g., drive failure) or Bisq itself (e.g., critical bugs).

All Bisq data is stored right on your computer—it's never stored (or even sent) to a central server, so backing it up is your job.

To see how to restore data to Bisq, see Restoring application data.

The safest, quickest, easiest, and most comprehensive thing you can do to safeguard your data is to back up the whole data directory at regular intervals. See the various elements of the data directory detailed here.

In addition, to make restoring payment accounts easier, you may want to back up an export of your payment accounts.

Go to Account > Backup and put in a location for your backup to be exported to (note that this section is titled "Backup wallet" in the software but it actually exports the entire data directory).

Data directory backup screen.
Data directory backup screen.
Historical full-size recovered source. Provenance catalogue.

When Bisq is closed, you can simply copy the entire data directory and paste it somewhere safe. Find the location of your data directory by clicking on the Open Directory button (see screenshot above) or see data directory locations here.

Backup files are not encrypted. If you’ve set a wallet password, your wallet files will be encrypted, but all your other data will not be encrypted.

We recommend encrypting the whole backup folder with something like gpg, 7-Zip, Cryptomator, etc.

If you just want to back up your payment accounts, export them from Account > National Currency Accounts.

Be advised: exporting your accounts this way only exports metadata. Aging and signing status are not included. To include account aging and signing status, you also need to save the btc_mainnet/keys/sig.key file from your data directory.

Because of the way restoring payment accounts works, it's best for most users to back up the whole data directory and back up a payment account export.

Export fiat payment accounts here. You can export altcoin accounts from the Altcoin Accounts tab.
Export fiat payment accounts here. You can export altcoin accounts from the Altcoin Accounts tab.
Historical full-size recovered source. Provenance catalogue.

Please be sure to properly back up your wallet seed.

If you want to carry over a particular onion address (and keep your local reputation), you can replace the btc_mainnet/tor/hiddenservice folder in your data directory with the one from your backup.

In Portfolio > History you'll find an Export to CSV button to export your trade history.

There's no way to import this data back into Bisq, but it can be useful to have a copy of this data for yourself for record-keeping, analysis, etc.

In Funds > Transactions you'll find an Export to CSV button to export your trade history.

There's no way to import this data back into Bisq, but it can be useful to have a copy of this data for yourself for record-keeping, analysis, etc.

Automatic backup with cyclic redundancy

Section titled “Automatic backup with cyclic redundancy”

Bisq doesn't directly implement a scheduled backup feature, but you can set up an automatic backup routine to store a versioned history of your data directory in a compact way.

Source and history

This article keeps its recovered wording, headings, step order and available images. Formatting and links are adapted for this site. The snapshot does not guarantee that every instruction is current.

Original page
Backing up application data
Revision
4058 · 3 Aug 2025
Last recorded editor
SuddenWhipVapor (not a complete author list)
Snapshot
18 October 2026
Source files
Original wikitext · Revision metadata
Image references
2 recovered, 0 missing · Media catalogue
Recovery gaps
0 restored historical template occurrences · 0 unresolved templates · 0 unresolved article links · 0 unresolved sections

Recovery scope and remaining source gaps