<p>Update 2024 (10 years later):</p>
<p>bitaddress.org has not changed in 8 years and may contain bugs &amp; outdated tech such as BIP38 encryption.</p>
<p>Instead, I recommend to use a modern BIP39 tool with a very good track record such as this:
<a href="https://github.com/iancoleman/bip39" rel="nofollow noreferrer">https://github.com/iancoleman/bip39</a></p>
<p>You should do your research and ensure that you create the wallet on an offline system which is also (ideally) stateless like <a href="https://tails.net/" rel="nofollow noreferrer">TailsOS</a>.  This will minimize (but not eliminate) the chances of malware being able to affect your wallets.</p>
<p>Once you have the downloaded files in a secure environment, ensure you properly check the gpg signature before loading the html file into a browser and using it to generate a paper wallet.</p>
<p><strong>Warning:</strong></p>
<p>Paper wallets generated in a browser may be fun and free, but they present many security risks, not least from the computer you are using.  Instead: consider using an Open Source mobile app or, if securing larger amounts, get a hardware wallet.</p>

CC BY-SA 3.0
2014-03-29T18:28:11.627Z
>      I do not know how crackable BIP38 is...  


I checked up on this, it is very safe, there is no concerns with the encryption itself.
Jonathan Cross
CC BY-SA 3.0
2014-02-13T15:42:10.607Z
"Make your paper wallet and several prints (do not save a copy anywhere on the computer)." Can you save on a pendrive while not connected to internet - and never have that pendrive inserted when the computer is internet enabled?
Peter
CC BY-SA 3.0
2014-02-13T16:10:45.527Z
You can do whatever you like, but if you are going to put it on a pendrive / usb stick, I'd suggest putting it inside a TrueCrypt encrypted file container.  One of the best parts of a paper wallet is that you can rest assured that the private keys are *nowhere at all* except on that piece of paper (and even then they are encrypted).  This means that an attacker *must* have physical access to that piece of paper to even begin an attack.  I do not know how crackable BIP38 is, but a lot of it will depend on the length of your password.
Jonathan Cross
CC BY-SA 3.0
2017-05-28T12:00:37.233Z
_**Drag** the bitaddress.org.html file into your browser._ seriously? why not just double-click it?
ericn
CC BY-SA 4.0
2019-04-01T00:47:54.230Z
**[PSA: For users of http://bitcoinpaperwallet.com](https://twitter.com/jonf3n/status/1062380032889368576)** Note, the website and all related business was sold to an unknown individual and is no longer being maintained at https://github.com/cantonbecker/bitcoinpaperwallet

Info on the website does not match the signed info on GitHub and provides no link to a new repo.
Jonathan Cross
CC BY-SA 4.0
2024-02-15T20:26:08.337Z
@JonathanCross: Is there a reason why you don't use PGP verification of the HTML file? Isn't this step necessary?
Ohumeronen
CC BY-SA 4.0
2014-02-13T14:16:46.457Z
2024-02-18T02:13:32.287Z
2024-02-18T02:13:32.287Z
Jonathan Cross
<p>The site does not have a download option.</p>

<p>I can save the page using Google Crome by CTR-S, but the version I have saved in this way does not work.</p>

<security><offline><bitaddress.org><bip38>
How to download bitaddress.org to use offline?
Peter
# How to download bitaddress.org to use offline?

(Asked by: username_0 on 2014-02-13)

The site does not have a download option.

I can save the page using Google Crome by CTR-S, but the version I have saved in this way does not work.

**Tags:** security, offline, bitaddress.org, bip38


---

## 1 answers

### Answer by username_1 on 2014-02-13. Score: 9 | Accepted answer

Update 2024 (10 years later):

bitaddress.org has not changed in 8 years and may contain bugs & outdated tech such as BIP38 encryption.

Instead, I recommend to use a modern BIP39 tool with a very good track record such as this:
<https://github.com/iancoleman/bip39>

You should do your research and ensure that you create the wallet on an offline system which is also (ideally) stateless like [TailsOS](https://tails.net/). This will minimize (but not eliminate) the chances of malware being able to affect your wallets.

Once you have the downloaded files in a secure environment, ensure you properly check the gpg signature before loading the html file into a browser and using it to generate a paper wallet.

**Warning:**

Paper wallets generated in a browser may be fun and free, but they present many security risks, not least from the computer you are using. Instead: consider using an Open Source mobile app or, if securing larger amounts, get a hardware wallet.

> **Comments:**
> **username_0**: "Make your paper wallet and several prints (do not save a copy anywhere on the computer)." Can you save on a pendrive while not connected to internet - and never have that pendrive inserted when the computer is internet enabled?  
> **username_1**: You can do whatever you like, but if you are going to put it on a pendrive / usb stick, I'd suggest putting it inside a TrueCrypt encrypted file container.  One of the best parts of a paper wallet is that you can rest assured that the private keys are *nowhere at all* except on that piece of paper (and even then they are encrypted).  This means that an attacker *must* have physical access to that piece of paper to even begin an attack.  I do not know how crackable BIP38 is, but a lot of it will depend on the length of your password.  
> **username_1**: >      I do not know how crackable BIP38 is...     I checked up on this, it is very safe, there is no concerns with the encryption itself.  
> **username_2**: _**Drag** the bitaddress.org.html file into your browser._ seriously? why not just double-click it?  
> **username_1**: **[PSA: For users of http://bitcoinpaperwallet.com](https://twitter.com/jonf3n/status/1062380032889368576)** Note, the website and all related business was sold to an unknown individual and is no longer being maintained at https://github.com/cantonbecker/bitcoinpaperwallet  Info on the website does not match the signed info on GitHub and provides no link to a new repo.  
> **username_3**: @username_1: Is there a reason why you don't use PGP verification of the HTML file? Isn't this step necessary?  

---

