2025-10-29T10:39:32.987Z [ERROR]: !!! CustomerError: The size of the build output (240686834) exceeds the max allowed size of230686720 bytes. Please reduce the size ofyour build output and try again.

[HarshitSrivastava007]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have removed any sensitive information from my code snippets and submission.

Amplify Hosting feature

Build settings

Is your feature request related to a problem? Please describe:

2025-10-29T10:39:32.987Z [ERROR]: !!! CustomerError: The size of the build output (240686834) exceeds the max allowed size of230686720 bytes. Please reduce the size ofyour build output and try again.

Describe how you'd like this feature to work

Please provide solution for this

[github-actions]

This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!

[jbreemhaar]

Yeah could you guys at aws/amplify please upgrade the max allowed size? It's been this for the last 3 or 4 years if I remember correctly. Next@16 is able to generate a much larger build size, and I'm currently blocked from upgrading to it because of this size limitation. We have around ~300 SSG pages because we support 5 different languages, so it's a lot of contentpages x 5 prerendered.

In nextjs 16, every page gets some additional meta payload which bumps us over the edge of the amplify hosting limit.

[jagmitg]

We've also hit a wall with this and it would be nice to increase the number. Or even allow us to define the storage.

[moeBabazadeh]

I encountered this issue after upgrading to Next.js v16. My build output exceeded the AWS Amplify 220MB limit (reaching ~302MB), specifically due to a bloated .next/server folder.

The Solution: Next.js v16 generates large server-side source maps by default. Disabling them in the config reduced the build size significantly.

Update your next.config.js (or next.config.mjs):

/** @type {import('next').NextConfig} */
const nextConfig = {
  // ... other config
  experimental: {
    // Disabling server source maps reduces .next/server size significantly
    serverSourceMaps: false,
  },
};
export default nextConfig;

After this change, my standard Amplify build passed successfully.
Hope this helps anyone stuck with this error. :)