# Use your Unity Asset Store assets in Godot

Yes. Unity's own support article, updated 2 July 2025, says Asset Store assets can be used with other engines as long as you follow the Asset Store EULA: ship them inside your game where players cannot extract them, and check each package for Restricted Asset terms or a publisher licence of its own. Models, textures and sounds import into Godot as files, and a whole .unitypackage comes in through the open-source Unidot Importer.

Source: https://flockbay.com/unity-asset-store-to-godot/ · Updated 2026-11-08

## Unity says yes, in writing, since July 2025

For years the honest answer to "can I use my Asset Store purchases in Godot?" was a forum thread. That changed when Unity published "Can I use assets from the Asset Store with other engines?" in its support help center, updated 2 July 2025. Its resolution reads: Unity Asset Store assets are not restricted to Unity projects.

The condition is the Asset Store End User License Agreement, section 2. What it rules out: redistributing the assets on their own or in a form players can extract, sharing one purchase among several people, monetizing an asset inside user-generated content without its creator's permission, and a project whose main purpose is to give others access to the asset. What it allows is the ordinary case: the asset shipped inside your game.

Summaries written before that article often say Asset Store assets usually cannot move to another engine. They predate it.

Sources, read 8 November 2026: [Unity support: Can I use assets from the Asset Store with other engines? (updated 2 July 2025)](https://support.unity.com/hc/en-us/articles/34387186019988-Can-I-use-assets-from-the-Asset-Store-with-other-engines), [Asset Store EULA FAQ](https://assetstore.unity.com/browse/eula-faq).

## Restricted Assets, open-source parts and Unity's own packages are the exceptions

Some packages carry Restricted Asset Terms, and some publishers attach a licence of their own; the article sends you to the package's documentation for those. Open-source components inside a package keep their own licence, which wins where it conflicts with the EULA.

Unity's own packages are a different case. TextMeshPro, the Universal and High Definition Render Pipelines, Cinemachine and the Input System come under the Unity Companion License, which allows their use only with Unity. Rebuild what you used from them with Godot nodes rather than copying them across.

## A .unitypackage is an archive you can open

The file Unity downloads to its Asset Store cache, the Asset Store-5.x folder under Unity in your user folder, is a gzipped tar. Inside, every asset sits in a folder named for its GUID with three files: asset, the file itself; asset.meta, Unity's import settings and GUID; and pathname, where it belongs in an Assets folder. Any archive tool unpacks it, which is how importers outside Unity read it.

## Unidot Importer brings a package into Godot 4

Unidot Importer is an open-source Godot 4 add-on, MIT-licensed and maintained by V-Sekai, that reads a .unitypackage or a Unity project folder and writes Godot files: prefabs become scenes, materials become StandardMaterial3D, FBX models come in through Godot's own importer with their animations, and the prefab references between them hold. Scripts are not converted: a MonoBehaviour arrives as a placeholder holding its Inspector values, for you to port.

That split is the honest shape of any move. Art and layout carry across; logic is rewritten, and the C# to GDScript map covers that half. Flockbay's Import from Unity runs Unidot inside the Godot it ships, so Import Unity package… in the chat brings a .unitypackage into your game, and the AI ports its scripts.

Source: [Unidot Importer on GitHub (MIT)](https://github.com/V-Sekai/unidot_importer).

## Models and sounds move as files; shaders and scripts are rebuilt

FBX and glTF models import into Godot 4 directly, rigs and animations included. PNG, TGA and PSD textures and WAV, OGG and MP3 audio copy across. A standard PBR material keeps its albedo, normal, metallic and roughness maps as a StandardMaterial3D.

Custom shaders written in ShaderLab, HLSL or Shader Graph are rewritten in Godot's shading language, keeping their properties as uniforms. A humanoid animation pack built on Mecanim retargets in Godot through a BoneMap and a SkeletonProfileHumanoid, which takes some setup per rig.

## Questions

### Can I use Unity Asset Store assets in Godot?

Yes, under the Asset Store EULA, as Unity's support article updated 2 July 2025 says: ship them inside your game so players cannot extract them, and check each package for Restricted Asset terms or its publisher's own licence.

### Can I sell a Godot game that uses Asset Store assets?

Yes, with the assets embedded in the game and not redistributed on their own, as the EULA requires.

### How do I import a .unitypackage into Godot?

With the open-source Unidot Importer add-on, which converts the package's prefabs, materials and models into Godot files, or with Import Unity package… in Flockbay's chat, which runs Unidot for you and adds the package's scripts to the port list. Models, textures and audio can also be copied in as plain files.

### Do Unity's own packages, like TextMeshPro or URP, move to Godot?

No. They come under the Unity Companion License, which allows their use only with Unity. Rebuild what you used from them with Godot nodes.

Download Flockbay free: Bring your game to Godot 4 with Flockbay's AI on Windows, macOS or Linux. https://flockbay.com/

Related: [Unity to Godot](/unity-to-godot/), [Unity C# to GDScript: the API map](/unity-csharp-to-gdscript/), [Flockbay vs Unity](/flockbay-vs-unity/)
