Zcash Memo Field Explained: Messages in Zcash Transactions
Zcash Memo Field Explained: Private Messaging in Transactions
Most blockchains let you send money. Zcash lets you attach a note to it, and that note is encrypted.
The Zcash Memo Field turns a payment into something closer to a sealed envelope: the amount and the message travel together, and only the recipient is meant to open it.
The Zcash Memo Field is a 512-byte space inside a shielded payment. It is encrypted along with the rest of the note, so it is meant for the recipient, not for public view.
It cannot be used on transparent payments, and the text format is a wallet convention rather than a consensus rule.
What Is the Zcash Memo Field?
Every shielded output in Zcash carries a fixed memo slot of 512 bytes. A sender can fill it with a short message, an invoice number, a reply address, or leave it empty.
Because it is part of the encrypted note, it does not appear in plain view on the chain the way a transparent transaction would.
Think of paying a friend back for dinner and writing "Thanks for Friday" on the envelope. Here the envelope is locked, and the note inside is locked with it.
How the Zcash Memo Field Is Formatted
The chain itself only stores 512 bytes. What those bytes mean is up to software, and ZIP 302, still a draft, describes the convention.
It builds on the protocol's own memo encoding, and it constrains how clients read a memo, not what the network accepts. The first byte decides how to interpret the rest:
0xF4 or lower: UTF-8 text. The reader trims trailing zeros and decodes the message.
0xF6 followed by all zeros: no memo at all.
0xF7 to 0xFE: reserved for future use.
0xFF: arbitrary data. The ZIP recommends this for private, non-standard use, with the other 511 bytes unconstrained.
0xF5: a legacy value used inconsistently in the past, so applications are told to prefer 0xFF.
If a text memo fails to decode as valid UTF-8, the reader should report an error. In practice, that means a message written by one app may look odd in another that follows a different convention.
Who Can Read the Zcash Memo Field?
The recipient's wallet can decrypt the Zcash memo field because the memo travels inside the note sent to them.
Anyone who holds the right viewing key can also read it, so sharing a viewing key with an accountant, auditor, or app shares the memos too.
For the wider picture of how shielded transfers hide details, see our guide to Zcash privacy and shielded transactions.
One limit is easy to forget: anyone who knows your shielded address can send you a memo.
Treat unexpected messages and links as you would an unknown email. Because the memo is encrypted, a public block explorer will not show its contents; our Zcash Blockchain Explorer guide explains what you can and cannot see on-chain.
Zcash Memo Field and Transparent Addresses
Memos belong to shielded payments only. ZIP 321, the payment request standard, says a request that attaches a memo to a transparent address must be rejected as invalid.
If you are paying someone through a unified address, the memo can only go with a shielded receiver.
A transparent fallback has no place to put it, so check what your wallet does before relying on a memo to carry something important.
Our Zcash Wallet Guide is a good place to compare wallets that handle shielded payments.
Sending a Zcash Memo Field Through Payment Requests
ZIP 321 lets a payment link carry a memo so the sender's wallet can prefill it. Three details matter:
The memo is base64url encoded, without padding.
The decoded size cannot exceed 512 bytes; shorter memos are padded with zeros.
Where a request has several payments, an index ties each memo to its address.
Merchants and apps use the Zcash Memo Field this way to match a payment to an order without asking the customer to type a reference. That is one of several practical examples in our overview of Zcash use cases.
Common Uses for the Zcash Memo Field
Invoice or order references, so a business can match payments.
Reply addresses, since the ZIP 316 interaction model mentions in-band "reply-to" memos as one way of sharing an address.
Short personal notes, such as thanks or a payment reason.
Application data, using the 0xFF arbitrary format.
Keep anything truly sensitive short and minimal. The memo is private in transit, but the recipient can screenshot, copy, or store it.
Limits and What Is Changing in the Zcash Memo Field
Today, each shielded output reserves 512 bytes, and a typical transaction is padded to two outputs.
That wastes space and limits what a memo can hold. Block space and size also feed into what a transfer costs, a topic we unpack in Zcash Transaction Fees.
ZIP 231, a draft, proposes memo bundles: one shared memo per transaction, split into encrypted chunks and up to 16 KiB in size.
It is not deployed, and the ZIP states it is not part of Network Upgrade 7. Treat it as a proposal that could change, not a feature to plan around.
Final Thoughts on the Zcash Memo Field
The Zcash Memo Field is a small feature with a clear job: carry a private note alongside a shielded payment.
It works well for references and short messages, and it is not a general-purpose chat channel.
Know that the Zcash Memo Field's format is a convention, that transparent payments cannot carry one, and that a viewing key reveals what it holds.
Check your wallet's own documentation for how it displays and sends memos, and watch the draft proposals before relying on future changes.
If you follow ZEC as a market as well as a technology, our Zcash Price Prediction page covers the price side, where forecasts remain opinions.
Disclaimer: This article is general educational information about Zcash memos and is not financial, investment, legal, or tax advice. Crypto transactions are irreversible, and privacy depends on correct wallet use and cannot be guaranteed.
