Old file versions are quietly eating your SharePoint storage.

Almost always version history. Every save keeps the previous version, and SharePoint's default keeps up to 500 versions per file — so a single large PowerPoint on version 735, or thousands of everyday documents, can quietly add hundreds of GB or several TB against your quota. TrimVersions365 measures exactly how much of your storage is old versions, per library, for free.

The current version is never in scope. TrimVersions365 only ever removes old file versions, never a document, folder, list item, or the live version — the compiled package has no code path to delete a current file, and the verifier in your download proves it. Every trim starts with a mandatory what-if preview you approve, and you can send trimmed versions to the recycle bin (reversible) instead of deleting them outright.

Yes — that's the entire free tier. Choose a policy (for example "keep the last 10 versions" or "nothing older than 2 years") and it shows the exact GB you would reclaim per library, with a CSV export. No key, no payment, nothing deleted. If the number is small, the honest answer is: don't buy Pro.

Trim the old versions you're paying to store. Microsoft's Extra File Storage add-on runs about €0.20 per GB per month — recurring forever — while much of that space is just historical versions nobody needs. TrimVersions365 reclaims it with a one-time purchase, so a tenant carrying a terabyte of version bloat can avoid roughly €2,000–€3,000 a year in add-on cost.

Because changing the version-limit setting only affects future saves — it never retro-deletes the versions your libraries already hold. That surprises a lot of admins. To actually reclaim existing storage you have to trim the backlog, which is exactly what TrimVersions365 does: it measures and removes the old versions already sitting in each library, safely and with a preview first.

No — and you don't have to take our word for it. The compiled package contains exactly one destructive endpoint type: SharePoint's file-version delete. There is no code path that deletes files, folders, list items, libraries or current versions, and the verifier script in your download (verify-compiled-package.js) scans the exact .sppkg you install and fails if that ever changes. The build pipeline runs the same check on every release.

That's your choice, made once per trim job. Every run offers a toggle: "Recycle deleted versions (recommended, reversible)" — trimmed versions go to the site recycle bin, the same place a version goes when you delete it by hand in SharePoint's version history; they can be restored from there until the bin is purged, and storage is fully released once they leave the bin — or "Delete permanently (frees storage immediately)" — trimmed versions are removed permanently the moment the job runs, the same behavior as Microsoft's own admin-side version trim jobs, and storage is reclaimed instantly. The toggle defaults to Recycle, because recoverable is the safer starting point. Either way, the mandatory what-if preview shows exactly what will be deleted before anything runs, and current versions are never in scope. Want an extra safety net on top of recycling? Trim conservatively first (for example "older than 730 days"), confirm, then tighten the policy.

It requests zero API permissions: no Microsoft Graph scopes, no Entra app registration, nothing on the admin's API-access approval page. It runs in the browser as the signed-in user; whoever presses Trim needs the delete rights they'd need to delete a version by hand (typically Edit/Contribute on the library). Exactly one network request ever leaves your tenant: the Pro license check to license.trimversions365.com, carrying the license key and your tenant hostname — nothing else. No file names, no contents, no counts, no telemetry. On the free tier, no request leaves the tenant at all.

Big jobs take hours; that's physics on a throttled API, and the engine is built for it. It enumerates pages, deletes version by version at an adaptive pace, and saves progress in a hidden list in your site after every file. Close the laptop, lose Wi-Fi, get redeployed by IT — reopen the page and the job offers to resume exactly where it stopped. Files that are checked out or locked when their turn comes are skipped gracefully and listed in the completion report with the reason, so you can re-run for just the stragglers later.

The engine follows Microsoft's published throttling guidance: when SharePoint answers 429 or 503 it reads the Retry-After header, waits at least that long, retries with exponential backoff and jitter, and reduces how many requests it keeps in flight until the service is comfortable. Throttling protects your tenant's other users — so the engine treats a throttle signal as an instruction, not an obstacle. Practical effect: a trim job runs politely in the background and simply takes longer on a busy tenant. Run big jobs in the evening if you want them faster.

One reason: resumability. Trim-job progress is stored in a hidden SharePoint list ("TrimVersions365Jobs") inside the site being trimmed — your data stays in your tenant, and a job can resume after the tab closes. Creating that list needs the "manage lists" right, which site owners have. If the signed-in user can't create lists, the tool falls back automatically: progress is kept in the browser's local storage instead, which resumes on the same machine and browser but not from a different one. Nothing errors; you just see a note about the weaker resume guarantee.

Partly — going forward. Microsoft's "Automatic" version-history setting (and the newer count/expiration limits) shapes how many versions new activity keeps, and Microsoft's own example shows about 96% version-storage reduction over six months. But changing limits does not trim the backlog your libraries already hold, and Microsoft's backlog tool is a PowerShell-only, admin-run batch job that deletes permanently, and its date-based expiration mode can't touch versions younger than 30 days or keep anything created before January 2023. TrimVersions365 handles the backlog with a UI, per-library scope, exclusions and a mandatory preview — and it coexists fine with Automatic limits: anything Microsoft has already scheduled for expiry is simply no longer there to trim. Versions under a retention policy or legal hold are protected by SharePoint itself; the tool skips them and says so in the report. Microsoft's own pages: learn.microsoft.com/sharepoint/set-default-org-version-limits (version limits) and learn.microsoft.com/sharepoint/trim-versions (the backlog trim tool).

Where SharePoint exposes real per-version sizes, the analysis sums them — that's a measurement, not an estimate. Where it doesn't, the tool shows a clearly-labeled upper-bound estimate (current file size × number of historical versions) and says so in the column header. You can cross-check any library against SharePoint's own Storage Metrics page (Site settings → Storage Metrics); the numbers should bracket what you reclaim. Microsoft documents the version-storage math at learn.microsoft.com/sharepoint/plan-version-storage; the exact price of the "Office 365 Extra File Storage" add-on is shown at purchase time in the Microsoft 365 admin center (learn.microsoft.com/microsoft-365/commerce/add-storage-space).

Free: the complete scan and what-if — every library, real counts, the reclaim calculation for any policy you like, CSV export. It never expires and needs no key. Pro: actually executing trims, exclusions, resumable jobs and the completion report. The boundary is deliberate: the free tier tells you in euros what the paid tier is worth to you. If the number is small, don't buy it — that's the honest outcome.

A license is bound to one tenant hostname (like contoso.sharepoint.com) — that's what the checkout asks for and what the validation checks. Agencies and MSPs buy one Pro license per customer tenant. Keys are revocable: if one leaks, email support and we reissue it for your tenant and revoke the old one. The web part caches a successful validation for 7 days and tolerates network failure with a 14-day grace period (measured from the last successful validation) before Pro locks, so a licensing-server hiccup never interrupts a trim job.

Refunds: there aren't any. The free analysis already shows the exact reclaim and payback number for your tenant before you spend a cent, so there's nothing to evaluate after purchase that you couldn't see before it — and the license key unlocks Pro instantly on payment. For that reason, all Pro purchases are final. If your install genuinely doesn't work, email [email protected] with your order number — we will help you get it running, but the purchase itself is not refundable. Classic sites: the web part needs a modern page to live on, but modern pages can be added to classic team sites, and the scan then covers that site's document libraries like any other. Publishing-portal edge cases exist; run the free analysis first — if it works, Pro works.