> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/get-started/setup.md).

# Setup

First-time Cake Wallet setup: set a 4- or 6-digit PIN, then create a new wallet or restore one from a recovery phrase, keys, backup file, or hardware wallet.

The first time you open Cake Wallet, it walks you through two quick steps: setting a PIN, and creating (or restoring) your first wallet. The whole thing takes about two minutes.

{% stepper %}
{% step %}

### Welcome

Open Cake Wallet and tap `Set a PIN`. By continuing, you agree to the Terms of Service linked on this screen.

![Cake Wallet welcome screen with Set a PIN button highlighted](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/getstarted_create-new-wallet_01_welcome_hl.png)
{% endstep %}

{% step %}

### Set your PIN

Enter a PIN, then enter it again to confirm. Cake Wallet uses a 4-digit PIN by default — tap `Switch to 6-digit PIN` if you'd like a longer one.

{% hint style="info" %}
Your PIN protects access to the app on this device. It is not a backup — only your recovery phrase can recover your wallet on another device.
{% endhint %}

![Setup PIN screen](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/getstarted_create-new-wallet_02_set-pin_hl.png)
{% endstep %}

{% step %}

### Create or restore

After your PIN is set, choose how to get your first wallet:

* **Create New Wallet** — start fresh. Continue with the [Create new wallet](https://docs.cakewallet.com/get-started/setup/create-new-wallet) guide.
* **Restore Wallet** — bring an existing wallet into Cake using its [recovery phrase or keys](https://docs.cakewallet.com/get-started/setup/restore-existing-wallet/recovery-phrase-or-keys), a [backup file](https://docs.cakewallet.com/get-started/setup/restore-existing-wallet/backup-file), a [hardware wallet](https://docs.cakewallet.com/get-started/setup/restore-existing-wallet/hardware-wallet), or the [Cupcake app](https://docs.cakewallet.com/cupcake/getting-started).

![Create or restore wallet choice](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/getstarted_create-new-wallet_05_create-or-restore.png)
{% endstep %}
{% endstepper %}

If you run into any trouble, contact us using the in-app chat under `Support`, by email at <support@cakewallet.com>, or on [Telegram](https://t.me/cakewallet_bot).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cakewallet.com/get-started/setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
