> For the complete documentation index, see [llms.txt](https://upland-3d.gitbook.io/upland-3d/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upland-3d.gitbook.io/upland-3d/go-karts/nft.md).

# NFT

## Specifications

* File type: GLTF
* File size:< 10MB
* Triangles limit 20,000 max
* 2 mandatory meshes (carbody and wheel) - *Check img\_1*

<figure><img src="/files/3Dczo9gw6JuPin2CFDyk" alt=""><figcaption><p>Mandatory meshes. img_1</p></figcaption></figure>

* Texture Size for car body mesh: 2048x2048&#x20;

### Details and Limitations

<figure><img src="/files/bqBqnF9wOl4JdT8F2UWH" alt="" width="375"><figcaption><p>size limit box. img_4</p></figcaption></figure>

* Attached your design to the size limitation guide *Check img\_4*

<figure><img src="/files/eP5STNAnjY3ctKLiNMdj" alt=""><figcaption><p>img_4_b</p></figcaption></figure>

* *Include your design in the empty area as shown in img\_4\_b*

<figure><img src="/files/NDNJJVZ7qVcrfSxHq4Un" alt="" width="375"><figcaption><p>baked_carbody material selection. img_5</p></figcaption></figure>

* Baked\_carbody material should be assigned to the main body part that provides the actual color and characteristics of the mesh. *Check img\_5*

### Deliverable files for NFT trim

<figure><img src="/files/jQb5Egra0cximN18VrWK" alt=""><figcaption><p>Material setup before exporting - img_6</p></figcaption></figure>

* GLTF files request

When exporting the GLTF be sure to pick the following values:

<figure><img src="/files/KUStvKSnrCn0kNcq2RND" alt="" width="375"><figcaption></figcaption></figure>

* You should export two different GLTF for this file:
  * One should not include any baked texture images. Share it as a separate JPG file
  * The other version should include the baked images&#x20;
* Roughness Map is allowed to be attached for both files
* UVmaps
  * baked\_carbody.jpg
  * wheel.jpg


---

# 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 dynamically by asking a question.

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

```
GET https://upland-3d.gitbook.io/upland-3d/go-karts/nft.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.