Unity Package Extractor and Asset Viewer

Restore useful project-relative asset paths from Unity editor GUID packages. Browse supplied C# source and compatible media, retain each asset.meta relationship, and inspect the GUID-to-path report alongside raw originals.

Drop your .unitypackage file here
Choose file

⚠ Drag-and-drop upload could not load — an ad blocker is most likely blocking it. Please disable your ad blocker and reload the page to upload a file.

Browse metadata, source and assets

Processing runs on our servers. Upload a package to browse its extracted files and readable format report, inspect partial results, download individual files or download the complete result ZIP. Extraction and supplied source viewing are identified separately from bytecode recovery.

unitypackage.json
files/0123456789abcdef0123456789abcdef/asset
project/Assets/Plugins/UniTask/Runtime/UniTask.cs
project/Assets/Plugins/UniTask/Runtime/UniTask.cs.meta

Supported variants and limits

Validated pathname data controls the project view. Unsafe, duplicate, case-colliding and missing mappings are reported while original GUID members remain available. Folder-only assets create directories without file bodies. This does not supply a complete Unity project, missing assets, a Unity editor or reconstructed IL2CPP method bodies.

Shared defaults are five minutes per job, 1 GiB expanded data, 256 MiB per member, 25,000 entries and four nested layers. Metadata reads are bounded to 4 MiB. Each nested compression or container layer shares these limits. Larger or damaged inputs can produce partial results; DECOMPILATION-NOTES.txt and extraction.json explain skipped files and recovery outcomes.

Related inspectors: DEB, RPM, macOS PKG, MCPACK, MCADDON, MCWORLD and MCTEMPLATE, Scratch, App Inventor and Unity packages.

For Unity runtime .assets, .bundle, .assetbundle or .unity3d files, use the Unity runtime asset extractor. For compiled applications, use the Java decompiler or APK decompiler.