> 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/transaction-fees/what-are-the-fees-for-sending-bitcoin-from-my-blink-wallet-to-another-wallet.md).

# What are the fees for sending Bitcoin from my Blink wallet to another wallet?

The transaction fees vary depending on the type of transaction, whether it's an on-chain transaction or a Lightning transaction.

For sending Lightning payments, a routing fee is paid by the user, but there are no extra fees applied by Blink.

Blink's on-chain transaction fees are composed of:

1. [**Miner fee**](/transaction-fees/what-are-mining-fees.md) — paid according to the current mempool state.
2. **Tiered fixed fee** — varies by withdrawal amount. See the Blink App for current tiers.
3. **Imbalance surcharge** — an additional fee may apply for accounts exceeding the Lightning/on-chain imbalance threshold in a rolling window.

The exact amount of transaction fees may vary depending on the current market conditions and network congestion. See the Blink App for current fees.


---

# 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/transaction-fees/what-are-the-fees-for-sending-bitcoin-from-my-blink-wallet-to-another-wallet.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.