YSM model formats: folder, zip and encrypted .ysm
Yes Steve Model (YSM) loads custom player models in three different container formats: unpacked folders, compressed archives, and encrypted .ysm files. Understanding how each format works and where to place your files inside the game directory is the essential first step for both players installing models and creators distributing them.
Supported Bedrock File Standards
At its core, Yes Steve Model is powered by the geckolib rendering engine. Because of this foundation, your raw geometry and animation files must follow standard Minecraft Bedrock Edition specifications.
Specifically, the mod supports Bedrock Edition 1.12.0 and above for model geometry files, alongside Bedrock Edition 1.8.0 for animation files. Starting from YSM version 2.3.0, the engine also supports Bedrock Edition animation controllers and animation audio.
The Three Model Container Formats
YSM recognizes three distinct ways to package a model. All three work identically once loaded into the game, so you can choose the format that best fits your current workflow:
1. Folder format: An uncompressed folder containing your raw model files. This is the recommended format for model creators because you can edit textures, geometry, or animations directly and reload them in-game immediately for rapid testing.
2. Compressed package format (zip): A direct archive package of a model folder. This format keeps all assets inside a single file, making it convenient for sharing open-source models with other players.
3. ysm format (.ysm): An encrypted, single-file package created from a model folder. Creators use this format to distribute finished models publicly while preventing others from extracting, editing, or stealing the raw assets.
Where to Place Model Files
All model data is stored inside your Minecraft instance folder under the path config/yes_steve_model. When you launch the game with YSM installed, the mod automatically manages several subdirectories inside this folder:
• custom: Place your downloaded or created models here if you want them to be usable by anyone immediately without requiring authorization.
• auth: Place custom models here if they must be authorized before a player is allowed to equip them (commonly used on servers).
• builtin: Holds the default models bundled with the mod. Do not put your own work here, because this folder is wiped and regenerated every time the game starts.
• cache: Stores encrypted model data automatically downloaded from multiplayer servers.
• export: Receives your newly encrypted .ysm files whenever you run the in-game export command.
<Minecraft Directory>/config/yes_steve_model/
├── auth/ (Custom models requiring authorization)
├── builtin/ (Default models - wiped on every launch!)
├── cache/ (Server model cache)
├── custom/ (Custom models free for immediate use)
└── export/ (Output directory for /ysm export)Subfolders and File Naming Rules (Since 2.2.1)
In older versions of the mod, renaming files or accidentally extracting a zip inside an extra folder could prevent a model from loading. Starting from version 2.2.1, YSM automatically scans nested subfolders up to 16 layers deep inside both the custom and auth directories.
You can organize your collection into categorized subfolders, and you can freely rename archive or .ysm files using any characters—including spaces and non-English characters like Chinese—without breaking model recognition.
Exporting and Using Encrypted .ysm Models
When you finish building a model in folder format and want to protect your work before sharing, you can convert it into the encrypted ysm format using an in-game command. Keep in mind that encryption is permanent and one-way: an encrypted .ysm file cannot be converted back into a regular folder and cannot be edited again.
Starting from version 2.2.2, you can also attach custom text metadata (such as author credits or version notes) using the optional extra_info argument. When someone opens a .ysm file (exported in YSM 1.2.0 or later) in a text editor like Notepad, this header information is readable at the top of the file. However, the header is protected against tampering—if anyone edits that text in Notepad, YSM will refuse to load the file.
Also note that the .ysm format is only backward-compatible (newer mod versions can load older files, not vice versa). If you export a model using a newer version of YSM, players running an older version of the mod will not be able to load it.
- Place your working model folder inside config/yes_steve_model/custom (or auth) so the game loads it.
- Launch Minecraft, enter a world, and run the export command with your model's ID.
- Retrieve the generated .ysm file from config/yes_steve_model/export.
# Basic export command
/ysm export <model_id>
# Export with custom header text (since version 2.2.2)
/ysm export <model_id> [extra_info]Questions
Where do I put a model I just downloaded?
Drop the folder, zip archive, or .ysm file into your game directory under config/yes_steve_model/custom. Since version 2.2.1, you can even organize them inside subfolders up to 16 levels deep.
Why did the models I put in the builtin folder disappear?
The config/yes_steve_model/builtin folder is strictly reserved for the mod's default assets. YSM deletes and regenerates this entire folder every time you launch Minecraft. Always use the custom or auth folders instead.
Can I unpack a .ysm file to edit its texture or animations?
No. The .ysm format is an encrypted distribution format. Once a folder model is exported to .ysm, it cannot be converted back into raw files or modified a second time.
Why won't my exported .ysm model load for a friend or after I edited its text?
There are two common reasons: First, the friend might be using an older version of the YSM mod than the version you used to export the file. Second, if anyone opened the .ysm file in a text editor like Notepad and altered the readable header information, the mod's integrity check will reject the file.