Unity rules reference

Every diagnostic PerfLint runs on a Unity project, one page each: what triggers it, what it costs, how to fix it by hand, and what the plugin can fix for you.

Each rule has a stable code (PERF.TEX005, ASSET.DUP001…) — the same one the editor window, the HTML report, and the CLI print. Scanning is free and runs entirely on your machine; nothing about your project is uploaded. Pages are being added rule by rule, so this list is a subset of what a scan reports today.

Performance

Import settings and scene data that cost memory, VRAM, or frame time.

Assets

Build size: duplicated, unreferenced, and badly packed content.

Migration

Deprecated APIs, package incompatibilities, and upgrade blockers.

Project Settings

Player/Editor settings that leave build size or CPU on the table.


Want the whole list applied to your own project instead of read one page at a time? Install the free scanner — it reports every rule above, with the exact files, and no upload. For measured before/after cases, see the blog.