Skip to content
All tool news

Tool desk · Updated daily

Tool news·Vercel·

Larger Request Bodies for Vercel Functions Reach 20MiB.

Vercel’s Larger Request Bodies for Vercel Functions raises inbound payload limits from 4.5MB to 20MiB in Public Beta.

CW

Create With tool desk

3 sources checked · 2 min read · 3 sections

ShareLinkedIn
Larger Request Bodies for Vercel Functions Reach 20MiB

Larger Request Bodies for Vercel Functions raises the maximum inbound request body from 4.5MB to 20MiB. The change is available in Public Beta for larger uploads, webhooks and API payloads.

The Vercel changelog confirms support for functions using the Node.js, Python and Bun runtimes. Routing Middleware can also pass these larger requests through to a function.

Edge runtime functions remain capped at 4.5MB. They return a 413 response when a request exceeds that limit.

Runtime or componentMaximum request bodyBehaviour
Node.js functions20MiBRequires the project opt-in and 4GB performance memory
Python functions20MiBRequires the project opt-in and 4GB performance memory
Bun functions20MiBRequires the project opt-in and 4GB performance memory
Routing Middleware20MiBPasses the request through without receiving its body
Edge runtime4.5MBReturns 413 for larger bodies

Enable Larger Request Bodies for Vercel Functions

Set the VERCEL_SUPPORT_LARGE_REQUEST_BODY=1 environment variable on the project. The opt-in covers the whole project within the environment where the variable is set.

That environment-level control means the beta can be enabled for a preview environment before production. Every function in the opted-in project must use Vercel’s 4GB performance memory setting.

Routing Middleware does not receive the request body while the option is active. This avoids the increased cost of transferring and processing the larger body in middleware. The request can still continue to the destination function.

What Changes for Existing Endpoints

Projects do not receive the higher limit automatically. Without the environment variable and required memory setting, the existing 4.5MB limit remains in place.

Endpoints already using the Edge runtime also keep the existing limit, even when the project has opted into larger bodies. A function that needs to accept more than 4.5MB must run on one of the supported Node.js, Python or Bun runtimes instead.

Frequently asked questions

What are Larger Request Bodies for Vercel Functions? They are a Public Beta option that increases the inbound request body limit from 4.5MB to 20MiB. The option covers Node.js, Python and Bun functions, plus requests passing through Routing Middleware.

How do I enable the 20MiB request body limit? Set VERCEL_SUPPORT_LARGE_REQUEST_BODY=1 in the required project environment. The project’s functions must also use the 4GB performance memory setting.

Is Larger Request Bodies for Vercel Functions free? The changelog does not list pricing or eligible plan details. It states that the feature is in Public Beta and requires the 4GB performance memory setting.

Sources

3 checked

How we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.

Worth passing on?

ShareLinkedIn

Go deeper on Vercel

Related reading, watching and going.

Everything on Vercel →

The briefing

19 May 2026

How to Migrate Your App from Lovable to Claude Code in 2025

Step-by-step guide to migrating your Lovable app to Claude Code. Learn how to move from Lovable's managed platform to a stack you own and control.

Read →

The briefing

10 Feb 2026

OpenClaw Review: 2 Weeks With This AI Agent

Honest 2-week review of OpenClaw — an autonomous AI agent powered by Claude. We test setup, safety, autonomy, and real value to see if it's worth using.

Read →
34 min

Podcast

My Daughter Built a Website Business, Claude Design First Look & Going All-In on Cloudflare

James and Kieran discuss practical AI-powered development through real-world examples, including a seven-year-old building a website business with Claude Code voice mode, Anthropic's new Claude Design tool, API security challenges in the AI agent era, and Cloudflare's expanding AI infrastructure offerings. The episode covers hands-on experiences with vibe coding, emerging design tools, and the evolving landscape of AI-assisted development.

Watch now ↗

Podcast

53. Why Your Vibe Code Needs Tests, Ditching SaaS & AI Agents That Work While You Sleep

James and Kieran discuss the practical realities of building AI-powered software, emphasizing the importance of testing in vibe-coded applications, exploring alternatives to traditional SaaS tools, and implementing autonomous AI agents for business operations. The episode covers technical topics like Convex databases, app store bottlenecks from AI-generated submissions, and using OpenClaw as a marketing automation agent.

Watch now ↗
38 min

Podcast

52. Your AI Co-Founder: OpenClaw, Manus & the Zero-Person Business

In this Create With podcast episode, James and Kieran are joined by Matt Roberts from Happy Operators for an in-depth discussion on using autonomous AI agents in production. The conversation covers practical experiences with OpenClaw, security considerations, comparison with emerging tools like Manus, and the broader shift toward AI-assisted development. They also discuss the VibeCoding Olympics results, Bubble's new AI capabilities, and research on Claude.MD file effectiveness.

Watch now ↗

Latest tool news

What else changed this week.

All tool news
VercelDigest

What Vercel Shipped in Mid-November

Two updates landed on Vercel's AI Gateway, both aimed at builders running agents and coding workflows through the gateway rather than juggling separate provider keys.

The Create With Briefing

Don't watch forty changelogs. Read one email.

Every Tuesday: the tool changes worth knowing, real business use cases, and what's on near you. Free, unsubscribe any time.