A single high-resolution photograph uploaded to a SharePoint team site can run to 8 MB or more. Multiply that across five years of team site activity, a dozen departments each embedding images in every page they publish, and a migration that imported an old intranet wholesale, and you have a storage problem that has nothing to do with document versions.
Version history gets most of the attention in SharePoint storage conversations, and rightly so. But images are a different kind of drain - less visible, growing silently, and easy to miss in a storage audit.
Where Do SharePoint Images Accumulate?
Images in SharePoint Online are not stored in some separate media bucket. They live in ordinary document libraries alongside your Word files and spreadsheets, counted against the same site collection quota. The main accumulation points:
Site Assets library on modern sites
Every image embedded in a modern SharePoint page - a banner, a team photo, a logo dropped into a news post - is stored in the site's Site Assets library. On an active intranet site where the communications team publishes weekly, this library grows steadily. The images are rarely deleted when the page they live on is retired or replaced.
Style Library on classic and publishing sites
Older SharePoint environments, particularly those built as intranets or portals using classic SharePoint publishing features, accumulated images in the Style Library. These sites often went through multiple redesigns, each adding a new set of imagery while the old images stayed in place.
Document libraries used as media stores
Some teams use SharePoint document libraries as a general repository for photos, marketing assets, or product images. Without a version limit or storage review process, a library that started with 200 product shots grows to several thousand files over three or four years.
Migrated intranet content
Migrations from legacy intranets - SharePoint on-premises, Confluence, or older CMS platforms - frequently import every image asset associated with historical pages. A migration that brings across five years of intranet content can introduce gigabytes of image storage overnight, much of it redundant.
What Does Image Storage Actually Cost You?
Microsoft 365 storage is not infinite. Once a tenant's pooled storage runs low, SharePoint begins enforcing per-site limits more strictly, and new site creation can be blocked until headroom is freed.
The practical consequence for most organisations is not a hard cutoff but a gradual tightening. Admins start getting alerts about site collections approaching their quotas. The SharePoint admin centre shows overall tenant storage creeping toward capacity. And when someone asks what is using all the space, the first instinct is to look at document libraries full of large PowerPoint files - not at Site Assets libraries quietly holding three years of embedded page images.
The version history angle is well understood. Fifty versions of a 2 MB report is a calculable, findable problem. Images are more diffuse. A Site Assets library with 1,200 images averaging 3 MB each is 3.6 GB of storage that shows up in no obvious report unless you know to look for it.
How to Find Your Image Storage Footprint
The SharePoint admin centre site storage report shows total storage per site collection. It does not break down by file type. To surface image-heavy libraries specifically, you have a few options:
- Browse Site Assets libraries manually. On any site, go to Site contents and open Site Assets. Sort by size. For a single site this takes a minute; across a 200-site tenant it is not a viable approach.
- Use ShareMaster's Report Master. Report Master exports a storage breakdown that includes file-level data. Filter the export by file type (jpg, png, gif, webp, svg) to identify the libraries and sites carrying the most image weight. This gives you a prioritised list for cleanup in under an hour across the whole tenant.
- PnP PowerShell. The
Get-PnPFolderItemcmdlet can iterate through libraries and sum file sizes by extension. It works but requires writing and maintaining a script for each variation of the report you need.
How to Reduce SharePoint Image Storage
Once you know which sites and libraries hold the most image weight, you have three levers:
Delete images that are no longer referenced
The safest approach: identify images in Site Assets that have no corresponding page or are associated with archived or deleted pages. These can often be removed entirely. The catch is that SharePoint does not have a built-in "find unreferenced assets" report, so this requires either a manual audit or a scripted check.
Compress images in place with Image Reducer
Space Master's Image Reducer tool compresses images stored in SharePoint document libraries and the Site Assets library without changing the file names or breaking page references. For libraries where the images are still in active use - live intranet pages, team site banners - this is the practical path. You reduce the storage footprint without touching page layout or content.
Set library-level storage limits and review cycles
For libraries that actively accumulate images (a marketing asset library, a news site's Site Assets), a periodic review prevents the backlog from rebuilding. A quarterly export from Report Master, filtered by image file type and reviewed by the site owner, keeps things in check without much overhead - even across large tenants.
A Note on Version History for Images
Images in SharePoint libraries can accumulate versions just like documents. An image that has been replaced three times in a Site Assets library has three full-resolution copies sitting in version history, not just the current one. Version trimming applies to images as well as documents. If you are running a storage reduction project, applying version limits to image-heavy libraries alongside compressing the current versions compounds the benefit.
The guide on reducing SharePoint storage quickly covers version trimming, empty folder removal, and bulk deletion as part of a broader storage cleanup. Image reduction fits naturally into that same project plan.
Frequently Asked Questions
Does SharePoint compress images automatically?
SharePoint Online does not compress or resize images uploaded to document libraries or the Site Assets library. The original file is stored at full resolution. Modern SharePoint pages serve responsive image renditions for display purposes, but the full-resolution file remains in storage at its original size.
Where do images accumulate most in SharePoint?
The main accumulation points are the Site Assets library on modern sites, the Style Library on classic publishing sites, document libraries used for photo or media storage, and content imported from legacy intranet migrations. All of these are standard document libraries counted against the same site storage quota as your files.
How do I find which SharePoint sites are using the most image storage?
The SharePoint admin centre site storage report shows total storage per site but does not break it down by file type. ShareMaster's Report Master exports a storage breakdown with file-level data, making it straightforward to filter by image file types and identify the libraries with the largest image footprints across the tenant.
Try ShareMaster free for 14 days