> For the complete documentation index, see [llms.txt](https://nixwiki.gitbook.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nixwiki.gitbook.io/home/wallet-functionality/gui/backup-and-security/wallet-backup.md).

# Wallet Backup

## Backup Frequency

Because the NIX GUI wallet utilizes HD key generation, you do not need to backup your wallet after generating 100 or 1000 receive addresses. All receive addresses you generate are based off of a single master private key which will grant you access to all future generated addresses.

{% hint style="warning" %}
**NOTICE:** Changing your password will not require a new backup, but any old backups will still use their respective password. Therefore, it is strongly recommended that you replace any previous wallet.dat backups.
{% endhint %}

{% hint style="danger" %}
**WARNING:** Ghost Vault funds are handled differently than public coins and require backups after any use of a ghost vault key (which includes sending to your own vault). The wallet automatically creates an updated backup file in the ghostbackups directory any time your ghost vault is used. This backup file is not in addition to your normal wallet.dat file, it is simply a recent backup of it.
{% endhint %}

## Backing up your wallet

You can manually copy your wallet.dat file to a new location by navigating to the NIX data directory and making a copy of the wallet.dat. The default location for this file is inside the wallets directory if it exists, otherwise, the root data directory (nix).

### Windows

{% hint style="success" %}
**TIP:** Windows hides the AppData folder by default when using the graphical file explorer. In order to get inside the AppData folder, you can either type "%AppData%" into the search bar or check the box for "Hidden items" under the View menu to show hidden files in the file explorer window and navigate your way there.
{% endhint %}

C:\Users\\(your username)\AppData\roaming\nix\wallets\wallet.dat

or

C:\Users\\(your username)\AppData\roaming\nix\wallet.dat

{% hint style="info" %}
**NOTE:** If a "wallets" directory exists, the software will use it as the default wallet directory. If it does not exist, then the root directory will be used.
{% endhint %}

### MacOS

{% hint style="success" %}
**TIP:** MacOS hides the Application Support folder by default.\
1\. On the top bar, left side of your screen click on "Go", then click on "Go to Folder".\
2\. Type or copy-paste: \~/Library/Application Support/nix/
{% endhint %}

\~/Library/Application Support/nix/wallets/wallet.dat

or

\~/Library/Application Support/nix/wallet.dat

{% hint style="info" %}
**NOTE:** If a "wallets" directory exists, the software will use it as the default wallet directory. If it does not exist, then the root directory will be used.
{% endhint %}

### Linux

\~/.nix/wallets/wallet.dat

or

\~/.nix/wallet.dat

{% hint style="info" %}
**NOTE:** If a "wallets" directory exists, the software will use it as the default wallet directory. If it does not exist, then the root directory will be used.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nixwiki.gitbook.io/home/wallet-functionality/gui/backup-and-security/wallet-backup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.