Cron on macOS (and the launchd Equivalent)
macOS still includes cron and crontab -e works, but Apple's supported scheduler is launchd. For a job that must survive OS updates and run reliably, write a LaunchAgent .plist; for a quick personal task, plain crontab is fine.
Plain cron still works
On a Mac you can run crontab -e and add 0 9 * * * /usr/bin/say hello exactly as on Linux. The first time, grant your terminal Full Disk Access in System Settings > Privacy or cron jobs touching protected folders will silently fail.
The launchd equivalent
Create ~/Library/LaunchAgents/com.example.job.plist with a StartCalendarInterval block (Hour 9, Minute 0), then launchctl load ~/Library/LaunchAgents/com.example.job.plist. launchd re-runs missed jobs after sleep, which cron does not.
Which to use
Use launchd for anything important or that runs while the Mac may be asleep. Use crontab for throwaway personal scripts where simplicity wins.
FAQ
Does cron work on macOS?
Yes, crontab -e still works on macOS, but Apple recommends launchd. Grant your terminal Full Disk Access or cron jobs touching protected folders fail silently.
What is the launchd equivalent of a cron job?
A LaunchAgent .plist in ~/Library/LaunchAgents with a StartCalendarInterval block, loaded via launchctl load. It re-runs jobs missed during sleep, unlike cron.
Why does my Mac cron job not run?
Most often macOS privacy protection: give your terminal (or /usr/sbin/cron) Full Disk Access in System Settings > Privacy & Security.