Thirty-two gigabytes of current project images had quietly become 940 GB of SharePoint Online storage at Focal Arc Creative, a 120-person digital marketing agency in Brisbane. The active files had not changed much. Version history had.
This is the story of how Daniel, the agency's IT manager, found the problem, measured it, and cleaned it up in a single weekend without touching a production file. It illustrates a pattern that appears repeatedly in creative and media businesses, where image libraries grow fast and version history runs unchecked for years.
A growing storage problem in a creative agency
The agency had five active SharePoint Online sites. Three held client project work, one was an internal brand asset library, and one was a shared marketing site. All five had document libraries with versioning enabled at the default setting: up to 500 major versions per file.
For most organisations, the default 500-version limit is generous but not catastrophic. For a creative agency uploading and revising image files daily, it is a slow-burning quota problem. Designers upload a 25 MB layered TIFF, export a revised JPEG, re-export when the client requests a colour correction, and upload a final approved version. Each upload creates a full copy in version history. Unlike Office documents, which use delta compression between versions, image files are stored as complete copies every time.
Over three years, the brand asset library alone had accumulated over 800 versions across its top 200 files. The library's current content was 18 GB. Its version history was 520 GB. Nobody had noticed because SharePoint's storage reporting in the admin centre shows total site storage, not the breakdown between current files and their versions. The site's quota alert was set at 90% of the allocated limit. By the time it triggered, the agency was already weeks away from a storage-related incident.
Daniel discovered the problem during a quarterly Microsoft 365 admin review when he noticed that three of the five sites were consuming storage out of proportion to their stated content volumes.
What the audit uncovered: versioning as the main culprit in image-heavy libraries
The first step was getting a breakdown of storage by content type, not by site. The Microsoft 365 admin centre does not provide this natively; it shows total site storage but does not split current files from version history. Daniel used ShareMaster's Report Master to export a storage utilisation report per library, which included version counts and the total storage consumed by versions per file.
The report confirmed the pattern across all five sites:
| Site | Current file storage | Version history storage | Version-to-current ratio |
|---|---|---|---|
| Brand Asset Library | 18 GB | 520 GB | 29:1 |
| Client Projects (Site A) | 6 GB | 180 GB | 30:1 |
| Client Projects (Site B) | 4 GB | 120 GB | 30:1 |
| Client Projects (Site C) | 2 GB | 60 GB | 30:1 |
| Marketing Site | 2 GB | 60 GB | 30:1 |
| Total | 32 GB | 940 GB | 29:1 |
The common factor across all five sites was image files: JPEGs, PNGs, and TIFFs stored with the same versioning settings as Word documents and Excel files. The business value of keeping 300 versions of a client logo revision was approximately zero. The storage cost was significant and growing each month.
The report also surfaced a secondary issue: several of the original source files were uncompressed or lightly compressed images at resolutions far beyond what web delivery or print required. A 45 MB uncompressed TIFF uploaded for a web banner project had been revised and re-uploaded 38 times. The current version alone was oversized.
The cleanup: two tools, one weekend
Daniel ran the cleanup over a single weekend using two features in ShareMaster's Space Master. The first was the Version Trimmer, configured to keep the last ten versions per file and delete anything older. For image files, he set a more aggressive policy: keep the last three versions. The logic was straightforward. Client work that required going back more than three image iterations had never arisen in his time at the agency, and if it did, the client would need to supply the original brief file rather than a SharePoint version anyway.
The Version Trimmer ran across all five sites simultaneously. Daniel set it to preview mode first, which showed the volume of versions marked for deletion before committing. The preview confirmed that 96% of all stored versions would be removed under the configured policy. He reviewed a sample of the files marked for trimming, satisfied himself that the policy was correct, and ran the trim.
The second tool was the Image Reducer, which recompresses image files to reduce their current-version file size without deleting the file. For the library's PNG and JPEG files that were serving as delivery assets (web banners, social images, presentation graphics), the original upload resolution was often three to five times larger than the delivery use case required. Image Reducer identified files over a configurable size threshold and applied lossy compression with a quality setting Daniel chose after reviewing a test batch.
The combination of version trimming and image reduction addressed both layers of the problem: the historical accumulation and the oversized current files.
See Space Master storage toolsResults after six weeks
Total storage across the five sites dropped from 972 GB to 89 GB - a 91% reduction. The version trim did most of the work, removing 840 GB of historical image versions. Recompressing approximately 1,400 current files with the Image Reducer added a further 43 GB recovered, completing the cleanup over two days.
The business impact was concrete. The agency had been six weeks away from purchasing additional Microsoft 365 storage. That purchase was no longer necessary for the current year. The reclaimed quota was sufficient to support the agency's projected growth for the next eighteen months without any additional licensing cost.
The weekend cleanup also produced a secondary benefit Daniel had not anticipated: the SharePoint sites became noticeably faster for users browsing and previewing files. Fewer versions in the version history panel meant the interface loaded faster when users opened the version history for a file. Designers reported that the document library pages felt more responsive, likely because the underlying list data was smaller.
What other admins with image-heavy libraries can take from this
The pattern at Focal Arc Creative is not unique to creative agencies. Any Microsoft 365 organisation that uses SharePoint Online to store images, whether marketing assets, product photos, property images, or scanned documents, is likely accumulating version history at a rate far higher than the rest of its document libraries. The storage cost is hidden in the version history layer, which is not visible in the standard admin centre storage view.
Three actions make the biggest difference for admins in this situation:
- Run a storage audit by library, not by site. Total site storage figures mask where the problem is concentrated. A library-level report showing version storage separately from current-file storage is the starting point. The guide to finding large files in SharePoint Online covers how to get this breakdown.
- Set a version policy appropriate to the file type, not a single policy for everything. Image libraries rarely need more than three to five versions. Document libraries used for drafting and approval workflows may need ten to twenty. Applying the default 500-version limit to both is the configuration gap that produces this problem.
- Run version cleanup on a regular cadence. A one-time cleanup recovers the historical accumulation, but without repeating the process periodically, the storage will grow back to its previous level within a few years. Adding a recurring admin task to re-run the trim at regular intervals prevents the problem from returning.
For organisations preparing for a Microsoft 365 Copilot rollout, storage hygiene in image libraries is also a governance consideration. Copilot indexes SharePoint content; a library with hundreds of nearly identical image versions adds noise to the index without adding retrieval value.
The tools and the approach that worked for Focal Arc Creative are available in ShareMaster's Space Master. The version and image cleanup runs entirely within SharePoint Online without requiring PowerShell scripting or custom code.