Vercel Functions now accept request bodies up to 20MiB in Public Beta
Vercel Functions now accept inbound request bodies up to 20MiB, up from 4.5MB, in Public Beta. The larger limit is enabled per project with the VERCEL_SUPPORT_LARGE_REQUEST_BODY=1 environment variable and requires the 4GB performance memory setting; it applies to Node.js, Python, and Bun runtimes and to Routing Middleware, while Edge runtime functions keep the 4.5MB cap.

Why it matters
Builders handling file uploads or large payloads on Vercel can now accept bodies up to 20MiB without leaving the platform, but must switch affected functions to the Node.js runtime and 4GB memory. When a project opts in, Routing Middleware no longer receives the request body, so any middleware logic that depends on body content will stop working.
Who should care
Developers and agencies running Next.js or other frameworks on Vercel Functions, especially teams handling uploads, form submissions, or body-dependent Routing Middleware.
What you can do
Set VERCEL_SUPPORT_LARGE_REQUEST_BODY=1 in a Preview environment, confirm functions use 4GB memory and the nodejs runtime, and audit any Routing Middleware that reads the request body before enabling it in production.