Unity
Build Size Guard: Track Changes and Enforce Limits
$39.99
Price history
Recorded standalone sale prices and the latest available store price, in USD. Historical dots use the sale start date and its recorded offer price. Prices can change during a sale; this is not a daily price log. Bundle prices and upcoming offers are excluded. History covers up to the 100 most recent recorded offers.
Lowest recorded standalone price in this history: $39.99. The latest store price is $39.99, matching the lowest recorded price shown here.
View 2 recorded prices
| Sale start / price check | Price | Observation |
|---|---|---|
| $39.99 | Latest store price | |
| $39.99 | Unity First Price 2026-06-20 2026-06-27 |
Sale and bundle history
The 1 most recent recorded offers including this asset. Past offers may no longer be available. Bundle prices cover a package, not this asset alone.
About Build Size Guard: Track Changes and Enforce Limits
- Tools, Systems & Learning > Development Tools & Automation
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 is 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:
Build normally.
Build Size Guard records a snapshot automatically.
Release baseline vs current. Open the tool and Compare: Latest vs previous.
Identify the top culprits, then fix the real cause.
Add budgets to prevent the same regression from returning.
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 is 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:
Build normally.
Build Size Guard records a snapshot automatically.
Release baseline vs current. Open the tool and Compare: Latest vs previous.
Identify the top culprits, then fix the real cause.
Add budgets to prevent the same regression from returning.