> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ton.org/llms.txt
> Use this file to discover all available pages before exploring further.

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.ton.org/feedback

```json
{
  "path": "/standard/tokens/nft/overview",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# NFT: Non-fungible token

Non‑fungible tokens (NFTs), defined in [TEP‑62](https://github.com/ton-blockchain/TEPs/blob/0d7989fba6f2d9cb08811bf47263a9b314dc5296/text/0062-nft-standard.md), represent the digital embodiment of uniqueness within the TON ecosystem. Unlike their fungible counterparts, each NFT possesses distinct characteristics that make it irreplaceable and non‑interchangeable. This fundamental property of uniqueness enables NFTs to serve as digital certificates of authenticity for a wide array of digital and physical assets.

NFTs can verify ownership of digital assets using blockchain technology. Each token carries a unique identifier and associated metadata that distinguish it from every other token. This uniqueness makes NFTs particularly valuable for representing assets where individual characteristics matter.

Use cases:

* Digital art
* Real-world assets
* Access rights

The technical implementation of NFTs in TON mirrors the distributed architecture philosophy found in [Jettons](/standard/tokens/jettons/overview). Individual item contracts represent each NFT, while collection contracts manage overall collection metadata and coordinate minting processes. This distributed approach ensures that NFT operations remain efficient and scalable even as collections grow to encompass thousands or millions of individual tokens.

## Architecture and smart contracts

NFTs in TON are built using a distributed smart contract architecture consisting of:

* NFT collection contracts – serve as the source of truth for items, providing addresses, collection metadata, and coordinating the overall collection.
* NFT item contracts – each NFT is represented by its own smart contract account, storing the collection address, index, current owner, and individual metadata.

This architecture ensures that each NFT operates independently while maintaining a connection to its collection.

## Transfer mechanism

The current owner sends a transfer message to the NFT item contract, which updates the owner field and optionally sends notifications to the new owner along with any excess Toncoin. [This transfer flow](/standard/tokens/nft/how-it-works#transfer-nft-item) ensures atomicity while maintaining flexibility for ownership notifications and handling remaining funds.

## Marketplace-ready templates

To deploy NFTs compatible with existing TON marketplaces, use contract implementations that follow the [NFT standard](/standard/tokens/nft/how-it-works).

Implementations include:

* [TON reference NFT contracts](https://github.com/ton-blockchain/nft-contract) – reference implementation of the TON NFT standard.
* [Getgems NFT contracts](https://github.com/getgems-io/nft-contracts) – NFT contracts used by the Getgems marketplace.