SharePoint / SharePoint/sp-dev-docs

Marketplace SPFx .sppkg update size limit is capped at 25 MB

Open
#10,934 9 comments 0 reactions 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since Jul 7, 2026.

area:spfx sharepoint-developer-support
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

Description

What type of issue is this?

other

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested
  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)
Additional environment details
  • Browser version: not applicable; this is a Marketplace package upload/update limitation
  • SPFx version: 1.22.2
  • Node.js version: v22.14.0
  • Package size: ~30.8 MB after production build
  • Build command: heft build --clean --production && heft package-solution --production
  • Package setting: includeClientSideAssets: true
Issue description

We are hitting the 25 MB marketplace update size limit for an SPFx .sppkg package.

Image

We are building a client-side CAD viewer for SharePoint. The package is about 30.8 MB after production build because it includes the runtime assets needed to render CAD and 3D files in the browser.

This appears to be specifically a Marketplace upload/update limitation. The same .sppkg can be uploaded through the tenant App Catalog, so there is already precedent for SharePoint accepting larger SPFx packages.

Could Microsoft increase the Marketplace SPFx .sppkg update size limit above 25 MB? Anything above the current limit would help; 50 MB would give Marketplace SPFx apps with legitimate client-side runtime assets much more breathing room.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.