Retiring Native Unity Files for Kit Downloads
We're dropping native Unity format support for all future KitBash3D Kit releases.
Why we're making this change
We're standardizing our pipeline around our most popular and commonly used DCCs due to low historical demand for native Unity files.
This shift lets us prioritize the platforms that our customers use the most and deliver highly stable builds where our asset architecture performs best.
What happens to your workflow
Future Releases
Upcoming Kits will not offer a native Unity format. For new Kit releases you can use FBX or OBJ formats to drop assets into your Unity scene.
Refer to the Unity Importing Model Files Documentation for detailed conversion steps on bringing standard 3D file formats into your project.
⚠️ Technical Support Limits
Our team cannot assist with engine-specific troubleshooting, custom shader graphs, or format conversions inside Unity.
Manual Pipeline Requirements: Importing raw FBX or OBJ files means you must manually set your material creation modes, extract embedded textures, and reassign maps to standard materials inside your project pipeline.
For hands-on pipeline help, check out the Unity Model Importing Guide or the Unity Model Materials Documentation to map your assets correctly.
Use these native engine tools to keep your build moving forward on schedule.
Legacy Access for Previously Purchased Kits
You retain to native Unity files (HDRP & Built-In) for any Kit that you previously purchased that offered Unity Native files for download and has not been updated.
For context, a Kit update is when we revisit our older Kits to upgrade them with our newest file structures or optimize them for Gameplay Ready performance.
We're monitoring how Unity handles industry asset standards. For tracking legacy setups, head over to our setup guide on How to Open a Kit in Unity with Textures Linked to process your older format files.