Build Size Guard: Track Changes and Enforce Limits

Stop build size regressions before they ship. Build Size Guard automatically records build size snapshots, compares two builds, shows exactly what changed, and can enforce size limits (budgets) locally and in CI.

✅ What you get

• Automatic build snapshots saved per build target (so you can track history over time).
• Compare any two builds and see the exact delta: total size change + where it came from.
• Top contributors list (what grew the most, what shrank, what is new).
• Grouping views so you can understand changes fast (by folder/path and by category).
• Budgets and enforcement to fail fast when size grows beyond your rules.
• CI friendly outputs so teams can gate regressions in pipelines.

🔍 Find the cause in minutes

When a build grows, the question is never “did it grow?”, it’s “what specifically changed?”

Build Size Guard highlights:

• Largest increases (new or expanded assets)
• Largest decreases (useful for validating optimizations)
• New entries (assets that suddenly started contributing)
• Changed distribution across categories (useful for texture/audio bloat)
• Target-specific differences (Android vs iOS vs Windows can diverge)

💸 Budgets (size limits)

Set budgets that match how real projects work:

• Total build size budget per target
• Optional rules like max allowed regression per snapshot comparison
• Optional category budgets (for example: textures, audio, meshes, shaders, managed code, native/plugins) depending on what Unity can report for your target

When a budget is violated, you can make it loud:

• Editor feedback for local builds
• CI failure for automated checks (non-zero exit style workflow)

🧰 Typical workflow

1. Build normally.
2. Build Size Guard records a snapshot automatically.
3. Release baseline vs currentOpen the tool and Compare:
   Latest vs previous
4. Identify the top culprits, then fix the real cause.
5. Add budgets to prevent the same regression from returning.

🤖 Designed for teams and CI

• Works for solo devs who want quick answers.
• Works for teams who need enforcement and history.
• Generates shareable reports so regressions are easy to review in PRs and build logs.

🧩 Implementation notes

• Editor-only tooling (no runtime footprint).
• Uses Unity’s build reporting data to track size and changes.
• Best results when you keep a stable baseline snapshot for each target and compare against it.

🏠 Homepage

📂 Documentation

💬Support