Static Resources
Static Resources is a Setup page for managing files uploaded to Salesforce that can be referenced in Visualforce pages, Lightning components, and other customizations.
Definition
Static Resources is a Setup page for managing files uploaded to Salesforce that can be referenced in Visualforce pages, Lightning components, and other customizations. Static resources can include JavaScript libraries, CSS stylesheets, images, and ZIP archives containing multiple files, with a maximum size of 5 MB per resource.
In plain English
“Here's a simple way to think about it: Think of Salesforce like a video game. Most people just play the game as it is. But Static Resources is like having access to the game editor - developers can use it to create new levels, add new powers, or change how things work behind the scenes. It takes more skill, but you can make the game do things it couldn't before.”
Worked example
A developer at CloudBridge Solutions uploads a Static Resource containing a ZIP archive of the D3.js charting library, custom CSS styles, and icon images. She references these files in a Lightning Web Component that renders interactive data visualizations on the Account dashboard, without needing to host these assets on an external server.
Why Static Resources is where Visualforce and Lightning components find their assets
A custom Lightning component, a Visualforce page, or a managed package often needs supporting files - JavaScript libraries, CSS stylesheets, images, fonts, ZIP archives of multiple related files. Static Resources is the Setup page where those files get uploaded, with a per-resource cap of 5 MB. Once uploaded, code references them by name (often through merge fields), and the platform serves them as part of the org's content delivery.
The reason this earns admin attention is that Static Resources are part of the org's effective performance budget. Large libraries downloaded on every page load slow user experience; outdated versions create subtle bugs that don't surface until specific browsers tighten security; unused resources accumulate over years. Treat the catalog like a build artifact - version the names, track which components depend on which resources, retire what's unused, and rebuild as the codebase evolves.
How organizations use Static Resources
Bundle their entire brand-asset library (fonts, brand colors, logo SVGs, the master typography stylesheet) as Static Resources referenced from Lightning components. A brand refresh becomes a single Static Resource update; every Lightning page picks up the change without a redeploy.
Use Static Resources to host a JavaScript visualization library (Chart.js) that is referenced from a Lightning component. Hosting it as a Static Resource sidesteps the Salesforce CSP restriction on external script sources, and the version is locked to whatever was uploaded - eliminating the "CDN updated and broke our chart" incident class.
Manage all images embedded in their Knowledge articles as Static Resources rather than direct uploads. The benefit is referential integrity - delete a Static Resource and every Knowledge article referencing it is auditable in one query, instead of orphaned image links scattered across articles.
Trust & references
Straight from the source - Salesforce's reference material on Static Resources.
- Static ResourcesSalesforce Developers
🧠 Test your knowledge
Q1. What is required before deploying Static Resources-related code to production?
Q2. Where would a developer typically work with Static Resources?
Q3. What is a Governor Limit in the context of Static Resources?
Discussion
Loading discussion…