# AnimeStudio: opening Unity bundles, encrypted ones included
> AnimeStudio is a Windows tool that opens Unity asset bundles, handles the encrypted bundles used by Genshin Impact, Star Rail and Zenless Zone Zero, and exports textures, meshes, animations, audio and shaders from a GUI or a CLI. The first decision it asks you to make is which game you are extracting from, because the decryption differs per title.
**Escartem/AnimeStudio** — Asset extraction tool for unity games, supports many encrypted titles including all Hoyoverse ones (*ﾟ∀ﾟ*)
- Repository: https://github.com/Escartem/AnimeStudio
- Stars: 1,294 · Forks: 215
- Language: C++
- License: MIT
- Published: 2026-10-19 · Updated: 2026-10-19 · Language: en
- Canonical page: https://hysenlabs.com/projects/escartem-animestudio
## It opens bundles and shows you what is inside
AnimeStudio opens Unity bundles and lets you browse, preview and export their contents, which the README lists as textures, meshes, animations, audio, shaders and text assets. It handles the encrypted bundles used by Genshin Impact, Star Rail and Zenless Zone Zero and their other upcoming titles, it works on a long list of other encrypted games, and it works on regular Unity games too.
That last clause matters for how you think about the tool. This is not a Hoyoverse special case with a general purpose fallback, it is a general Unity asset reader with decryption support for the titles that need it.
The project ships as a GUI and a CLI in the same download. The README is explicit about which one to use: the GUI is what you want if you are just looking for assets, and the CLI is there for scripting and batch exports. That split is the same as a lot of extraction tooling, and it is the right one, because browsing an install interactively and dumping ten thousand textures on a schedule are different jobs with different interfaces.
The implementation is C++ and .NET together, with a native library layer and a managed application layer. The repository layout shows the split, with AnimeStudio.GUI/ and AnimeStudio.CLI/ as the two applications, AnimeStudio/ holding the core, and separate directories for the native pieces, AnimeStudio.Ooz/, AnimeStudio.FBXNative/, AnimeStudio.FBXWrapper/, AnimeStudio.HLSLDecompiler/, AnimeStudio.ACL/, AnimeStudio.PInvoke/, AnimeStudio.Patcher/ and AnimeStudio.Utility/. The licence is MIT.
## The game selector is the first decision, and the wrong choice gives garbage
The usage instructions are short, and the first line carries the most important warning in the README. You pick your game in the game selector first, and only then load a file or a folder, because each game has its own decryption, and loading with the wrong one selected will either fail or give you garbage.
That failure mode is worth dwelling on. A tool that said wrong game, try again would be an annoyance. A tool that produces plausible looking but corrupted assets is a trap, because you do not notice until you have exported thousands of files. The list has over 50 entries, including separate ones for closed beta versions, so the advice is to take the one that matches the build your files come from, and a build from a beta is a different entry from the release.
Once the game is right, the loop is ordinary. Load a file or a folder, browse the list, and export what you want. Assets can be filtered by type, by name or by container path, and most types can be previewed before exporting, which saves the export of the thousand textures you did not want.
The container path filter is the one that matters at scale. Unity bundles are organised into container paths that mirror the game's asset folder structure, so filtering by path is how you export one character, one environment set or one UI skin rather than the whole install.
The README also points at the official wiki for detail, at an original tutorial by Modder4869, and at the original readme of the project it descends from, RazTools' Studio, which is the historical starting point for this kind of tool.
## The Asset Browser is the answer to a game install you cannot load every time
For big dumps there is the Asset Browser, and it is the part of the tool that shows real design rather than just functionality.
It builds a map of everything in a game install, so you can search it without loading the whole thing every time. On a modern Hoyoverse title the install is large enough that loading it repeatedly is the difference between a usable tool and an unusable one, so a persistent index is the enabling feature rather than a convenience.
The maps have three properties worth knowing. They can be saved as message pack or json, so the format is a choice rather than a constraint, and message pack is the faster one for a large index. They can be relocated to a different install folder, which means a map built on one machine can be reused when the install moves or when you want to compare against a copy elsewhere. And two of them can be loaded side by side to see what changed between versions.
That last one is the genuinely useful feature for modding work. A game update is a diff, and if you can see which assets were added, changed or removed between two builds, you know what your mod has to account for without diffing two directories of binary files by hand.
The CLI exposes the same machinery through the --map_op and --map_type flags, so the map can be built in a script rather than only in the GUI.
## The CLI takes the same options as flags
The command line interface mirrors the GUI options, and the README gives a single worked example with an input path and an output path.
```
AnimeStudio.CLI.exe