Reviewed against the current product on October 31, 2026 · Published by Unity Asset Exporter.
Blender can't open a .unitypackage directly. Importing only its raw FBX can lose Unity's separate
material assignments. Export supported content as GLB first, then import that result into Blender.
How to import a Unitypackage into Blender
- Drop the
.unitypackageon the box above and select a supported model, prefab or scene. - Inspect its materials in the preview, then click Download GLB for a single file.
- In Blender, choose
File → Import → glTF 2.0 (.glb/.gltf)and select the exported file. - Switch viewport shading to Material Preview and inspect the materials, scale and orientation.
For a bulk GLB ZIP, extract the entire archive first and keep _shared_textures in its original
relative location. Moving just a model out of that folder structure can break its texture references.
Compare single and bulk exports.
Use Try with a sample package above to inspect the browser workflow before opening your own package. It demonstrates local preview and export, not a guarantee that every asset or Blender version imports identically.
The manual way (the painful one)
If you extract the package by hand and import the FBX into Blender, here's what you're signing up for:
- Extract the archive and hunt through GUID folders for the right FBX and its textures.
File → Import → FBX— inspect which materials and images the original FBX actually contains.- Open the Shader Editor, add Image Texture nodes, and load each map by hand.
- Wire base color, normal (through a Normal Map node), metallic/roughness and so on into the Principled BSDF — for every material, on every mesh.
Unity can store texture assignments in .mat files and GUID references outside the FBX.
Blender does not reconstruct those Unity-specific links just by importing the FBX, so missing assignments need manual setup.
Unity assets to Blender: what this route actually converts
This route is for supported 3D assets stored in a .unitypackage: models, reconstructed prefabs or
scenes, materials and textures. It is not a whole Unity-project converter and does not translate scripts,
gameplay logic, custom shaders or editor settings into Blender. Blender's documented glTF 2.0 importer opens
the exported GLB; see the official Blender glTF guide.
What maps carry over
glTF's material model maps cleanly onto Blender's Principled BSDF, so these come through connected:
- Base color (albedo), including alpha where present.
- Normal map, routed through a Normal Map node.
- Metallic and roughness (glTF packs these, and the importer splits them for you).
- Emission color and map.
- Ambient occlusion, where the material provides it.
Skinned characters keep their skeleton and import in the saved static pose. Animation preview and transfer to GLB are not available; original animation FBX files remain available as separate downloads.
Missing textures or unexpected results in Blender?
- Grey in Blender, textured here: check Material Preview and, for a bulk ZIP, restore the full folder structure including
_shared_textures. - Already wrong in this preview: check warnings and whether the package contains the referenced textures. Custom shaders and unsupported texture variants do not have a guaranteed PBR equivalent.
- Wrong size or orientation: inspect the imported object's transforms and compare with the browser preview before adjusting scale or axes.
- Character does not animate: GLB exports use the saved static pose. Download the original animation/source FBX if you need its authored clips; Unity Animator behavior is not converted.
For images without a 3D conversion, extract textures from the Unitypackage. If the exported result still looks wrong, use Help & feedback in the main converter and describe whether the problem started in the preview or after import. Only share screenshots and content you have permission to share.
Honest limits
Source models must be FBX (7.0+). Textures in PNG, JPG, TGA, WebP, BMP and GIF plus common PSD, TIF/TIFF, DDS, HDR and EXR variants are decoded and embedded. Unity-specific shader effects (custom HLSL, shader graphs) don't translate; you get standard PBR, which is what Blender expects anyway.