SWA deployment failed with the Reason: The size of the function content was too large

Question

SWA deployment failed with the Reason: The size of the function content was too large

Vadim Parfaniuc - US 0

Hello, we started receiving the following error message when deploying new builds to SWA, however, we are on the Standard plan and the size of the build should be set to 500Mb. Please advise.

Done Zipping Api Artifacts

The content server has rejected the request with: BadRequest

Reason: The size of the function content was too large. The limit for this Static Web App is 262144000 bytes.

Grmacjon-MSFT 19,076 Reputation points Moderator

2025-05-01T19:11:34.7266667+00:00
Hi Vadim Parfaniuc - US

We're sorry to hear you're facing this is issue. Could you please share the approximate size of your api folder (or the directory containing your Azure Functions) before the deployment process? What programming language and framework are you using for your Azure Functions (Node.js, .NET, etc)?

The error message is explicitly pointing to the size of your API artifacts (Azure Functions) being too large. While the Standard plan has a larger overall build size limit, there's a separate, smaller limit for the deployed size of your Azure Functions within the Static Web App. The 250 MB limit in the error message is the current limit for the total size of your function app deployed to Static Web Apps, even on the Standard plan.

To resolve, take a look into the contents of your api folder (or the directory you've configured for your Azure Functions). Investigate what's contributing to its size by:

Locally, navigate to your built API artifact directory (usually within the .azure/functions or a similar path after your build process).

Check the total size of this directory.

Drill down into the subdirectories to identify the largest contributors to the size (development dependencies, large data files, build artifacts that aren't needed at runtime, etc).

Hope that helps.

-Grace
Vadim Parfaniuc - US 0 Reputation points

2025-05-01T20:37:53.0133333+00:00

Hi Grmacjon-MSFT, thank you for looking into this issues. we are using node.js so the npm run build generates .next folder which is 28M however the size of the node_modules folder is 719M. if I correctly understand, the deployment task should push up to the SWA only the .next folder.

1 answer

Your answer

Grmacjon-MSFT 19,076 Reputation points Moderator

2025-05-01T19:11:34.7266667+00:00

Hi Vadim Parfaniuc - US

We're sorry to hear you're facing this is issue. Could you please share the approximate size of your api folder (or the directory containing your Azure Functions) before the deployment process? What programming language and framework are you using for your Azure Functions (Node.js, .NET, etc)?

The error message is explicitly pointing to the size of your API artifacts (Azure Functions) being too large. While the Standard plan has a larger overall build size limit, there's a separate, smaller limit for the deployed size of your Azure Functions within the Static Web App. The 250 MB limit in the error message is the current limit for the total size of your function app deployed to Static Web Apps, even on the Standard plan.

To resolve, take a look into the contents of your api folder (or the directory you've configured for your Azure Functions). Investigate what's contributing to its size by:

Locally, navigate to your built API artifact directory (usually within the .azure/functions or a similar path after your build process).

Check the total size of this directory.

Drill down into the subdirectories to identify the largest contributors to the size (development dependencies, large data files, build artifacts that aren't needed at runtime, etc).

Hope that helps.

-Grace
Vadim Parfaniuc - US 0 Reputation points

2025-05-01T20:37:53.0133333+00:00

Hi Grmacjon-MSFT, thank you for looking into this issues. we are using node.js so the npm run build generates .next folder which is 28M however the size of the node_modules folder is 719M. if I correctly understand, the deployment task should push up to the SWA only the .next folder.

Answer 1

Grmacjon-MSFT 19,076 Moderator

Yes, that is correct Vadim Parfaniuc - US.

Given that your .next folder is already small (28MB), so focus should be on reducing the size of the node_modules folder associated with your Azure Functions as shared on this similar thread on github.

One of the workaround is to Run **npm install --production or yarn install --production **within your api directory. This will install only the dependencies needed for production, excluding development dependencies.

You should also review your api/package.json file and remove any unnecessary dependencies. If you're using a build process for your functions (e.g., for TypeScript), please make sure that the build output only includes the necessary files and dependencies.

Grmacjon-MSFT 19,076 Reputation points Moderator

2025-05-05T17:52:40.12+00:00

@Vadim Parfaniuc - US checking in to see if the above helped answer your question. Please let us know if you have further questions

Share via

SWA deployment failed with the Reason: The size of the function content was too large

1 answer

Your answer