Supabase Storage Object Size Limit

Quick Answer

Check file.size <= 52428800 bytes before calling upload()

The Limit

What is this limit?

Each individual file uploaded to Supabase Storage can be at most 50 MB (52,428,800 bytes). The per-object cap applies across all plans.

Why this limit exists

Storage is served through a shared object store; the per-object cap keeps upload and egress predictable and prevents a single upload from exhausting bandwidth or disk on shared infrastructure.

What happens when this limit is exceeded

• The upload fails with an EntityTooLarge / 413 error
• The client may receive a 'Payload too large' message
• Resumable uploads stop with a size-limit error

How to check or raise this limit

1. The 50 MB per-object cap is fixed across plans - there is no per-object raise on managed plans
2. Measure the file size client-side before upload
3. Plan for large media through external storage or compression pipelines

Code Examples

const MAX_BYTES = 50 * 1024 * 1024 // 50 MB
if (file.size > MAX_BYTES) {
  alert('File must be under 50 MB')
} else {
  await supabase.storage.from('uploads').upload(file.name, file)
}

Framework-Specific Notes

const MAX = 50 * 1024 * 1024
if (file.size > MAX) {
  throw new Error('File exceeds the 50 MB storage limit')
}

You Might Also Like

Recommended Tools

Recommendations are editorial — DB Error Reference takes no payment or affiliate fees for tool listings.

Official Sources

This page is based on the official Supabase documentation linked below and adds practical guidance on top.

• Supabase Storage FAQ (file size)official