Can you update Hedera NFT metadata?

Learn when Hedera NFT metadata can be updated, how token keys affect the operation and why editing a draft is different from changing a minted NFT.

Content reviewed on

Some Hedera NFTs support metadata updates. Whether an update is possible depends on the collection's keys, the operation and the NFT's ownership conditions. Owning an NFT is not, by itself, permission to change its metadata.

Start by identifying what you want to change: a draft, the JSON or media file, or the metadata value recorded for a minted serial.

A draft is still preparation

A draft in DreamForge has not yet become an NFT merely because it has a name and preview. Edit drafts before pinning and minting so the first published result is the one you intend.

Once a serial exists, changing an old draft is not evidence that its on-ledger metadata has changed. Check the actual serial after any update.

An IPFS file has a content address

Publishing changed JSON or artwork to IPFS produces an address for that content. It does not replace the bytes at an existing content address.

If the minted NFT still points to the old JSON, applications will continue to retrieve that version. Changing the NFT's pointer is a separate authorized network operation.

Which key authorizes an update?

Hedera's NFT metadata update operation supports metadata-key authorization. Supply-key authorization also supports certain updates while NFTs remain in the treasury. Check the current rules and actual token configuration rather than assuming one key can change every serial.

Read Hedera's NFT metadata update reference before planning an update across distributed NFTs.

Plan the change before submitting it

Record the token ID, affected serials and current metadata addresses. Prepare the replacement files and inspect their previews. Check that the authorized account or signing arrangement is available for the intended operation.

If collectors already hold the NFTs, explain what is changing and preserve the previous files where appropriate. A technical ability to update metadata is separate from the commitments made to collectors.

Verify the minted result

After a confirmed update, inspect the metadata of the actual serial. Allow for application and gateway caching when checking the display. Keep the transaction reference so a stale preview is not mistaken for a failed update.

An existing minted DreamForge entry with its recorded serial and completed state
An existing confirmed result, shown to explain where the serial appears.

If you cannot establish the available authority, ask SentX support before changing keys or creating replacement NFTs.

Understand token keys or review the metadata structure.

How SentX shows an update

SentX keeps its own copy of each NFT's metadata, image and attributes. After an update on Hedera, run a refresh. It compares the update time recorded on the network with the copy SentX has, and when they differ it reads the metadata, image and attributes again. Run one after every update rather than waiting for the page to change.

What to refreshWhereWho can use it
One NFTFetch Latest from Network, on the NFT page under TraitsThe holder, the collection treasury and SentX staff
Up to 25 serials at a timeThe Refresh metadata card on the collection overview in DreamForgeThe treasury and the collection's authorized wallets
The whole collectionReindex on the collection's Market page in DreamForgeThe treasury and the collection's authorized wallets

The Refresh metadata card unlocks once the collection is on the SentX marketplace. A launch keeps its own copy of each serial's name and image, so make updates before you set up a launch.

NFT images reach the page through a CDN. A new address shows as soon as the refresh reads it. An image replaced at the same web address can keep showing the old version for a while, and a refresh does not clear it.