What is the cron expression for every 30 minutes?

The cron expression for every 30 minutes is */30 * * * *. This schedule runs 48 times per day.

How do I set up a cron job for every 30 minutes?

Open your crontab with 'crontab -e' and add a line starting with '*/30 * * * *' followed by the command you want to run. For example: */30 * * * * /path/to/script.sh

Cron Expression for Every 30 Minutes

Q: What does each field in */30 * * * * mean?

A cron expression has 5 fields: minute (*/30), hour (*), day of month (*), month (*), and day of week (*). In */30 * * * *: */30 — every 30th minute (0, 30); * — every hour.

*/30 * * * *

Expression Breakdown

The cron expression */30 * * * * schedules a job to run every 30 minutes. A standard cron expression consists of five fields representing minute, hour, day of month, month, and day of week. Here is what each field means in this expression:

Minute	`*/30` — every 30th minute (0, 30)
Hour	`*` — every hour
Day of Month	`*` — every day of the month
Month	`*` — every month
Day of Week	`*` — every day of the week

This schedule runs 48 times per day (2 times per hour), which amounts to 336 times per week and approximately 1440 times per month.

Next 5 Run Times

Starting from April 11, 2026 00:00 UTC, the next five executions are:

2026-04-11T00:00:00Z — Sat, 11 Apr 2026 00:00:00 GMT
2026-04-11T00:30:00Z — Sat, 11 Apr 2026 00:30:00 GMT
2026-04-11T01:00:00Z — Sat, 11 Apr 2026 01:00:00 GMT
2026-04-11T01:30:00Z — Sat, 11 Apr 2026 01:30:00 GMT
2026-04-11T02:00:00Z — Sat, 11 Apr 2026 02:00:00 GMT

Common Use Cases

Running a task every 30 minutes is a popular cron schedule. Here are some typical applications:

Report generation: Report generation and automated summaries
Inventory sync: Inventory sync between e-commerce platforms
DNS record: DNS record propagation checks
Automated backup: Automated backup verification and integrity checks

Code Examples

Linux / macOS Crontab

# Open crontab editor
crontab -e

# Add this line to run your script every 30 minutes
*/30 * * * * /usr/local/bin/my-task.sh

# With logging
*/30 * * * * /usr/local/bin/my-task.sh >> /var/log/my-task.log 2>&1

Python (schedule library alternative)

# Using APScheduler with cron trigger
from apscheduler.schedulers.blocking import BlockingScheduler
from apscheduler.triggers.cron import CronTrigger

scheduler = BlockingScheduler()
trigger = CronTrigger.from_crontab("*/30 * * * *")
scheduler.add_job(my_function, trigger)
scheduler.start()

JavaScript (Node.js with node-cron)

const cron = require('node-cron');

// Run task every 30 minutes
cron.schedule('*/30 * * * *', () => {
  console.log('Task running at', new Date().toISOString());
  // Your task logic here
});

Frequently Asked Questions

What does each field in */30 * * * * mean?

A cron expression has five fields separated by spaces: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-7, where 0 and 7 are Sunday). The */n syntax means "every nth interval." In */30 * * * *, the fields are: */30 — every 30th minute (0, 30); * — every hour; * — every day of the month.

How do I verify that */30 * * * * is correct?

Use the EpochPilot Cron Expression Builder to paste your expression and see the next run times visually. You can also use the crontab -l command to list your current crontab entries, or test with a simple echo command: */30 * * * * echo "test" >> /tmp/cron-test.log.

What timezone does cron use?

By default, cron uses the system timezone configured on your server. On most cloud servers this is UTC. You can check your system timezone with timedatectl on Linux or date +%Z. Some cron implementations (like Kubernetes CronJobs) let you specify a timezone explicitly. Always verify your server's timezone to ensure jobs run at the expected times.

Try the Cron Expression Builder to create and test cron schedules.