Cron Expression Generator for Linux, GitHub Actions, AWS EventBridge, Kubernetes, pg_cron, Vercel, Quartz, Spring, Laravel, Airflow, Dagster, Prefect, SAP BTP, ServiceNow, Node.js, Django, Google Cloud, Azure, Plesk
Standard cron generators only support Unix/Linux syntax. Modern infrastructure is spread across GitHub Actions, AWS EventBridge, Kubernetes CronJobs, PostgreSQL pg_cron, Vercel serverless functions, Quartz Scheduler for Java, Spring @Scheduled annotation, Laravel Task Scheduler (Console/Kernel.php), Apache Airflow DAGs, Dagster Schedule definitions, Prefect Deployments, SAP BTP Job Scheduler, ServiceNow Scheduled Script Executions, Google Apps Script Time Triggers, Node.js node-cron, Django-Q and Celery Beat, Google Cloud Scheduler, Azure Logic Apps Recurrence, and Plesk/cPanel Task Scheduler — each with different syntax, field ordering, and platform-specific constraints. This tool generates the correct expression and complete ready-to-use code for all of them.
The cross-platform translator lets you take any cron expression and see the equivalent for all platforms simultaneously — essential when migrating a scheduled job from a Linux server to GitHub Actions or AWS EventBridge.
Platform-Specific Notes
Why does Vercel Cron give me a warning?
Vercel Hobby tier has a minimum interval of 1 hour. The Pro tier supports down to 1 minute intervals. This tool detects when your expression would require more frequent execution than Hobby allows and flags it. The vercel.json output format is identical — only the minimum interval differs between tiers.
What is the difference between 5-field and 7-field cron?
Standard Unix cron uses 5 fields: minute, hour, day-of-month, month, day-of-week. Quartz Scheduler (Java) uses 7 fields by adding seconds at the start and an optional year at the end. Spring @Scheduled uses 6 fields (adds seconds). This tool automatically adjusts the output format and field labels based on the selected platform.
How does pg_cron differ from standard cron?
pg_cron is a PostgreSQL extension that runs jobs inside the database. The cron expression syntax is identical to Unix cron, but jobs are scheduled with cron.schedule() and run SQL commands. Jobs must be scheduled from the postgres database even if they operate on another database. The tool generates the complete SQL including the extension setup and schedule creation.
Why does SAP BTP need a REST API call?
SAP BTP Job Scheduler does not use a crontab file. Jobs are created via a REST API call with a JSON payload that includes the cron expression. The expression syntax matches standard 5-field cron, but the delivery mechanism is different. This tool generates the complete API request body.
Can I use this for Kubernetes CronJobs?
Yes. Kubernetes CronJob spec.schedule uses standard 5-field cron syntax in UTC. The tool generates a complete CronJob manifest YAML including concurrencyPolicy (set to Forbid to prevent overlapping runs), job history limits, and a template container. Adjust the image and command to match your workload.