{
  "agent": {
    "identifiers": [],
    "kind": "announcement",
    "review": "editorial",
    "source_fingerprint": "682294208b046480e0d3f1602482783310f8d65dc9bce706ff55fd58dd18e6fb",
    "source_id": "vercel-functions-changelog",
    "source_key": "https://vercel.com/changelog/vercel-functions-now-support-request-bodies-up-to-20mib",
    "version": null
  },
  "category": "infrastructure",
  "commercial_opportunities": null,
  "compatibility_and_migration": "Use the 4 GB Performance memory setting and set VERCEL_SUPPORT_LARGE_REQUEST_BODY to 1. Check whether Routing Middleware reads request bodies.",
  "confidence": "high",
  "developer_impact": "Functions can receive larger uploads and webhook payloads on eligible runtimes.",
  "discovery_date": "2026-11-21",
  "event_date": "2026-11-20",
  "evidence": [
    {
      "basis": "Maintainer release notes or announcement.",
      "fields": [
        "title",
        "event_date",
        "technical_description",
        "what_changed",
        "previous_behavior",
        "new_behavior",
        "developer_impact",
        "known_limitations",
        "compatibility_and_migration",
        "summary"
      ],
      "url": "https://vercel.com/changelog/vercel-functions-now-support-request-bodies-up-to-20mib"
    }
  ],
  "id": "evt-620f7b8b350ea82cea7b5bc2",
  "known_limitations": "Edge runtime deployments retain the 4.5 MB limit. This beta covers inbound bodies.",
  "new_behavior": "The opt-in applies to the project environment. Routing Middleware in an opted-in project receives other request metadata without the body.",
  "organization": "Vercel",
  "previous_behavior": "The previous request body limit was 4.5 MB.",
  "priority": {
    "band": "P2",
    "dimensions": {
      "adoption_potential": {
        "reason": "The source gives users a way to evaluate the change. Adoption was not measured.",
        "value": 4
      },
      "agent_relevance": {
        "reason": "Agent backends that ingest payloads may use the new limit.",
        "value": 3
      },
      "commercial_opportunity": {
        "reason": "This editorial record assesses technical adoption.",
        "value": 0
      },
      "commoditization_risk": {
        "reason": "Market effects were not assessed.",
        "value": 0
      },
      "security_impact": {
        "reason": "The record makes no security severity claim.",
        "value": 0
      },
      "source_credibility": {
        "reason": "The maintainer reports the release and its stated behavior.",
        "value": 5
      },
      "technical_significance": {
        "reason": "The beta changes request handling limits and middleware behavior.",
        "value": 4
      },
      "time_sensitivity": {
        "reason": "Integration teams can review the change before the next deployment.",
        "value": 3
      }
    },
    "reason": "Weighted evidence score of 52. The score meets the P2 threshold.",
    "score": 52
  },
  "related_event_ids": [],
  "revision": 1,
  "schema_version": 1,
  "security_implications": null,
  "security_severity": null,
  "source_authority": "maintainer",
  "source_urls": [
    "https://vercel.com/changelog/vercel-functions-now-support-request-bodies-up-to-20mib"
  ],
  "status": "active",
  "summary": "Eligible Node.js, Python, and Bun functions can accept 20 MiB inbound bodies in beta. Check memory settings and body-dependent middleware before opting in.",
  "tags": [
    "public-beta",
    "request-limits",
    "infrastructure"
  ],
  "technical_description": "Vercel Functions can opt in to a 20 MiB inbound request body limit in public beta.",
  "technology": "Vercel Functions",
  "title": "Vercel Functions raise inbound request limits to 20 MiB in beta",
  "verification_date": "2026-11-21",
  "what_changed": "Eligible projects can raise the inbound request body limit from 4.5 MB to 20 MiB for supported runtimes."
}
