Lambda payload size limit
A synchronous Lambda invocation can carry up to 6 MB in the request and 6 MB in the response; an asynchronous invocation (Event invocation type, S3, SNS or EventBridge style triggers) is limited to 1 MB; and a function using response streaming can send up to 200 MB back. These limits are fixed. For anything bigger, put the data in S3 and pass the object key or a presigned URL.
The payload limits
| Invocation | Request | Response | Adjustable |
|---|---|---|---|
| Synchronous (RequestResponse) | 6 MB | 6 MB | No |
| Synchronous with response streaming | 6 MB | 200 MB | No |
| Asynchronous (Event) | 1 MB | Not returned to caller | No |
| Request line and headers (function URLs) | 1 MB combined | - | No |
The Lambda documentation uses MB to mean 1,048,576 bytes, so the synchronous limit is 6,291,456 bytes. Responses larger than 6 MB that are streamed are capped in bandwidth: the first 6 MB go out uncapped and the rest at 2 MBps.
The caller usually has a smaller limit
The 6 MB ceiling is rarely the one you hit first. Each service in front of Lambda has its own size limit, and the smallest one wins:
| Front door | Its limit | Notes |
|---|---|---|
| API Gateway REST or HTTP API | 10 MB payload | Lambda's 6 MB applies first for Lambda proxy integrations |
| Application Load Balancer | 1 MB request and response body for Lambda targets | Larger bodies fail at the load balancer |
| SQS event source | 1 MiB per message | Batch of messages is assembled up to Lambda's limit |
| SNS, EventBridge (async) | 1 MB async limit on Lambda | Large events need a claim-check pattern |
| Step Functions Lambda task | 256 KiB state payload | See Step Functions limits |
Base64 encoding for binary data adds about a third, so a 4.6 MB binary file is already close to 6 MB once it is encoded for an API Gateway proxy event.
What the errors look like
An error occurred (RequestEntityTooLargeException) when calling the Invoke operation:
Request must be smaller than 6291456 bytes for the InvokeFunction operationOn the response side, a function that returns more than 6 MB fails at the end: the caller gets an error even though the function's own logs show it ran to completion, which is a useful clue when the code looks fine. The RequestEntityTooLarge page covers both directions and the deploy-time variant of the same exception.
To see how big a request is before you send it:
# Size in bytes of the event you are about to send
wc -c < event.json
# Invoke with a file payload (raw JSON, not base64)
aws lambda invoke --function-name report-builder --cli-binary-format raw-in-base64-out \
--payload fileb://event.json response.jsonDesigning around it
- Claim check: upload the large object to S3, send
{"bucket": "...", "key": "..."}in the event, and have the function read it. This is the standard fix for async and queue-driven paths. - Presigned URLs for clients: instead of uploading through API Gateway and Lambda, return a presigned PUT URL and let the client upload straight to S3; for downloads, return a presigned GET URL or redirect.
- Response streaming for large or slow responses to HTTP clients via function URLs or API Gateway REST APIs set to stream.
- Compress text payloads such as JSON or CSV when you control both ends; gzip often shrinks them five to ten times.
- Trim events: API Gateway proxy events include headers and request context you may not need; with a custom integration you can map only the body.
Questions
What is the maximum response size for a Lambda function?
6 MB for a normal synchronous invocation, or up to 200 MB when the function streams its response.
Is the Lambda payload limit 256 KB for asynchronous invocations?
That was the older limit. The Lambda quotas page now lists 1 MB for asynchronous invocations at the time of writing; older blog posts and SDK comments still mention 256 KB.
Can I increase the Lambda payload size limit?
No. The payload limits are fixed. Use S3 for large data, or response streaming for large responses.
Payload errors often appear only for a few large customers or files, so they hide in error rates. CloudConsole, a phone app for AWS, is being built to surface those error alarms and the log lines behind them on your phone.
About the app → · Download on the App Store