Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia Ethereum · Entry 251

Burning an NFT: which record disappears and what can remain?

AI-assisted research · separate automated verificationCorrections

Theme
Ethereum
Sources
5 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for Burning an NFT: which record disappears and what can remain?
FactDetailSource
ImplementationA burn entry point is not mandatory in ERC-721.[1]
AuthorizationOpenZeppelin Contracts v5.4.0’s ERC721Burnable checks ownership or approval.[3]
HistoryBurning is represented by events rather than deleting previous chain history.[1][2]
01

Check the collection’s actual burn method

A collection may expose an authorized burn function, restrict it or omit it. The versioned OpenZeppelin ERC721Burnable example permits an owner or approved operator to perform a burn; another contract can impose different rules.

Do not assume an NFT can be destroyed by invoking a function found in an unrelated collection’s interface.

02

An ERC-1155 burn can affect only a quantity

Suppose an address holds five units of one ERC-1155 token ID and the contract authorizes a burn of two. The resulting balance is three units. This is different from removing the token ID everywhere or erasing every holder’s balance.

For an ERC-721 token, a burn concerns the unique token’s live ownership record. Neither operation erases the transactions that led up to it.

03

Destroyed ownership is not deleted content

An NFT can point to offchain metadata and images. Burning the token does not instruct every web server or IPFS node to delete those files. Other people may retain the same content independently.

Likewise, sending a token to an address thought to be inaccessible may leave the contract counting it as owned there. Use the contract’s documented semantics when discussing burned supply.

Direct answers

Questions people ask

Can an approved operator burn an NFT?

It depends on the implementation. OpenZeppelin Contracts v5.4.0 ERC721Burnable permits owners or approved operators, so approval scope can matter beyond a marketplace transfer.

Does burning remove the NFT’s image from the internet?

No. Token accounting and offchain storage are separate. Existing media copies can remain available after a burn.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

Burning an NFT removes the token or quantity from the contract’s live ownership accounting under that contract’s rules. A transfer to an inaccessible address is not necessarily the same operation. ERC-721 does not require a public burn function; some implementations allow owners or approved operators to burn, while others do not expose burning at all.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Implementation: A burn entry point is not mandatory in ERC-721.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Authorization: OpenZeppelin Contracts v5.4.0’s ERC721Burnable checks ownership or approval.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
History: Burning is represented by events rather than deleting previous chain history.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. ERC-721 NFT standardEthereum Improvement Proposals

    Ownership, receiver checks, token-level and operator approvals, mint/burn event semantics.

    Locator: safeTransferFrom; approve; setApprovalForAll; Transfer; metadata · Version / scope: ERC-721 · Retrieved: 2026-10-02T18:55:25.399ZOpen source
  2. ERC-1155 multi-token standardEthereum Improvement Proposals

    Receiver acceptance, collection-wide operators, balance accounting and burn events.

    Locator: Safe transfer rules; operator approvals; minting and burning · Version / scope: ERC-1155 · Retrieved: 2026-10-02T18:55:25.400ZOpen source
  3. OpenZeppelin ERC721BurnableOpenZeppelin

    A versioned example of authorized NFT token destruction, distinct from moving to an inaccessible address.

    Locator: burn · Version / scope: OpenZeppelin Contracts v5.4.0 · Retrieved: 2026-10-02T18:55:25.609ZOpen source
  4. IPFS content addressingIPFS contributors

    A CID identifies content rather than promising a continuously available server.

    Locator: Content identifiers; content addressing · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:25.788ZOpen source
  5. IPFS persistence and pinningIPFS contributors

    Availability depends on nodes retaining and serving content; pinning prevents local garbage collection.

    Locator: Pinning; garbage collection; remote pinning · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:25.704ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

Degrees of Satoshi editorial project. “Burning an NFT: which record disappears and what can remain?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/nft-burning/