---
title: "Installing Assets"
description: "Install MCAssets files into the supported workflow for a purchased package."
canonical_url: "https://mcassets.net/docs/product-usage/installing-assets"
last_updated: "2026-05-28T01:16:10.896Z"
---

# Installing Assets

Installation depends on the package formats listed on the product page. Always use the format prepared for your target tool first.

## Basic install checklist

- Extract the downloaded ZIP before importing files.
- Keep textures beside the model files when the workflow expects relative paths.
- Use plugin-specific folders for ItemsAdder, Nexo, ModelEngine, or MythicMobs outputs.
- Use `.mimodel` files for Mine-imator workflows.
- Use `.json` files for Vanilla Java resource pack workflows.
- Use `.glb` files for Blender, Cinema 4D, Autodesk Maya, Houdini, Unreal Engine, Unity, or Godot workflows when supported.

## Avoid common mistakes

Do not rename files before the first import unless the package notes tell you to. Do not move textures away from model files until you know how the target tool resolves asset paths.