Size Analysis
Monitor mobile builds for size changes before they reach users.
Size Analysis is currently in Early Access. To access, turn on Early Adopter in your settings.
Size Analysis monitors your mobile app size to prevent regressions before they reach users. Upload builds from CI to spot regressions early, understand what's inside each bundle, and keep release artifacts lean.
- Faster downloads reduce install drop-off
- Install size is linked to uninstall rates, particularly for customers with limited storage or slower connections
- Size bloat can have downstream technical impact: longer build times, startup times, code complexity, etc.
Size Analysis breaks down your mobile app so you can see exactly where size is coming from. It surfaces Insights that recommend concrete fixes, such as compressing images or stripping debug info.
Size Analysis also provides actionable insights on how you can reduce your app's size. Insights are tailored to each platform. Dive deeper in:
Compare any two builds to see what changed, review module-level diffs, and confirm that optimizations worked.
Integrate into CI Size Analysis results on pull requests. You can track size on every commit to ensure there are no unnecessary size increases.
Learn how to set it up in the CI integration guide.
You can follow the platform guides to learn how to upload builds for Size Analysis:
Below is the metadata included in your build, regardless of the platform.
We use build metadata to organize builds in the UI and ensure correct comparisons.
| Field | Description |
|---|---|
org* | Sentry organization slug |
project* | Sentry project slug |
build-configuration* | Build configuration describing how the app was built, for example Release or Debug or Release-Bazel |
head-sha | Current commit SHA |
base-sha | Base commit SHA (for comparisons, recommended to use the branch's merge-base) |
head-repo-name | Repository name (org/repo) |
pr-number | Pull request number |
head-ref | Branch or tag name |
base-ref | Base branch name |
* required field
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").