WHAT UNITY DOES WITHOUT TELLING YOU

Create a prefab variant. Change nothing. Unity has already written eleven property overrides onto its root: the name, three position components, four rotation components and three rotation-hint values. Eight of them are identical to the base and do nothing at all. For a UI prefab with a RectTransform root there are twenty-one.

That happens on every variant, in every project, before you touch anything. Multiply it across your project, then add the overrides you made and forgot, the ones a teammate's change made pointless, and the ones pointing at script fields renamed two sprints ago.

Dead Overrides reads your prefabs and tells you which overrides still mean something.

WHAT IT FINDS

Redundant — the override writes the value the base already has. Removing it changes nothing. Values are compared by type, never as text: a float written as 0.16 reads back from Unity as 0.15999999642372131, and a string comparison would call that a real change.

Stale — the target object or property no longer exists in the base. Usually a renamed or deleted script field. This is the one category that means something is actually broken rather than merely wasteful.

Shadowed — a descendant variant overrides the same property on the same object, so this value never reaches anything. Reported per descendant chain, because an override can be dead through one descendant and live through another.

Prefabs that should have been variants — same hierarchy, same components, differing only in a handful of values. Copy-paste instead of inheritance. This works even in projects that use no variants at all.

Accumulation metrics — overrides per node, chain depth, total along the chain, share redundant. Flags refactor candidates against thresholds you set.

WHY IT DOESN'T DROWN YOU IN NOISE

A report full of things you cannot act on is worse than no report.

Overrides nobody authored — Unity's own bookkeeping and third-party component state — are classified as noise and folded away by default, with a counter. Open the fold and every entry names the rule that classified it, with a button to turn that rule off. Rules are ordered, editable and yours.

Package content is excluded by default, because the first thing a new tool should not do is hand you a page of advice about somebody else's files. Excluded paths and their file counts are always shown — silent filtering is worse than no filtering.

When the tool cannot analyse something, it says so in a separate line instead of guessing.

WHAT IT DOESN'T DO

This version is read-only. There is no auto-fix button, and nothing is ever written to your prefabs. Deleting an override is a decision, and the tool does not make it for you.

A demo folder with prepared prefabs is included, so the first scan shows all four kinds of finding straight away.