How to Run Cron on macOS in 2025: A Complete Guide

Running cron jobs on macOS has become increasingly challenging due to Apple's enhanced security features. If you've been struggling to get your cron jobs working on modern macOS versions, this guide will walk you through the necessary steps to grant the required permissions and get everything running smoothly.

The Problem

Starting with macOS Mojave (10.14) and becoming more restrictive with each release, Apple introduced privacy protections that prevent background processes from accessing user data without explicit permission. This means your cron jobs might fail silently when trying to access files in protected locations like Desktop, Documents, Downloads, or external drives.

Prerequisites

• macOS Monterey (12.0) or later
• Administrator access to your Mac
• Basic familiarity with Terminal and cron syntax

Step 1: Grant Full Disk Access to Cron

The first crucial step is granting Full Disk Access to the cron binary. This allows cron to access files anywhere on your system.

Here's how to do it:

1. Open System Settings (or System Preferences on older versions)
2. Navigate to Privacy & Security → Full Disk Access
3. Click the lock icon and authenticate with your password
4. Click the + button to add a new exception
5. Press ⌘⇧G (Command+Shift+G) to open the "Go to folder" dialog
6. Enter /usr/sbin and press Enter
7. Find and double-click the cron file
8. Ensure the checkbox next to cron is enabled

Step 2: Grant Full Disk Access to Terminal

Since you'll be editing crontab through Terminal, it also needs Full Disk Access:

1. Still in Privacy & Security → Full Disk Access
2. Click the + button again
3. Navigate to Applications → Utilities
4. Select Terminal.app and click Open
5. Make sure Terminal is checked in the list

Step 3: Restart Crontab

After granting the necessary permissions, you need to restart your crontab for the changes to take effect:

# First, save your current crontab (if you have one)
crontab -l > ~/my_crontab_backup.txt

# Remove the current crontab
crontab -r

# Re-add your crontab
crontab ~/my_crontab_backup.txt

# Or create a new one
crontab -e

Step 4: Test Your Setup

Let's create a simple test to verify everything is working:

# Edit your crontab
crontab -e

# Add this test job that runs every minute
* * * * * echo "Cron is working! $(date)" >> ~/Desktop/cron_test.log

# Save and exit (in vim: ESC, then :wq)

Wait a minute or two, then check if the file appears on your Desktop:

cat ~/Desktop/cron_test.log

If you see timestamps appearing every minute, congratulations! Your cron is working correctly.

Common Issues and Solutions

Issue 1: Cron jobs still not running

Make sure you've granted Full Disk Access to the actual programs your cron jobs are calling. For example, if your cron job runs a Python script:

* * * * * /usr/bin/python3 /Users/yourname/script.py

You might need to grant Full Disk Access to /usr/bin/python3 as well.

Issue 2: Environment variables

Cron runs with a minimal environment. Always use full paths and set necessary environment variables at the beginning of your crontab:

PATH=/usr/local/bin:/usr/bin:/bin
HOME=/Users/yourname

# Your cron jobs below

Issue 3: Output and error handling

Always redirect output to log files for debugging:

* * * * * /path/to/script.sh >> /path/to/logfile.log 2>&1

Security Considerations

Granting Full Disk Access is a significant security permission. Only grant it to trusted applications and scripts. Regularly review your Full Disk Access list and remove permissions for apps you no longer use.

While macOS's security features can make running cron jobs more complex, it's still entirely possible with the right permissions. The key is understanding that both cron and Terminal need Full Disk Access, and you need to restart your crontab after making these changes.

Remember to always test your cron jobs thoroughly and use proper logging to troubleshoot any issues. Happy scheduling!