About Unity Prefab Inspector

Parse and display Unity .prefab YAML structure in a readable format. Part of the DevTools Surf developer suite. Browse more tools in the Game Dev collection.

Use Cases

• Unity developers debugging prefab serialization issues
• Technical artists tracing component references in complex prefabs
• Version control users resolving merge conflicts in prefab YAML
• Build engineers auditing prefab structure for optimization

Tips

• Search for specific component GUIDs to trace references
• Expand nested prefab hierarchies to find override values
• Compare prefab YAML before and after changes to spot differences

Fun Facts

• Unity switched to YAML-based prefab serialization in Unity 3.5 (2012), replacing binary format — this enabled version control diffing but made prefab files much larger.
• Unity's YAML format uses a custom tag system (e.g., !u!1 for GameObject, !u!4 for Transform) that maps to internal class IDs — there are over 200 documented class IDs.
• Nested prefabs, one of Unity's most requested features, finally shipped in Unity 2018.3 after years of development — previously, prefab-in-prefab workflows required third-party solutions.

FAQ

What's a Unity prefab?

A reusable GameObject template stored as a .prefab YAML file. Drop the file in the tool to see its component structure without opening Unity.

Why inspect prefabs outside Unity?

Code review, merge conflict resolution, scripting automated checks (no missing scripts, consistent layer assignments). Useful in CI.

Does it modify prefabs?

Read-only. For modifications open in Unity — direct YAML editing of prefabs is fragile and often breaks.

What about nested prefabs?

Shown in-tree. References to other prefabs are highlighted; you'll need to inspect those separately.