Addressly — Addressables Update Guard & Auditor

If you ship content updates with Addressables without re-releasing the whole app, your catalog can quietly drift between versions. A key gets removed or renamed, an asset stops being Addressable, a type changes — and the update breaks for everyone still on the previous version. It fails late, in production, and it's painful to trace.

Addressly turns each build into a versioned snapshot of your Addressables catalog, then compares any two versions and warns you — before you ship — about anything that would break live clients. Along the way it audits the current build for duplicate assets, implicit dependencies, and size, and tells you how much of your next update is genuinely new content versus bundles that were rebuilt for no reason.

How it works: open Window → Addressly, build your Addressables content as usual, and click Capture — Addressly reads the Build Layout report from that build (it never builds or changes anything). Save a snapshot for each release; before the next update, compare them on the Diff tab. You get a clear, color-coded report of breaking changes, the full catalog diff, and an update-impact summary — how many MB players will re-download, and how much of that is wasted churn.

Works with any project, any genre. Addressly is a developer tool, not content — there are no assets to customize and it isn't tied to a genre. It works with any Unity project that uses Addressables, and is especially valuable for live-ops and mobile titles that push frequent content updates. Analysis is strictly editor-only and read-only: Addressly never modifies your project or your assets.