Edge Function limits per plan.
| Limit | Free | Pro | Scale | Enterprise |
|---|---|---|---|---|
| Edge Functions per project | 10 | 100 | 250 | 1,000 |
| Edge Function invocations per month | 500,000 | 2,000,000 | 5,000,000 | 25,000,000 |
| Edge Function CPU time per month (account) | 10,000 CPU-s | 30,000 CPU-s | 100,000 CPU-s | 500,000 CPU-s |
| Edge Function size (all files) | 5,120 KB | 20,480 KB | 20,480 KB | 20,480 KB |
| Edge Function memory | 128 MB | 150 MB | 256 MB | 256 MB |
| Edge Function CPU time per request | 2,000 ms | 2,000 ms | 4,000 ms | 4,000 ms |
| Edge Function wall-clock limit | 60 s | 150 s | 400 s | 400 s |
- CPU time counts only the time your code computes; waiting for
fetchor the database does not count. Wall-clock is the total time a request (includingwaitUntilwork) may take. - A function that goes over its CPU time or memory is stopped and the request gets
546. - When the monthly invocations are used up, functions answer
429 QUOTA_EXCEEDEDuntil the 1st of next month or until you upgrade. - Request bodies up to 20 MB. Your plan's API requests per second apply to functions too.
- Paused projects answer
503until they are restored. - Work that takes longer than the wall clock (imports, batch e-mails, AI calls over many documents) fits background jobs: in steps, or in job mode as one run of up to 60 minutes.