Your site builds on AWS Amplify, then deployment stops because the output is too large. If you're tired of trimming a working app to get the next release out, deploy the site on Forte. Forte builds from your GitHub repository, so you can test the same source on a new host before moving your domain.
This is the kind of error that sends teams looking for another option:
2026-11-11T19:09:28.860Z [ERROR]: !!! CustomerError: The size of the build output (240030978) exceeds the max allowed size of230686720 bytes. Please reduce the size ofyour build output and try again.Amplify has rejected the size of the deployment output. A larger build machine won't change that limit. You can reduce what you ship, or move the site to a host that packages it differently.
What the Amplify build-size error means
AWS documents a build output limit of 220 MB for server-side rendered apps. Server-side rendering, or SSR, means the host runs server code to produce a page when someone requests it. The limit in this error, 230686720 bytes, is exactly 220 MiB, where a MiB is 1,048,576 bytes. AWS SSR troubleshooting guide
The reported output is about 229 MiB. That's enough to block this deployment even if the app code compiled successfully. These figures describe the supplied error, rather than a benchmark of how large a typical app becomes.
For apps that use the Amplify deployment specification, AWS applies the limit to each uncompressed compute bundle. That's the folder containing the server and the files it needs to run. Compressing the archive further doesn't make those unpacked files smaller. Amplify deployment specification
A small feature can bring a large server dependency
A page can look almost unchanged while its server output grows. Imagine adding PDF exports to a reports app. If the implementation ships a browser binary or large font files with the server, those files become part of what the host must deploy.
The same concern applies to image-processing libraries, bundled data files, and dependencies that include native binaries. Check what actually reached the output before removing anything. A package can be large and still be needed by a route your customers use.
You can inspect the Amplify artifacts and remove files that the app doesn't need at runtime. AWS describes that approach in its troubleshooting guide. It can be a sensible fix when the output contains unused files. When the files are required, deploying on Forte gives you another path without cutting the feature just to fit the bundle limit.
Deploy the site on Forte
Start with the GitHub branch containing the release you want to ship. You'll need a Forte account and the Forte GitHub App installed for that repository. Keep the Amplify deployment serving your domain while you test.
- Open the Forte console and select or create a Project for the site.
- Open Websites, choose Create Website, and select the repository and branch.
- Review the site's environment variables and secrets. Set the values it needs on Forte before relying on the new deployment.
- Create the Website and follow its first build. Forte detects the framework, package manager, build command, and output directory from the repository. Use the advanced settings if your project needs an override.
- Open the generated URL and test the pages and server routes your visitors use.
The website deployment guide covers the full setup. Forte builds the site through its own hosting pipeline; you don't upload the rejected Amplify artifact or carry over the Amplify packaging step.
If your SSR app needs Forte to authenticate incoming requests or record them for debugging, deploy it as a Service. A Website serves traffic directly and doesn't provide those gateway features. Your app still owns its access rules.
Check the release before moving your domain
Test the feature that increased the output. For the reports app, generate a PDF and open it. Load a page directly, refresh a nested route, and check that images and fonts arrive. If the app has sign-in, test the callback and a page that requires a session.
Review the Website runtime limits too. Changing hosts removes this Amplify packaging limit from your release path; the new host still has build and runtime limits. For example, long-running exports may need a separate backend workflow.
Once the new URL works, follow the custom-domain setup to connect your domain. Update any sign-in callback settings that depend on the domain name, then repeat the same checks through the domain visitors use.
You can keep optimizing dependencies because smaller deployments are useful. Deploying on Forte lets you plan that work separately from getting past the Amplify build-size error.