Cron fields: minute, hour, day-of-month, month, weekday
Cron 스케줄을 시각적으로 구성하고 검증합니다. 쉬운 언어로 설명하고 바로 복사할 수 있는 표현식 생성.
* * * * *every minute
Common presets
*****Cron format reference
│ ┌── hour (0–23)
│ │ ┌── day of month (1–31)
│ │ │ ┌── month (1–12)
│ │ │ │ ┌── day of week (0–6, Sun=0)
│ │ │ │ │
* * * * *
*Every value*/nEvery n-th valuea-bRange from a to ba,b,cSpecific values1-5Monday to Friday0 0 * * *Daily at midnightCron fields: minute, hour, day-of-month, month, weekday
Cron is five (or six with seconds) independent fields; daylight saving can shift wall-clock triggers—prefer UTC for infra tasks when possible.
Validate expressions in staging; some platforms use quartz extensions incompatible with vanilla cron.
Reading a cron expression
┌───────── minute (0–59) │ ┌─────── hour (0–23) │ │ ┌───── day of month (1–31) │ │ │ ┌─── month (1–12) │ │ │ │ ┌─ day of week (0–6, Sunday = 0) │ │ │ │ │ 0 9 * * 1-5 → 09:00, Monday to Friday
Each field accepts * (every value), a single number, a list (1,15), a range (9-17) or a step (*/15). The builder writes these for you and shows a plain-English description of the schedule, so you can confirm it before pasting it into crontab or a CI configuration.
Worked examples
- */15 9-17 * * 1-5 — every 15 minutes from 09:00 to 17:45, weekdays only (the last run is 17:45 because the hour field stops at 17).
- 30 2 * * 0 — 02:30 every Sunday, a common slot for weekly maintenance.
- 0 0 1 * * — midnight on the first day of every month, for monthly reports.
- 0 9,18 * * * — 09:00 and 18:00 every day.
- 0 0 1 1 * — once a year at midnight on 1 January.
Gotchas that cause missed or duplicate runs
- Day of month OR day of week: when both fields are restricted, standard cron runs when either one matches. 0 0 13 * 5 runs on every 13th and on every Friday, not only on Friday the 13th.
- Uneven steps: */7 in the minute field runs at :00, :07 … :56 and then :00 again, leaving a 4-minute gap each hour. Steps only divide evenly when they are factors of 60 (minutes) or 24 (hours).
- Daylight saving time: in a local time zone, jobs scheduled between 01:00 and 03:00 can be skipped or run twice on the nights the clocks change, depending on the cron implementation. Schedule critical jobs in UTC or outside that window.
- Time zone of the server: crontab uses the machine’s time zone; GitHub Actions schedules always run in UTC; Kubernetes CronJobs can set an explicit timeZone.
- Last day of the month: standard cron has no syntax for it. Run daily on the 28th–31st and check in the script whether tomorrow is the 1st.
Cron dialects
- Standard (Vixie) cron and most Linux systems: the five fields shown here. Many also accept 7 for Sunday and three-letter names (MON, JAN).
- Quartz (Java) and Spring: six or seven fields, starting with seconds, and ? for “no specific value” in day-of-month or day-of-week.
- AWS EventBridge: six fields including a year, and one of the two day fields must be ?.
- GitHub Actions: standard five fields in UTC, with runs no more often than every 5 minutes and possible delays at busy times.
Paste the five-field output from this tool as-is into crontab, GitHub Actions or Kubernetes; for Quartz or EventBridge, add the extra fields their syntax requires.
Making a cron job run reliably
- Run the command by hand first, as the same user cron will use.
- Use absolute paths: cron starts jobs with a minimal environment and a short PATH, so commands that work in your shell may not be found.
- Capture output, e.g. 0 2 * * * /usr/local/bin/backup.sh >> /var/log/backup.log 2>&1, otherwise errors are mailed to a local mailbox nobody reads, or lost.
- Prevent overlaps for long jobs with a lock, for example flock -n /tmp/backup.lock /usr/local/bin/backup.sh.
In-depth guides
- Cron Syntax Explained: 20 Schedules You Can Copy, and the Traps to Avoid
The five cron fields, copy-ready schedules for common jobs, and the time-zone, DST and day-of-week traps across Linux, GitHub Actions and Kubernetes.
Related tools
These free tools pair well with this page — open them in a new tab to finish your workflow.
자주 묻는 질문
크론 표현식이란 무엇인가요?
크론 표현식은 반복 일정을 정의하는 5개 필드(분, 시, 일, 월, 요일)로 구성된 문자열입니다. Unix cron, GitHub Actions, 클라우드 스케줄러 등 많은 시스템에서 지정된 시간에 작업을 자동으로 실행하는 데 사용됩니다.
크론에서 별표(*)는 무엇을 의미하나요?
별표(*)는 '모든 값'을 의미합니다. 예를 들어 분 필드의 *는 '매분', 시 필드의 *는 '매시간'을 의미합니다. 해당 위치의 모든 유효한 값과 일치하는 와일드카드입니다.
15분마다 작업을 실행하려면 어떻게 하나요?
단계 구문을 사용합니다: */15 * * * *. 분 필드의 */15는 '15분마다'를 의미합니다. 마찬가지로 시 필드의 */2는 '2시간마다'를 의미합니다.
크론에서 일요일은 0인가요, 7인가요?
표준 크론에서 요일 필드의 0과 7 모두 일요일을 나타냅니다. 대부분의 크론 구현은 두 값 모두 허용합니다. 월요일은 1, 화요일은 2, 토요일은 6입니다.
크론은 시간대를 지원하나요?
기존 Unix cron은 서버의 시스템 시간대를 사용합니다. Kubernetes CronJob(타임존 필드)이나 GitHub Actions(타임존 속성) 같은 현대적인 스케줄러는 명시적인 시간대 설정을 지원합니다. cron 작업을 실행하는 서버의 시간대를 항상 확인하세요.
크론의 최소 실행 빈도는 얼마인가요?
표준 크론의 최소 해상도는 1분입니다. 1분 미만의 스케줄링에는 슬립 간격이 있는 연속 루프나 초 단위를 지원하는 작업 스케줄러(Java의 Quartz나 일부 도구의 6필드 크론 등)가 필요합니다.