> 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/features/advanced/change-network-fee.md).

# Change network fee

You can change the network fee when you send funds, or set a default fee priority that new transactions start with. Transactions with low fees may take hours or even days to be confirmed, which can result in delayed or canceled exchanges.

{% hint style="info" %}
**Medium** is a sensible balance of speed and cost, and is a good choice in most cases.

If you want a high chance of your transaction being confirmed quickly and don't mind paying more in fees, move up to **Fast** — or **Fastest** on Monero, Zano and Zcash, the only coins that offer that level. The available levels differ per coin; see the table below.
{% endhint %}

## Change the fee when sending

On the **Send** screen, expand the **Advanced Settings** dropdown — it is collapsed by default and also holds Coin Control — then tap the **Fees** row to open the **Set fees** sheet and choose a priority.

The **Fees** row's subtitle shows the current estimated fee in both crypto and fiat; that estimate is the value, not the row's label.

For Bitcoin and other Bitcoin-family coins, each priority shows an estimated confirmation time and a sat/byte rate. On Bitcoin you can also choose **Custom** to set your own rate.

![](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/send_btc_12_fees_hl.png)

For Monero, Zano and Zcash, pick from the named priorities **Slow**, **Automatic**, **Medium**, **Fast**, and **Fastest**.

![](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/send_xmr_03_fee-priority.png)

For Ethereum and tokens, the fee is the gas paid in the chain's native coin — for example, ETH on Ethereum.

## Fee levels by coin

| Coin                                     | Fee levels                                                                          |
| ---------------------------------------- | ----------------------------------------------------------------------------------- |
| Bitcoin                                  | Fast, Medium, Slow (shown as `Slow ~24hrs+`), and **Custom**                        |
| Litecoin, Bitcoin Cash, Dogecoin, Decred | Fast, Medium, Slow — no **Custom**                                                  |
| Ethereum, Polygon, Base, BNB Smart Chain | Fast, Medium, Slow                                                                  |
| Monero, Zano, Zcash                      | Slow, Automatic, Medium, Fast, Fastest                                              |
| Solana, Tron, Arbitrum                   | None. A **Fees** row appears with a read-only estimate, but tapping it does nothing |
| Nano                                     | None, and no **Fees** row at all                                                    |

{% hint style="warning" %}
There is no **Regular** fee level on any coin. **Fastest** and **Automatic** exist only on Monero, Zano and Zcash, and **Custom** exists only on Bitcoin.
{% endhint %}

## Set your default fee priority

To choose the fee priority that new transactions start with, set a per-wallet default:

{% stepper %}
{% step %}
Tap the **Settings** gear in the top-right corner of the home screen.
{% endstep %}

{% step %}
Under **Wallet settings**, tap **Other**.
{% endstep %}

{% step %}
Tap **Fee priority** and select an option.
{% endstep %}
{% endstepper %}

This default applies to that wallet (for example, "Automatic" on a Monero wallet). You can still change the fee for any individual transaction from the Send screen.

The **Fee priority** row is only present on coins that have fee levels, so you will not see it on Solana, Tron, Arbitrum, Nano or Banano.

## Speed up a stuck Bitcoin transaction

If a Bitcoin transaction is taking too long to confirm, you can rebroadcast it at a higher fee using Replace-by-Fee (RBF).

{% hint style="info" %}
**Bump fee** only appears when all of the following are true. If you cannot find the option on a transaction, one of these conditions is not met — there is no setting to switch on.

* **The wallet is a Bitcoin wallet.** Bumping is not offered on Litecoin, Bitcoin Cash, Dogecoin, Decred, Monero, Zano, Zcash, or any EVM chain.
* **The transaction is outgoing.** You can only bump a payment you sent, never one you received.
* **The transaction is still replaceable** — that is, unconfirmed and signalling RBF.
* **The recipient was not a Silent Payments address.** Cake Wallet deliberately disables bumping for sends to a Silent Payments address.
  {% endhint %}

{% stepper %}
{% step %}
From your transaction history, open the outgoing Bitcoin transaction you want to speed up.
{% endstep %}

{% step %}
Tap **Bump fee** to rebroadcast the transaction with a higher fee.
{% endstep %}
{% endstepper %}

![](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/send_btc_16_tx-details_hl.png)


---

# 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://docs.cakewallet.com/features/advanced/change-network-fee.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.
