> For the complete documentation index, see [llms.txt](https://docs.playground.ooo/degen-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playground.ooo/degen-engine/concepts/rendering.md).

# Rendering

The Metadata Renderer is a vital component within the Degen Engine protocol, responsible for generating metadata and media assets for NFTs. As a hybrid renderer, it combines traits to produce a single image or media asset displayed across NFT marketplaces, wallets, and other platforms.

### How the Metadata Renderer Works

When an NFT is created, it is assigned a collection of traits stored within the contract. These traits contain essential information, such as the NFT's name, image, and other metadata. As new traits are added or burned, the renderer automatically updates the NFT's media asset to ensure accurate representation.

Rendering an NFT's media asset involves merging the individual media assets of each trait into one unified asset. For instance, if an NFT possesses traits for the head, torso, and legs, the metadata renderer will combine the respective media assets to generate a complete image of the NFT.

### Benefits of the Metadata Renderer

By merging traits in this manner, the Metadata Renderer facilitates greater flexibility and customization in NFT design. Creators can effortlessly add or remove traits to modify an NFT's appearance or functionality without needing to create an entirely new asset.

Moreover, the Metadata Renderer guarantees consistent NFT representation across all platforms. When users view an NFT on a marketplace or wallet, they see the same media asset generated by the renderer. This consistency creates a unified and standardized user experience for NFTs, which is crucial for widespread adoption of this technology.

{% hint style="info" %}
Users can also create their own Metadata Renderer to render more complex media assets. In this case, they can establish their own rules for calculating and applying Render Order.
{% endhint %}


---

# 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://docs.playground.ooo/degen-engine/concepts/rendering.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.