How to open a .unitypackage
- 1
Drop the .unitypackage
Drag the file onto the box or tap to choose it. Asset Store downloads, Booth and VRChat avatar packages and itch.io kits all work. No file? Try the sample crate kit.
- 2
Browse the folders
The files appear under their real Unity paths, such as Assets/Characters/Textures, not as the GUID folders stored in the package. Open and close folders, or type in the filter box to find a file.
- 3
Preview a file
Tap a file to see it: PNG, JPG, TGA and DDS textures, FBX, OBJ and GLB models in 3D, audio with a player, and C# scripts, shaders, materials and prefabs as text.
- 4
Choose what to keep
Filter by name or by type (only textures, only models) to pick part of the package. Tick Include .meta files if you will copy the files into a Unity project.
- 5
Download
Save the single file you are looking at, the filtered files, or all of them as one ZIP with the folder tree kept.
Private by design. The package is unpacked by JavaScript in your browser. It is never uploaded, so paid assets and avatar files you bought stay on your device.
What is inside a .unitypackage
.unitypackagegzip-compressed tar- A Unity package is a tar archive packed with gzip, the same as a .tar.gz. Renaming it does not help on its own, because the files inside are not stored under their real names.
GUID foldersOne folder per asset- Every asset sits in a folder named after its 32-character GUID. Inside are asset (the file itself), asset.meta (Unity's import settings and the GUID) and pathname (one line with the real path, such as Assets/Models/Crate.fbx).
preview.pngThumbnail- Many assets also carry a small preview.png, the thumbnail Unity showed in the Project window. The extractor shows it next to the file.
.meta filesGUID and import settings- Materials, prefabs and scenes point to textures and meshes by GUID, not by file name. Keeping the .meta files is what lets those links survive when the folder is copied into another Unity project.
UnityFS bundlesA different format- AssetBundles, .assets files and built game data use the UnityFS format. They hold imported, engine-ready data rather than source files, and this tool does not open them.
Why open a package without Unity
Unity is a large install, and importing a package into a project only to copy out one texture or model is slow. Many people who download a .unitypackage do not use Unity at all: Blender users who bought a character on Booth, VRChat creators checking what an avatar package holds before importing it, artists who want the source textures, and people on a Mac or Chromebook without the editor.
The extractor gives you the files exactly as the author made them, under the same folders. FBX and OBJ models open in Blender, PNG and TGA textures open in any image editor, and scripts are plain C# text. Nothing is converted or re-saved, so the files you download are byte for byte the ones in the package.
Keeping .meta files or leaving them out
Leave .meta files off when you only want the models and textures for Blender, Substance or another engine. You get a clean folder tree with no Unity files in it.
Turn them on when the files are going into a Unity project by hand, for example to add part of a package without the import dialog. Each file then keeps its GUID, so materials still find their textures and prefabs still find their meshes. The ZIP also keeps the .meta of each parent folder, which Unity expects.
Large packages and odd names
Packages are read as a stream, so a 500 MB avatar or environment pack unpacks without loading the compressed file into memory twice. The progress bar shows how far it has got. Very large packages still need free memory for the unpacked files, so a phone may stop well before a desktop does.
Paths are cleaned before anything is saved: characters Windows does not allow are replaced, and any path that tries to climb out of the folder (a zip-slip trick) is flattened. If two files end up with the same path, the second gets a (2) suffix instead of overwriting the first, and a note tells you.
What this unitypackage extractor does
Real folder tree
Files are shown under their Assets/... paths, rebuilt from each GUID's pathname entry.
Previews
Textures (PNG, JPG, TGA, DDS), FBX, OBJ and GLB models in 3D, audio, and text for scripts, shaders and materials.
Filter and pick
Search by name or folder and filter by type, then download only the matches.
ZIP with or without .meta
Download everything as one ZIP that keeps the folders, with Unity .meta files if you want them.
Big packages
Streams packages up to 1 GB with a progress bar, and handles long and non-English file names.
Private by design
Runs in your browser. Packages are never uploaded and no account is needed.
Limits, honestly
- UnityFS files (AssetBundles, .assets, .bundle, sharedassets) are a different format and are not opened here.
- PSD, EXR and HDR textures and Blender .blend files are listed and downloaded but not previewed.
- Model previews use the textures found in the package by file name; a material set up only in Unity may show grey.
- Packages over 1 GB are not opened, and phones may run out of memory well before that.
- Files are extracted as they are; nothing is converted, imported or upgraded to a newer Unity version.