A Unity asset extractor for Python based on AssetStudio.
Python 3.6.0 or higher is required
pip install UnityPyor download/clone the git and use
python setup.py installThe following is a simple example.
import os
import UnityPy
def unpack_all_assets(source_folder : str, destination_folder : str):
# iterate over all files in source folder
for root, dirs, files in os.walk(source_folder):
for file_name in files:
# generate file_path
file_path = os.path.join(root, file_name)
# load that file via UnityPy.load
env = UnityPy.load(file_path)
# iterate over internal objects
for obj in env.objects:
# process specific object types
if obj.type in ["Texture2D", "Sprite"]:
# parse the object data
data = obj.read()
# create destination path
dest = os.path.join(destination_folder, data.name)
# make sure that the extension is correct
# you probably only want to do so with images/textures
dest, ext = os.path.splitext(dest)
dest = dest + ".png"
img = data.image
img.save(dest)
# alternative way which keeps the original path
for path,obj in env.container.items():
if obj.type in ["Texture2D", "Sprite"]:
data = obj.read()
# create dest based on original path
dest = os.path.join(destination_folder, *path.split("/"))
# make sure that the dir of that path exists
os.makedirs(os.path.dirname(dest), exist_ok = True)
# correct extension
dest, ext = os.path.splitext(dest)
dest = dest + ".png"
data.image.save(dest)You probably have to read Important Classes and Important Object Types to understand how it works.
People who have slightly advanced python skills should take a look at AssetBatchConverter.py for a more advanced example.
Environment loads and parses the files that are given to it. It can be initialized via:
- a file path - apk files can be loaded as well
- a folder path - loads all files in that folder (bad idea for folders with a lot of files)
- a stream - e.g. io.BytesIO, filestream,...
- a bytes object - will be loaded into a stream
UnityPy can detect itself if the file is a WebFile, BundleFile, Asset or APK itself.
The unpacked assets will be loaded into .files, which is a dict consisting of asset-name : asset.
The all objects of the loaded assets can be easily accessed via .objects,
which itself is a simple recursive iterator.
import io
import UnityPy
# all of the following would work
src = "file_path"
src = b"bytes"
src = io.BytesIO(b"Streamable")
env = UnityPy.load(src)
for obj in env.objects:
passAssets are a container that contains multiple objects. One of these objects can be an AssetBundle, which contains a file path for some of the objects in the same asset.
All objects can be found in the .objects dict - {ID : object}.
The objects which have a file path can be found in the .container dict - {path : object}.
Objects contain the actual files which, e.g. textures, text files, meshes, settings, ...
To acquire the actual data of an object it has to be read first, this happens via the .read() function. This isn't done automatically to save time because only a small part of the objects are of interest. Serialized objects can be set with raw data using .set_raw_data(data) or modified with .save() function if supported.
All object types can be found in UnityPy/classes.
.name.imageconverts the texture into aPIL.Image.m_Width- texture width (int).m_Height- texture height (int)
Export
for obj in env.objects:
if obj.type == "Texture2D":
data = image.read()
data.image.save(path)Sprites are part of a texture and can have a separate alpha-image as well. Unlike most other extractors (including AssetStudio) UnityPy merges those two images by itself.
.name.image- converts the merged texture part into aPIL.Image.m_Width- sprite width (int).m_Height- sprite height (int)
Export
for obj in env.objects:
if obj.type == "Sprite":
data = image.read()
data.image.save(path)TextAssets are usually normal text files.
.name.script- binary data (bytes).text- script decoded via UTF8 (str)
Some games save binary data as TextFile, so it's usually better to use .script.
Export
for obj in env.objects:
if obj.type == "TextAsset":
data = image.read()
with open(path, "wb") as f:
f.write(bytes(data.script))MonoBehaviour assets are usually used to save the class instances with their values. If a type tree exists it can be used to read the whole data, but if it doesn't, then it is usually necessary to investigate the class that loads the specific MonoBehaviour to extract the data. (example)
.name.script.raw_data- data after the basic initialisation
Export
import json
for obj in env.objects:
if obj.type == "MonoBehaviour":
data = image.read()
if data.type_tree:
with open(path, "wt", encoding="utf8") as f:
json.dump(data.type_tree.to_dict(), f, ensure_ascii = False, indent=4) .samples-{sample-name : sample-data}
The samples are converted into the .wav format. The sample-data is a .wav file in bytes.
clip : AudioClip
for name, data in clip.samples.items():
with open(name, "wb") as f:
f.write(data).export()- mesh exported as .obj (str)
The mesh is converted into an Wavefront .obj file.
mesh : Mesh
with open(f"{mesh.name}.obj", "wt", newline = "") as f:
# newline = "" is important
f.write(mesh.export())- [] documentation
I'm an active data-miner and noticed that unitypack has problems with new unity assets. The problem in unitypack isn't that easy to fix and the undocumented code is a bit hard to understand. That's why I tried other tools like UABE and AssetStudio. Sadly none of these tools can be used like unitypack. That's why I started this project.