Human to Cron
Natural language to cron converter online. Build cron expressions with dropdowns. Human-readable cron builder—convert schedule to cron free.
Your Cron Schedule
0 9 * * 1,2,3,4,5 At 09:00 AM, only on Monday, Tuesday, Wednesday, Thursday, and Friday
7/8/2026, 9:00:00 AM7/9/2026, 9:00:00 AM7/10/2026, 9:00:00 AM
How often should it run?
At what time?
Hour
Minute
On which days?
MIN HR DAY MON DOW
Features
- Type your desired schedule in natural plain English (e.g., "every tuesday at 4pm")
- AI-driven contextual parsing translates the phrase directly into valid cron syntax
- Supports complex clauses ("every 15 minutes between 9am and 5pm")
- Instant reverse-explanation validation generated automatically
- Handles colloquialisms like "weekdays", "midnight", or "weekends"
Common Use Cases
- Writing infrastructure schedules without needing to memorize cron syntax rules
- Quickly prototyping deployment triggers during meetings or brainstorming
- Allowing non-technical product managers to generate schedule configurations safely
- Converting legacy English documentation directly into code-ready cron strings
Natural Language Scheduling
Generative natural language processing bridges the gap between human intent and the strict structural bounds of system architecture.
When you type "every weekday at 6:30 PM", the parser maps the linguistic tokens to the cron fields:
- "6:30 PM" → Minute
30and Hour18(24-hour clock conversion) - "every weekday" → Days
1-5(Mon-Fri) instead of the*wildcard
Resulting output: 30 18 * * 1-5
Examples
Valid - Simple Input
Every Monday at 9:00 AM Valid - Range Input
Every 30 minutes from 10am to 2pm Valid - Specific Days
On the 1st and 15th of the month at midnightFrequently Asked Questions
Can the tool understand "every other week"?
Natural Language to Cron has limitations based on the underlying cron spec itself. Since pure cron cannot do modulo math on weeks, requests for "bi-weekly" schedules might generate approximations or fallbacks.
How specific do I need to be in my sentences?
Try to be clear about Minutes, Hours, and Days. "Every morning" is vague and might default to 8:00 AM. It is better to write "Every morning at 8:30 AM".
Does this handle timezone phrases?
If you type "at 5 PM EST", the translated cron string will still just output `0 17 * * *`. You must ensure the environment executing the cron is locally set to EST, or shift the math to UTC yourself.
💡 Tips
- Always use the companion "Next Run Calculator" to verify that the generated output from your English phrase perfectly matches your actual intentions.
- Keep your language simple and instructional rather than conversational for best parsing accuracy.