# NFT Metadata

The NFT Metadata refers to all the information attached to each NFT  you mint/create.

Usually, most Hedera NFTs follow the [HIP-412](https://hips.hedera.com/hip/hip-412) Metadata Scheme, which is a standard widely adopted by the community to agree on what information NFTs should contain.

These are the 3 main elements all NFTs should contain:

<figure><picture><source srcset="/files/WwKGwetbzn0wjZHihK87" media="(prefers-color-scheme: dark)"><img src="/files/8J2co72tVxjccQBMAMxB" alt=""></picture><figcaption><p>NFT Metadata inputs in Kabila Tools - NFT Creation</p></figcaption></figure>

### 1. Main Media File (Mandatory)

All NFTs must contain a main Media File. A file that could be an image (.PNG or .JPG), a GIF, a video (.mp4), an audio file (.mp3), a 3D file (.glb), etc.

You'll always need to define a main media file for each NFT you create.

This Main Media File will be used by Wallets and Marketplaces to display the NFT.

### 2. NFT Information (Mandatory)

On Hedera, this typically refers to the NFT´s written information:

* **Name.** The name of the NFT.
* **Creator.** The name of the brand or artist.
* **Description.** The description of the NFT (usually around 300-500 characters).

### Attributes and Properties (Optional)

Additionally to the main NFT information, an NFT could include:

* **Attributes.** Additional pieces of structured information, commonly used for traits in PFP Collections.
* **Properties.** Additional attached files (images, videos, 3D files, PDFs, etc).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://academy.kabila.app/nft-academy/hedera-nfts/nft-metadata.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
