> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/creator/scene-editor/build/nfts.md).

# NFTs

Adding NFT Portraits to your scenes

You can add NFTs (Non-Fungible Tokens) into your scene, displayed as picture frames.

All image and gif formats that are supported in OpenSea are also supported by Decentraland by picture frames. NFTs in video or audio format are currently not supported. NFTs that also have 3D representations, like Decentraland wearables, are displayed in picture frames as 2D images.

## Adding an NFT

Use the NFT smart item, that you can find in the **Smart Items** asset pack, or by simply searching *NFT* in the search bar above. Once you drag a copy of the NFT item to your scene and select it, there are a few fields that you can configure.

![](https://45449780-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoPnXBby9S6MrsW83Y9qZ%2Fuploads%2Fgit-blob-81fe7d71b8b9e2f56a1ec942daa856fc4e7e2747%2Fnft-item.png?alt=media)

The main fields to configure determine what NFT to display:

* **Network**: The blockchain network that your NFT is in. It uses Ethereum mainnet by default, but you can also pick Polygon (matic), or one of several test networks.
* **Contract**: The contract address of the collection that this NFT belongs to (ie: Cryptokitties, SuperRare, Decentraland Halloween Wearables 2019, etc)
* **Token**: The unique id of this specific NFT

To obtain these, the simplest way is to look them up in the Decentraland Marketplace and then check the URL. For example, from the URL of the following item:

*<https://market.decentraland.org/contracts/0xb932a70a57673d89f4acffbe830e8ed7f75fb9e0/tokens/20175>*

You can infer that the contract is *0xb932a70a57673d89f4acffbe830e8ed7f75fb9e0* (referring to SuperRare) and the ID is *20175*.

Similarly, you can also obtain these from the OpenSea URL of the token. For example, from the URL of the following item:

*<https://opensea.io/assets/0x31385d3520bced94f77aae104b406994d8f2168c/2614>*

You can infer that the contract is *0x31385d3520bced94f77aae104b406994d8f2168c* and the ID is *2614*.

Other optional fields that can be configured in the NFT smart item are:

* **Frame style**: The default frame style has a glowing margin that might not match the style of the artwork or your scene. There are several other options to pick from with varying styles, from baroque to minimalist, or even tape on the painting's corners.
* **Color**: NFTs with transparent background are given a background color, violet by default. You can choose any other color. Note that some frame styles, like *None*, don't include a background color at all.

{% hint style="warning" %}
**📔 Note**: You can only see these changes take effect when entering the scene in Preview mode. None of these changes modify the representation of the smart item that you drag around in edit mode.
{% endhint %}

See [Display an NFT](/creator/scenes-sdk7/media/display-a-certified-nft.md) for more details on how Decentraland handles NFT portraits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decentraland.org/creator/scene-editor/build/nfts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
