# Tokenizing parent assets
Tokenizing a parent asset makes a gaming asset available for reuse inside the Interoperable Asset Store. After a collection is created or imported and contains tokenized assets, users can upload the required files, set technical details, and prepare each asset for receiving reuse proposals from other studios.
To begin tokenizing a parent asset, navigate to your **profile** and select any asset in your possession. Each asset page contains an option to list or register the asset for reuse inside the protocol.
### **Listing an asset for reuse**
To tokenize an asset:
1. Open your **profile** and select the **Assets** tab.
2. Click the asset you want to tokenize.
3. Click the **List** button on the asset page.
4. A modal will appear, allowing you to define listing parameters and upload files.
The listing modal contains several fields used to prepare the asset for registration in the Interoperable Asset Store. These include:
#### **Listing duration**
Controls how long the asset will be available for reuse proposals.\
Users can choose from preset durations.
#### **Royalty percentage**
Defines the creator’s royalty rate for every approved reuse of the asset.\
This percentage is enforced automatically by the protocol.
#### **Game engine**
Indicates which engine the asset is built for, such as Unity or Unreal.\
This helps other studios understand compatibility before submitting a reuse proposal.
#### **Technical details**
Users can specify:
* whether the asset is rigged
* whether animations are included
* whether textures are included
* polygon count
* any additional notes about the model
These details help other studios evaluate whether the asset fits their game requirements.
### **Uploading asset files**
Every tokenized parent asset must include a **ZIP file** containing the source asset files.\
The ZIP file should include everything required for reuse, such as:
* 3D models (FBX, OBJ, BLEND, etc)
* textures
* animation files
* materials
* rigs or skeletons
Users can upload any combination of files depending on the type of asset they are creating. These files are encrypted before being uploaded to IPFS, ensuring the asset remains protected until reuse is approved.
### **Uploading a preview model (optional but recommended)**
Users can upload a **GLB preview model** so that other studios can inspect the asset directly in the web application. A high-quality GLB preview greatly improves visibility and increases the chance of receiving reuse proposals.
#### **Recommended best practices for GLB files**
* separate animations by name based on your 3D software workflow
* ensure the GLB renders correctly in the browser
* test lighting and materials before uploading
* keep the GLB optimized for fast loading
The GLB file is displayed in the interactive 3D viewer on the asset page, allowing studios to inspect the asset before submitting a proposal.
### **Finalizing the parent asset**
After completing the listing modal and uploading the files, click **Submit**.\
The protocol will:
* encrypt the source files
* store the encrypted ZIP on IPFS
* register the parent asset on-chain
* attach the preview model
* finalize the metadata
Once the asset is tokenized, it becomes visible in the collection and available for reuse proposals.
---
# 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://infinity-games.gitbook.io/infinity-games-docs/using-the-interoperable-asset-store/tokenizing-parent-assets.md?ask=
```
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.