Salesforce enforces a 250 MB per-org limit on static resources. Static resources in Salesforce managed packages — including JavaScript libraries, CSS files, images, fonts, and ZIP archives bundled with the package — count toward this org-wide static resource storage limit.
If installing a managed package would cause the org's total static resource storage to exceed the 250 MB limit, the installation will fail. This behavior affects both the initial installation of a managed package and the upgrade of an existing managed package to a newer version that includes additional or larger static resources.
Why the Package Installation Fails
When you attempt to install a managed package, Salesforce validates that the resulting total static resource storage across all resources in your org will not exceed the 250 MB per-org limit. If the package's bundled static resources would push the total over the limit, the installation is blocked to protect org data integrity. The error typically indicates that the package cannot be installed due to the static resource limit.
Steps Before Contacting Support
Before logging a case with Salesforce Support, complete the following steps to reduce static resource usage:
1. Navigate to Setup and search for "Static Resources" to view all currently stored static resources in your org.
2. Review the list and identify any static resources that are no longer in use (for example, files associated with uninstalled packages, old versions of libraries, or deprecated content).
3. Delete unused or obsolete static resource files to free up storage space.
4. After deleting unused resources, attempt to install the managed package again.
5. If storage cannot be reduced sufficiently, contact Salesforce Support to request a review of your static resource limit.
000383061

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.