Zcash Transaction Fees Explained

Key Facts

• One ZEC equals 100,000,000 zatoshis; 10,000 zatoshis equals 0.0001 ZEC.
• ZIP 317 uses 5,000 zatoshis per logical action and charges for at least two actions.
• The formula treats transparent, Sapling, and Orchard components by their public processing footprint rather than charging extra simply for privacy.
• Fees are public and are designed to be computable from public transaction data.
• A wallet can pay a non-conventional fee, but underpaying may hurt relay or inclusion and unusual values can weaken privacy.
• Old pages quoting a flat 0.00001 ZEC default describe the obsolete ZIP 313 era, not the current ZIP 317 convention.

The current short answer

For an ordinary minimal Zcash transfer, the current conventional fee is 10,000 zatoshis, or 0.0001 ZEC. That number comes from ZIP 317: a 5,000-zatoshi marginal fee multiplied by the greater of two grace actions or the transaction's calculated logical actions.

It is a convention used by wallets and node policy, not a fixed consensus tax on every transaction. A transaction builder can choose another value, but nodes and miners use fee policy when relaying, retaining, and selecting transactions. For normal users, the useful number is the fee shown by a maintained wallet at approval time.

Why Zcash stopped using one flat fee

The older ZIP 313 convention reduced the default to 1,000 zatoshis regardless of transaction shape. That made a simple transfer and a transaction with hundreds of outputs pay the same amount even though they imposed very different work on nodes. ZIP 317 replaced that flat convention with a proportional mechanism.

The goal is not to make shielded ZEC expensive. It is to charge by public processing footprint while preserving room for privacy padding. A normal one-recipient transaction with change stays inside the two-action grace window, while transactions with more inputs, outputs, or shielded actions scale upward.

What a logical action means

For Orchard, the contribution is the number of Orchard actions. For Sapling, it is the larger of Sapling spends or outputs. Transparent contribution is based on the encoded size of inputs and outputs relative to standard P2PKH components. The formula then sums the relevant pool contributions for the transaction.

This abstraction matters because an Orchard action can combine an input and an output. Charging a naive inputs-plus-outputs total would penalize Orchard's structure. ZIP 317 instead aims for comparable network cost across transparent and shielded components.

Why the minimum uses two actions

A useful transfer normally needs an output for the recipient and an output for change. Zcash transaction builders also pad shielded input and output counts to reduce information leakage from transaction arity. The two-action grace window lets that ordinary padding happen without doubling the fee simply because the wallet protects a user from a shape-based fingerprint.

With a 5,000-zatoshi marginal fee and two grace actions, the minimum conventional result is 10,000 zatoshis. Once the logical-action count exceeds two, the conventional fee rises linearly in 5,000-zatoshi increments under the current active revision.

Fees are public even in shielded transfers

A fully shielded Zcash payment can encrypt sender, recipient, amount, and memo fields, but the transaction fee is public. ZIP 317 explicitly requires that the conventional fee be computable from public transaction data so calculating it does not require leaking private wallet selection information.

That is also why unusual manual fees are a bad default. A distinctive fee can become one more observable feature used to correlate activity. Zcash's privacy guidance recommends relying on privacy-focused wallet policy rather than choosing a personal fee signature for every payment.

When a Zcash fee becomes larger

A transaction can cross the grace window when it consumes many transparent UTXOs, spends many shielded notes, creates many outputs, or uses several pool components. Dust consolidation, batch payments, migration work, and complex cross-pool construction can therefore cost more than a simple payment.

A test transfer is a separate transaction, so it pays its own fee. Shielding a transparent deposit is also a separate transaction. Those costs are normally small, but a guide should say so plainly instead of calling a multi-step workflow free.

Why underpaying can leave a transaction behind

Nodes may apply a low-fee penalty, evict transactions under mempool pressure, or decline to relay transactions that fall too far below policy. ZIP 317 also recommends a block-template selection algorithm that favors transactions paying at least the conventional fee while limiting unpaid logical actions.

Paying more does not buy an unlimited priority lane, and paying less is not a clever privacy trick. If a current wallet reports an unexpected fee, first inspect the number of inputs, outputs, or notes it is using and confirm the software version before forcing a custom value.

Read fee claims with a date attached

Zcash fee guidance changed from ZIP 313 to ZIP 317 and continues to evolve through draft revisions for new transaction components. As of July 19, 2026, ZIP 317 Revision 0 is active; its Ironwood and memo-bundle revisions are still marked Draft in the official ZIP. A future network upgrade can therefore change the applicable contribution set without changing this article's URL.

For a real transfer, trust the current wallet review screen and the current official ZIP over an old search snippet. This page explains the mechanism and the present baseline; it is not a live mempool quote or a substitute for the fee the transaction builder actually constructs.

FAQ