Closed iiskakov closed 4 weeks ago
We ran into the same issue earlier. Here’s a bit more info: https://vercel.com/docs/errors/FUNCTION_PAYLOAD_TOO_LARGE
We ran into the same issue earlier. Here’s a bit more info: https://vercel.com/docs/errors/FUNCTION_PAYLOAD_TOO_LARGE
Yup, thanks, I've seen this. If I understood it correctly - vercel functions are not supposed to be used to transfer data basically, and current way of how uploads are implemented uses them (not by design though) 🤔
Is there any movement on this? Or work arounds.
I would love to hear more about this too
Yes, this is a known limitation. We need to implement client uploads, so the uploads do not go through Vercel which limits the file size that can be uploaded. Here is the related discussion: https://github.com/payloadcms/payload/discussions/7569
Hey @JarrodMFlesch is there a current recommended workaround to just upload directly to s3 or s3 compatible storage like supabase, r2, while still integrating with the admin media collection?
This issue has been automatically locked. Please open a new issue if this issue persists with any additional detail.
Link to reproduction
https://github.com/iiskakov/is-it-really-one-click-though
Environment Info
Describe the Bug
When deploying a Payload v3 project on Vercel using the S3 plugin for file uploads, Vercel’s 4.5MB file upload limit still applies. This severely restricts media-heavy projects, as file uploads beyond this size fail, even though external storage (S3) is configured. This limitation isn’t documented, and it's critical for projects relying on large file uploads, especially given Payload’s “Next.js-first” marketing for v3.
Reproduction Steps
Adapters and Plugins
@payloadcms/storage-s3