Cron every Wednesday at 18:00: the expression, explained, in WordPress

The cron expression for “every Wednesday at 18:00” is 0 18 * * 3. This page shows what each field does, the next five times it will fire, the mistake most people make with it, and a working WordPress example you can paste.

The expression

0 18 * * 3

Field	Value	Meaning
minute	0	exactly 0
hour	18	exactly 18
day of month	*	every day of month
month	*	every month
day of week	3	Wednesday only

Next five runs (UTC, from now)

2026-09-23 18:00 UTC
2026-09-30 18:00 UTC
2026-10-07 18:00 UTC
2026-10-14 18:00 UTC
2026-10-21 18:00 UTC

Mistakes people make with this schedule

Filling both day-of-month and day-of-week. In classic cron they combine with OR, so "0 18 1 * 3" runs on the 1st and on every Wednesday.
Assuming the server clock is your clock. Cron runs in the machine’s timezone unless the runtime says otherwise; the examples here are UTC.
No lock around a job that might overlap itself, and no alert when it silently stops. That second one is what Supercrontab is for.

Run it in your stack

Linux crontab Laravel WordPress Next.js / Vercel Node.js Python Docker GitHub Actions

// WP-Cron only fires on page loads. Disable it and call wp-cron.php
// from a real scheduler instead:
// define('DISABLE_WP_CRON', true);

0 18 * * 3 curl -fsS https://example.com/wp-cron.php?doing_wp_cron

On low-traffic sites WP-Cron drifts. An external caller makes it exact.

Questions

Does 0 18 * * 3 run in my local time?

Only if the scheduler is configured for it. crontab uses the system timezone; Vercel and GitHub Actions always use UTC; Laravel and node-cron take a timezone option. In Supercrontab the timezone is a field on the job.

What if the previous run is still going?

Classic cron starts the next run anyway. Add a lock (flock on Linux, withoutOverlapping() in Laravel) or let Supercrontab skip the tick while the previous request is open.

Is there a shorter way to write this?

No. The five-field form is the shortest portable version.