How to set up Cron Jobs in cPanel
cPanel Cron Jobs are scheduled tasks that run at set times or intervals. They let you automate repetitive work on your site without having to do it by hand each time.
When should you use a Cron Job?
- Run maintenance scripts for your site.
- Launch scheduled tasks for your application.
- Process periodic sends or cleanups.
On shared hosting it is best to start with a moderate frequency so you do not use too many resources.
Before you start
- You need access to cPanel.
- Have the full path of the script you want to run ready.
- Confirm the frequency your application recommends (hourly, once a day, etc.).
- If you use your own script, make sure it has execute permission.
Avoid dangerous deletion commands: an automated task repeats the mistake on every run.
Create the Cron Job in cPanel
- Log in to cPanel and open Cron Jobs in the advanced features section.
- Under Cron Email, enter an address to be notified when the task runs and save with Update Email (optional).
- Under Common Settings, choose a base frequency, for example once per hour; this fills in the minute, hour, day, month, and weekday fields.
- If you need something more specific, adjust those five fields manually.
- Under Command, enter the full command using absolute paths for the interpreter and the script.
- Click Add New Cron Job to save.
If your panel is in another language, the labels may vary slightly. Using absolute paths avoids failures when the system cannot find the file through a relative path.
Test the Cron Job
- Wait until the schedule you set has passed.
- Check the notification email if you enabled Cron Email.
- Confirm the expected change in your application or its logs.
- If you see no result, create a simple test task that writes to a file and check again.
Edit or delete the Cron Job
- In Cron Jobs, scroll down to Current Cron Jobs to see the task list.
- Use Edit and adjust the line to change the frequency or command without duplicating the task.
- Use Delete and confirm when the task is no longer needed.
- Avoid leaving several tasks that do exactly the same thing.
Final verification
- The Cron Job appears in the current tasks list.
- The configured frequency is the one you actually wanted.
- The command and path are written without errors.
- The application shows signs of execution (logs or expected changes).
Common errors
- The task does not run → The script path is incorrect → Check the full path from File Manager.
- It uses too many resources → The frequency is too high → Increase the interval between runs.
- Nothing happens when it runs → The interpreter or a parameter is missing from the command → Complete the command with the interpreter and the absolute path.
- You do not know if it ran → There is no visible output → Enable Cron Email or add a log to a test file.
When to ask for help
If the task does not run after checking the path and command, if you need an uncommon frequency, or if you are unsure of the right interpreter, open a ticket from your client area. Share the exact command and the expected frequency so support can guide you within your shared hosting.
Recommended reading
Still need help?
If this guide didn’t solve your issue, our team can help you via ticket.