Cron tools › Platforms
Vercel cron jobs
Type the schedule of a Vercel cron job. The checker applies Vercel's own limits — no day names, never both day
fields, once a day on Hobby — shows when it fires, and writes the vercel.json entry. It can also write the same job as a
Vercel Schedule, the beta that adds a time zone.
Next runs
Configuration
Try one
How to add a cron job on Vercel
- Type the schedule in five fields. Use numbers only: Vercel does not accept
MON,SUN,JANorDEC. - Pick your Plan. On Hobby a cron job can run at most once a day, and anything more frequent fails the deployment.
- Set the Path of the function to call, starting with
/, and copy thevercel.jsonentry. - Add a
CRON_SECRETenvironment variable and check it in the route, as in the handler below, then deploy to production — cron jobs run only on production deployments. - Need local time instead of UTC? Switch Format to Schedules (beta), which takes a
timezone.
Vercel cron syntax compared with Linux cron
| Vercel | Linux cron (Vixie / cronie) | |
|---|---|---|
| Fields | minute, hour, day of month, month, day of week | the same five |
| Day of week | 0-6, Sunday = 0 | 0-7, Sunday = 0 or 7 |
| Names (MON, JAN) | Not supported | Supported |
| Day of month and day of week both set | Not allowed: when one has a value, the other must be * | Runs when either matches |
@daily-style shorthands | Not in the documented syntax (digits and * , - / only) | Supported |
| Time zone | Always UTC (Schedules: any IANA zone) | The server's zone |
The "first Monday of the month" pattern 0 9 1-7 * 1 therefore cannot be written for Vercel at all. Schedule
0 9 1-7 * * and return early in the function unless the day is a Monday. For the plain meaning of any line, use the
cron parser.
Plan limits for cron jobs
| Plan | Cron jobs per project | Most frequent | When it fires |
|---|---|---|---|
| Hobby | 100 | Once per day | Any time within the scheduled hour: 0 1 * * * can run from 1:00 to 1:59 am |
| Pro | 100 | Once per minute | Within the minute specified |
| Enterprise | 100 | Once per minute | Within the minute specified |
A Hobby expression that would run more than once a day fails the deployment with "Hobby accounts are limited to daily cron jobs. This cron expression would run more than once per day." Disabled cron jobs still count towards the 100.
How Vercel calls the function
- An HTTP
GETto the production deployment URL plus thepath, with the user agentvercel-cron/1.0. - The
x-vercel-cron-scheduleheader holds the expression that fired, so several jobs can share one path. - With a
CRON_SECRETenvironment variable, the request carriesAuthorization: Bearer <secret>. A deployment keeps the value it was built with, so a new secret takes effect after the next deployment. - A failed run is not retried. Redirects are not followed, which trips up Next.js
trailingSlash: put the slash in the path. - Delivery is best effort: a run can occasionally be missed or delivered twice, and a long job can overlap the next one. Make the job idempotent.
Cron Jobs or Schedules?
Vercel calls Cron Jobs a legacy feature that "will be migrated to Schedules in the future". Schedules (public beta) use the same
five-field syntax but are declared under schedules, keyed by a name, and add a timezone (IANA, default UTC)
and a jitter window: each run starts at some point within 1-15 minutes of its time (Pro and Enterprise default to 1, Hobby
is always 15). The shortest interval between runs must be at least the jitter window, so Hobby schedules can run every 15 minutes
rather than once a day. A path schedule sends POST by default; set "requestMethod": "GET" to keep a cron
route unchanged, and remove the old crons entry, or the route runs twice. Named time zones follow daylight saving time;
what happens in the skipped or repeated hour is not documented — see the DST checker.
FAQ
Why did my Vercel cron job not run?
Cron jobs run only on production deployments, not previews. Also check that the path exists and does not redirect (Vercel does not
follow redirects), and that the CRON_SECRET check is not returning 401.
Can I run a Vercel cron job every 5 minutes on Hobby?
Not as a Cron Job: Hobby allows once per day, and */5 * * * * fails the deployment. As a Schedule the Hobby limit is
every 15 minutes, because the jitter window is always 15 minutes. Pro and Enterprise allow every minute.
Which time zone do Vercel cron jobs use?
UTC, always. 0 9 * * * is 09:00 UTC. For local time either convert the hour yourself — the
time zone converter does it — or use a Schedule with a timezone.
Can I use MON-FRI in a Vercel cron expression?
No. Write the numbers: 0 9 * * 1-5 is 09:00 UTC on weekdays, with 0 for Sunday and 6 for Saturday.