Explain and build cron expressions with a visual editor — privacy-first cron scheduler tool
A cron expression editor is a tool that helps you build, understand, and validate cron schedule expressions used by Unix cron daemons, Kubernetes CronJobs, AWS EventBridge, GitHub Actions, and other scheduling systems. Cron expressions use five fields (minute, hour, day-of-month, month, day-of-week) to define when a task should run, with special characters like * (every), / (step), - (range), and , (list) for complex schedules.
While cron syntax is powerful, it is also error-prone and difficult to read. An expression like 0 9 1-15 * 1-5 is not immediately obvious (it means 9:00 AM on weekdays during the first half of each month). A visual editor translates between human-readable descriptions and cron syntax, shows the next scheduled execution times, and validates that your expression will run when you expect it to — preventing costly scheduling mistakes in production systems.
PinusX provides the same cron expression parsing and explanation as crontab.guru but with 100% client-side processing — no analytics tracking, no data collection, and no server-side processing of your inputs. Every cron calculation happens locally in your browser. This is a privacy-first alternative that does not track which schedules you are configuring or use your input data for any purpose. In November 2025, jsonformatter.org (a similar type of online tool) leaked over 80,000 user credentials because of server-side processing. PinusX processes everything in your browser tab. Your cron schedules and configuration context remain entirely private.
Standard cron uses five fields separated by spaces: minute (0-59), hour (0-23), day of month (1-31), month (1-12), and day of week (0-6, where 0 is Sunday). Special characters include * (any value), / (step values), - (ranges), and , (lists). Example: 30 9 * * 1-5 means 9:30 AM every weekday.
Both tools parse and explain cron expressions. PinusX runs entirely in your browser with zero server communication, making it more private. We also provide a visual builder interface, support for non-standard 6-field and 7-field cron expressions (used by Quartz and Spring), and show more future execution times. No tracking or analytics.
The expression */5 means every 5th interval. In the minute field, */5 means every 5 minutes (0, 5, 10, 15, ...). In the hour field, */5 means every 5 hours (0, 5, 10, 15, 20). The step value divides the field range into equal intervals starting from the lower bound.
Yes. Kubernetes CronJobs use the standard 5-field cron format. Build your expression here, verify the schedule with the execution preview, then paste it into your CronJob YAML spec.schedule field. Our tool shows the schedule in UTC by default, which is what Kubernetes uses.
Yes. While standard Unix cron uses 5 fields, some systems like Quartz Scheduler and Spring use 6 or 7 fields that include seconds. Toggle the extended mode to parse expressions that start with a seconds field. This is useful for Java-based scheduling systems.
Your data never leaves your browser. 100% client-side processing.
Get instant alerts when your endpoints go down. 60-second checks, free forever.
Start Monitoring Free →