> For the complete documentation index, see [llms.txt](https://faq.blink.sv/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.blink.sv/custody-and-security/can-i-move-my-blink-funds-to-my-own-custody.md).

# Can I move my Blink funds to my own custody?

If you're already using Non-Custodial Mode, you hold your own keys — your funds are already in your own custody within Blink. The information below applies to Custodial Mode users who want to move funds to an external wallet or switch to Non-Custodial Mode.

## Moving funds from Custodial Mode

Yes, you can move your funds from Custodial Mode at any time. You have two options:

1. **Switch to Non-Custodial Mode** — Move your funds to Non-Custodial Mode within Blink, where you hold your own keys via the Spark protocol. A guided migration is available in the app.
2. **Withdraw to an external wallet** — Send your funds to any Bitcoin wallet you control, via Lightning or on-chain.

It is important to note that once you move your funds to your own custody — whether in Non-Custodial Mode or an external wallet — you will be solely responsible for their security and any potential loss. Make sure you have a good understanding of how to securely store your Bitcoin and take all necessary precautions to protect your private keys.

Explore different types of bitcoin wallets and learn how to withdraw from Blink on the Blink Blog: [blink.sv/blog/choosing-the-right-bitcoin-wallet](https://www.blink.sv/blog/choosing-the-right-bitcoin-wallet)


---

# 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://faq.blink.sv/custody-and-security/can-i-move-my-blink-funds-to-my-own-custody.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.