Cron Parser
Valida y ve próximas ejecuciones
- #1Jun 29, 2026, 9:00:00 AM
- #2Jun 29, 2026, 9:15:00 AM
- #3Jun 29, 2026, 9:30:00 AM
- #4Jun 29, 2026, 9:45:00 AM
- #5Jun 29, 2026, 10:00:00 AM
- #6Jun 29, 2026, 10:15:00 AM
- #7Jun 29, 2026, 10:30:00 AM
- #8Jun 29, 2026, 10:45:00 AM
- #9Jun 29, 2026, 11:00:00 AM
- #10Jun 29, 2026, 11:15:00 AM
Sobre esta herramienta
Validate cron expressions, see a plain-English breakdown of each field, and preview the next runs in any timezone. The right tool for sanity-checking a crontab line, learning what an unfamiliar cron means, or scheduling a recurring job with confidence.
Privvert computes the next runs locally - no server round-trip. Pick a timezone (your local zone, UTC, or any IANA zone like Europe/Copenhagen) to see when the cron will fire there.
Cron expressions are five (or six, with seconds) fields - minute, hour, day-of-month, month, day-of-week - separated by spaces. Each field supports wildcards (*), lists (1,15,30), ranges (1-5), steps (*/15), and special tokens (@daily, @weekly). Privvert parses your expression, validates each field, and shows the next 10 execution times in your local timezone so you can see at a glance whether '0 0 * * 1' really means what you think.
Características
- Standard 5-field cron parsing
- Per-field plain-English breakdown
- Next N runs in your chosen timezone
- IANA timezone selector
- Quick preset chips (every minute, hourly, daily, weekly, monthly, yearly)
- Inline error messages for invalid expressions
- Browser-only - runs locally
Cómo usarla
- Paste a cron expression, or pick a preset.
- Pick the timezone.
- Read the next runs and the per-field breakdown.
Todo sucede dentro de tu navegador usando JavaScript y WebAssembly. Tus archivos nunca se suben a un servidor, nunca se almacenan y nosotros nunca los vemos.
Preguntas frecuentes
No - only the standard 5-field cron form (minute, hour, day-of-month, month, day-of-week) is accepted. 6-field expressions with seconds will be rejected.
Special strings like @reboot and @daily are platform-specific (Vixie cron). Privvert focuses on numeric expressions; convert @daily to '0 0 * * *' yourself.
Common gotchas: confusing day-of-month with day-of-week, server timezone mismatch, and writing 0 0 * * * thinking it's hourly (it's daily at midnight). The plain-English breakdown helps avoid these.
On Vixie cron (most Linux systems), if either is restricted, the other is ignored - the cron fires when EITHER condition matches. This is non-obvious; the breakdown explains your case clearly.
Cron expressions are evaluated in the timezone of the host running them. If your server is UTC and you wrote '0 9 * * *' expecting 9 AM local, the job will run at 9 AM UTC - which is the middle of the night in Asia or before dawn in California. Always pin the timezone explicitly.
Both mean Sunday in standard cron. Day-of-week uses 0-6 (Sunday=0) historically, but most modern cron implementations also accept 7 as Sunday for compatibility with systems that count Monday=1.