<p>Encrypted; to more than one place convenient to you: hard drive, pendrive, cloud. Some store it on paper but that's another school.</p>

CC BY-SA 3.0
2013-01-12T08:22:19.353Z
2013-01-12T08:51:48.313Z
2013-01-12T08:51:48.313Z
superuser
<p>The file you'll need to back up is <code>wallet.dat</code> which can be found in <code>%appdata%\roaming\bitcoin</code> on Windows or <code>~/.bitcoin</code> on Linux/MacOSX.</p>

<p>By default a pool of 100 pre-generated, unused addresses is maintained in your wallet, and so it is safe to use 100 new addresses without backing up your wallet.  New addresses are used most times you send bitcoins and used as a "<a href="https://bitcoin.stackexchange.com/questions/736/how-does-change-work-in-a-bitcoin-transaction">change</a>" address, and also when you request a new receiving address. As you use new addresses, more are generated and added to the end of the pool.  Once you've used 100 since backing up, you'll start using addresses which aren't in the backup. To this end, the frequency of your backups is largely determined by the frequency of your transactions and this is largely a personal decision. If you absolutely cannot manage a backup every 100 transactions (why?) or are comfortable with a more aggressive schedule (and smaller wallet) there is a <code>-keypool</code> option to change the number of addresses pre-generated.</p>

<p>Best practices for storing wallet backups almost always include encryption. Most folks in the community swear by tools like <a href="http://www.truecrypt.org/" rel="nofollow noreferrer">TrueCrypt</a> for such purposes, though there are countless alternatives. Storage of the backup depends largely on how long-term the storage is intended to be and the security levels necessary. For small amounts of coin and short-term backups, online services like DropBox or Mozy might be adequate, assuming the wallet is encrypted before uploading. For longer-term or higher security backup, coins might be sent to an offline wallet stored in paper form at a physically secured location or any variation between.</p>

<p>Regardless of your wallet backup methodology and schedule, it is ALWAYS a good idea to take some basic measures to <a href="https://en.bitcoin.it/wiki/Securing_your_wallet" rel="nofollow noreferrer">secure your wallet</a>.</p>

CC BY-SA 3.0
2013-12-09T19:02:36.540Z
I just read this answer and it was like I was reading some alien language... Can someone please explain this for the non technical person?  i.e. if I backup my .dat file and only receive bitcoins with it and never send, will that single backup last forever?
oshirowanen
CC BY-SA 3.0
2011-09-08T06:14:13.403Z
Aren't addresses generated in chunks of about a 100 and cached? So, you should only backup every ~50 transactions.
ripper234
CC BY-SA 3.0
2011-09-08T06:16:32.010Z
You're correct, amending my answer.
David Perry
CC BY-SA 3.0
2011-09-08T06:18:12.727Z
Until we get [deterministic wallets](http://bitcoin.stackexchange.com/questions/718/what-is-a-deterministic-wallet), then backing up once is enough.
David Schwartz
CC BY-SA 3.0
2011-09-08T06:23:16.403Z
Even with the deterministic wallets we [sort of already have](https://github.com/casascius/Bitcoin-Address-Utility) backing up once is enough so long as you never perform any sends. Basically the tech we have in that arena is adequate for "savings" type accounts, but we're not there yet for "checking" type accounts.
David Perry
CC BY-SA 3.0
2012-02-05T18:35:11.833Z
The keypool isn't generated "in blocks of 100 addresses", it's maintained at 100 addresses.  Every time you use one of the 100, another is generated to replace it.
Chris Moore
CC BY-SA 3.0
2012-10-02T04:50:58.793Z
This answer could do with updating to mention that the standard client can now encrypt the wallet.
Highly Irregular
CC BY-SA 3.0
2011-09-08T06:09:13.823Z
2012-02-07T00:41:20.827Z
2017-04-13T12:47:36.707Z
David Perry
<ul>
<li>How often? Is backing it up once enough?</li>
<li>Any best practices to storing the backup?</li>
</ul>

CC BY-SA 3.0
2011-09-08T05:57:53.507Z
See related but not identical: http://bitcoin.stackexchange.com/questions/28/how-can-i-keep-my-wallet-secure
ripper234
<wallet><backup>
How should you backup your wallet?
ripper234
# How should you backup your wallet?

(Asked by: username_0 on 2011-09-08)

* How often? Is backing it up once enough?
* Any best practices to storing the backup?

**Tags:** wallet, backup

> **Comments:**
> **username_0**: See related but not identical: http://bitcoin.stackexchange.com/questions/28/how-can-i-keep-my-wallet-secure  

---

## 2 answers

### Answer by username_2 on 2011-09-08. Score: 16 | Accepted answer

The file you'll need to back up is `wallet.dat` which can be found in `%appdata%\roaming\bitcoin` on Windows or `~/.bitcoin` on Linux/MacOSX.

By default a pool of 100 pre-generated, unused addresses is maintained in your wallet, and so it is safe to use 100 new addresses without backing up your wallet. New addresses are used most times you send bitcoins and used as a "[change](https://bitcoin.stackexchange.com/questions/736/how-does-change-work-in-a-bitcoin-transaction)" address, and also when you request a new receiving address. As you use new addresses, more are generated and added to the end of the pool. Once you've used 100 since backing up, you'll start using addresses which aren't in the backup. To this end, the frequency of your backups is largely determined by the frequency of your transactions and this is largely a personal decision. If you absolutely cannot manage a backup every 100 transactions (why?) or are comfortable with a more aggressive schedule (and smaller wallet) there is a `-keypool` option to change the number of addresses pre-generated.

Best practices for storing wallet backups almost always include encryption. Most folks in the community swear by tools like [TrueCrypt](http://www.truecrypt.org/) for such purposes, though there are countless alternatives. Storage of the backup depends largely on how long-term the storage is intended to be and the security levels necessary. For small amounts of coin and short-term backups, online services like DropBox or Mozy might be adequate, assuming the wallet is encrypted before uploading. For longer-term or higher security backup, coins might be sent to an offline wallet stored in paper form at a physically secured location or any variation between.

Regardless of your wallet backup methodology and schedule, it is ALWAYS a good idea to take some basic measures to [secure your wallet](https://en.bitcoin.it/wiki/Securing_your_wallet).

> **Comments:**
> **username_0**: Aren't addresses generated in chunks of about a 100 and cached? So, you should only backup every ~50 transactions.  
> **username_2**: You're correct, amending my answer.  
> **username_4**: Until we get [deterministic wallets](http://bitcoin.stackexchange.com/questions/718/what-is-a-deterministic-wallet), then backing up once is enough.  
> **username_2**: Even with the deterministic wallets we [sort of already have](https://github.com/casascius/Bitcoin-Address-Utility) backing up once is enough so long as you never perform any sends. Basically the tech we have in that arena is adequate for "savings" type accounts, but we're not there yet for "checking" type accounts.  
> **username_5**: The keypool isn't generated "in blocks of 100 addresses", it's maintained at 100 addresses.  Every time you use one of the 100, another is generated to replace it.  
> **username_6**: This answer could do with updating to mention that the standard client can now encrypt the wallet.  
> **username_3**: I just read this answer and it was like I was reading some alien language... Can someone please explain this for the non technical person?  i.e. if I backup my .dat file and only receive bitcoins with it and never send, will that single backup last forever?  

---

### Answer by username_1 on 2013-01-12. Score: -1

Encrypted; to more than one place convenient to you: hard drive, pendrive, cloud. Some store it on paper but that's another school.


---

