Reviewed against the current product on October 31, 2026 · Published by Unity Asset Exporter.
You were sent a .unitypackage and just want to look inside — but the only "official" way is to
install Unity, a 5+ GB editor plus a hub, an account and a project just to peek at a file. You don't need any
of that.
How to open and extract a Unitypackage file without Unity
- Use Choose file above, or drop the actual
.unitypackage. For ZIP, RAR or 7z downloads, extract the outer archive on your device first. - Wait for local unpacking, then browse Files in the restored Unity folder structure.
- Download a source file from the tree, or choose Raw package files (FBX + PNG) for the original contents as a ZIP. Other original file types are included where present.
- If you want portable 3D content instead of source files, select a supported model, prefab or scene and choose Download GLB.
Raw extraction does not convert Unity materials or recreate the scene in another editor. A single exported GLB embeds supported textures; a bulk GLB ZIP uses a shared texture folder that must stay beside its models. See which download to use, or extract an original FBX without converting it.
What about .unitypackage.gz files?
A Unitypackage already uses gzip compression. An extra .gz suffix may just be a filename,
but the contents still need to be a valid Unity package archive. Renaming a ZIP, AssetBundle or an arbitrary
gzip file to .unitypackage does not make it compatible. If a downloader added another compression
layer, unpack that outer layer on your device and choose the original package.
A normal archive tool can expose GUID-named folders rather than useful filenames. This viewer reads the package's
pathname entries to restore the original Unity paths. AssetBundles and UnityFS containers are not supported.
What a .unitypackage actually is
Despite the custom extension, a .unitypackage is nothing exotic: it's a gzip-compressed
tar archive. Rename it to .tar.gz and a normal archiver will open it. Inside you'll find
one folder per asset, each named after the asset's GUID (a 32-character hex id) rather than a
filename. A typical GUID folder holds:
asset— the actual file bytes (the FBX, PNG, material, etc.).asset.meta— Unity's YAML metadata, including that GUID and import settings.pathname— the original project path likeAssets/Models/Car.fbx.
That GUID layout is why loose extraction is awkward — the real names and the links between models, materials and textures live in metadata, not in the folder structure.
Your options
- Install Unity. Correct, but heavy: gigabytes of download and a full project setup just to view assets.
- CLI / script extractors. Command-line scripts reconstruct the original paths on disk. Fast, but install-required, and they output loose files with textures still unlinked.
- This browser tool. Drop the package, browse the file tree, preview models in 3D, download individual files or a ZIP — and optionally export models as textured GLB. No install.
Why browser-based wins for a quick look
For "what's in here and does the model look right?", nothing beats a page that unpacks the archive in memory and shows you the tree plus a live 3D preview in seconds. There's nothing to install, it works on any OS, and because gzip/tar parsing and rendering happen client-side, no package upload is needed. Large-package success depends on the device's available memory and the archive safety limits.
Privacy: files never leave your device
This matters for paid Asset Store content and client work. The package is read with the browser's own
FileReader and processed entirely in JavaScript on your machine. Nothing is uploaded
— there's no server to send it to. Close the tab and it's gone.
Honest limits
Model support is FBX (7.0+) today. PNG, JPG, TGA, WebP, BMP and GIF plus common PSD, TIF/TIFF, DDS, HDR and EXR variants can be previewed in-browser; every original file remains available for raw extraction too.