Unity's profiler tells you memory went up. It does not tell you that GameManagerCache.pooledEnemies is still holding forty destroyed enemies, which is the one sentence you actually needed.

Snapshots

Capture memory and see it broken down by category — textures, meshes, audio, shaders, materials, managed heap — with the largest consumers named. Take a second snapshot after loading a level and diff it: what appeared, what grew, what never came back. The numbers are the ones Unity reports, labelled correctly: allocated total, managed heap, native memory, and reserved memory shown separately rather than mixed together.

Leak Detective

Scans for the patterns that leak in real projects: static fields holding destroyed Unity objects, event handlers never unsubscribed, coroutines still running on dead objects, and steady growth across snapshots. The report names the declaring type and the field, and traces the reference chain from the leaked object to the root that holds it. You get a line to delete, not a direction to search in.

Texture Gallery

Every texture in memory with its size, format, mip status and read/write flag, sorted by what it costs. Duplicate detection finds the same image imported twice under different names — the single most common source of wasted texture memory in a shipped game.

Recommendations That Carry Numbers

Advice without a number is noise. Check the project against a platform budget — low-end mobile through current consoles — and every recommendation that can be measured comes back with the bytes it frees: how much compression saves on these specific textures, how much capping the size to the platform limit saves, how much disabling Read/Write returns, how far over budget the project actually is. The list sorts by what pays off. Recommendations that cannot be quantified, like avoiding allocations in a hot path, are marked as advice rather than padded with a fake number.

Gc Pressure

Watch the allocation rate, the pressure on the heap, and the predicted time until the next collection while the game runs, sampled continuously. Attribute allocations to a named scope in your own code.

Export

HTML, CSV, JSON or Markdown — for the ticket, the wiki, or the build report.