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

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.

Evidence: [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721); [ERC-1155 multi-token standard](https://eips.ethereum.org/EIPS/eip-1155); [OpenZeppelin ERC721Burnable](https://raw.githubusercontent.com/OpenZeppelin/openzeppelin-contracts/v5.4.0/contracts/token/ERC721/extensions/ERC721Burnable.sol)

Canonical: https://degreesofsatoshi.com/encyclopedia/nft-burning/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Implementation:** A burn entry point is not mandatory in ERC-721. ([ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721))
- **Authorization:** OpenZeppelin Contracts v5.4.0’s ERC721Burnable checks ownership or approval. ([OpenZeppelin ERC721Burnable](https://raw.githubusercontent.com/OpenZeppelin/openzeppelin-contracts/v5.4.0/contracts/token/ERC721/extensions/ERC721Burnable.sol))
- **History:** Burning is represented by events rather than deleting previous chain history. ([ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721); [ERC-1155 multi-token standard](https://eips.ethereum.org/EIPS/eip-1155))

## 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.

Evidence: [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721); [OpenZeppelin ERC721Burnable](https://raw.githubusercontent.com/OpenZeppelin/openzeppelin-contracts/v5.4.0/contracts/token/ERC721/extensions/ERC721Burnable.sol)

## 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.

Evidence: [ERC-1155 multi-token standard](https://eips.ethereum.org/EIPS/eip-1155)

## 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.

Evidence: [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721); [IPFS content addressing](https://docs.ipfs.tech/concepts/content-addressing/); [IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/)

## Questions

### 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.

Evidence: [OpenZeppelin ERC721Burnable](https://raw.githubusercontent.com/OpenZeppelin/openzeppelin-contracts/v5.4.0/contracts/token/ERC721/extensions/ERC721Burnable.sol)

### 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.

Evidence: [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721); [IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/)

## Claims and scope

### nft-burning-quick-answer

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: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### nft-burning-fact-implementation

Implementation: A burn entry point is not mandatory in ERC-721.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### nft-burning-fact-authorization

Authorization: OpenZeppelin Contracts v5.4.0’s ERC721Burnable checks ownership or approval.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

### nft-burning-fact-history

History: Burning is represented by events rather than deleting previous chain history.

Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [ERC-721 NFT standard](https://eips.ethereum.org/EIPS/eip-721) — Ethereum Improvement Proposals. Ownership, receiver checks, token-level and operator approvals, mint/burn event semantics. Locator: safeTransferFrom; approve; setApprovalForAll; Transfer; metadata. Retrieved: 2026-10-02T18:55:25.399Z.
- [ERC-1155 multi-token standard](https://eips.ethereum.org/EIPS/eip-1155) — Ethereum Improvement Proposals. Receiver acceptance, collection-wide operators, balance accounting and burn events. Locator: Safe transfer rules; operator approvals; minting and burning. Retrieved: 2026-10-02T18:55:25.400Z.
- [OpenZeppelin ERC721Burnable](https://raw.githubusercontent.com/OpenZeppelin/openzeppelin-contracts/v5.4.0/contracts/token/ERC721/extensions/ERC721Burnable.sol) — OpenZeppelin. A versioned example of authorized NFT token destruction, distinct from moving to an inaccessible address. Locator: burn. Retrieved: 2026-10-02T18:55:25.609Z.
- [IPFS content addressing](https://docs.ipfs.tech/concepts/content-addressing/) — IPFS contributors. A CID identifies content rather than promising a continuously available server. Locator: Content identifiers; content addressing. Retrieved: 2026-10-02T18:55:25.788Z.
- [IPFS persistence and pinning](https://docs.ipfs.tech/how-to/pin-files/) — IPFS contributors. Availability depends on nodes retaining and serving content; pinning prevents local garbage collection. Locator: Pinning; garbage collection; remote pinning. Retrieved: 2026-10-02T18:55:25.704Z.

## Revision history

- 2026-10-02: First publication after primary-source research and separate automated verification.

## Cite this entry

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/