What is the UNITY3D file format?
A .unity3d file is a 3D game data archive that stores data for browser games which required the Unity Web Player plugin to run. This type of file was used for deploying games built with the Unity engine to the web. A single .unity3d holds compiled game code including environment data, assets, objects, textures, animations, lighting, and audio - packaged as a binary serialized container.
Internally, .unity3d files start with the ASCII tag UnityWeb at byte offset 0 (older compressed streamed builds) or UnityFS for newer variants, followed by a version string. This container format later evolved into the Unity AssetBundle (.bundle), which shares the same serialization approach and is still in active use.
The .unity3d format is a proprietary format created by Unity Technologies and is used by the Unity game engine. Unity Web Player - the browser plugin required to open .unity3d files - was deprecated with Unity 5.4 in 2016, after which browser vendors dropped NPAPI plugin support entirely. As a result, .unity3d files cannot be played in any modern browser. Legacy files can still be inspected or extracted using community tools such as AssetStudio.
Security & safety
RISK: MEDIUMA .unity3d is data loaded by the Unity runtime, but it can contain compiled scripts (game code), so a malicious or tampered bundle loaded by a Unity app is not purely inert. The bigger practical risk is the surrounding ecosystem: the Unity Web Player plugin is dead and unpatched, so NEVER reinstall it or run an old NPAPI browser to play these files. Extract assets in a sandboxed tool (AssetStudio) rather than executing unknown bundles, and only obtain games from sources you trust.
Format details
in a nutshellPrograms that open UNITY3D files
Technical details
deep spec| MIME type | application/vnd.unity |
| File signature | ASCII "UnityWeb" at byte offset 0 (compressed streamed build); newer variants begin with "UnityFS" |
| Byte order | Big-endian - Unity's legacy serializer stores multi-byte integers in big-endian order |
| Compression | LZMA by default for Web Player streamed builds; later Unity bundle variants also support LZ4 and uncompressed modes |
| Container structure | Proprietary binary container; not ZIP-based - assets and their dependency graph are stored in a flat serialized layout |
| Asset types | Scenes, meshes, textures, audio clips, shaders, compiled scripts (Mono bytecode), and animation data |
| Script storage | Compiled Mono C# bytecode - source files are not included; scripts are baked into the bundle during the Unity build process |
| Texture compression | Textures embedded in DXT (desktop), ETC (mobile), or other platform-native GPU-compressed formats |
| Delivery model | Designed for HTTP streaming; the file header is parsed first so assets can begin loading before the full download completes |
| Successor format | Unity AssetBundle (.bundle / .assetbundle) - shares the same serialization core and replaced .unity3d after Unity Web Player was discontinued |
| Deprecation | Unity Web Player - the only runtime that can open .unity3d in-browser - was discontinued in Unity 5.4 (2016); no modern browser supports it |
| Developer | Unity Technologies (San Francisco, CA); format is proprietary and undocumented publicly |
| Released | Mid-2000s with the Unity Web Player; Web Player deprecated with Unity 5.4 (2016) |
| Specification | docs.unity3d.com |