1001Ferramentas
Tools Categories Guides FAQ
About Contact Privacy Policy Terms of Use
⏰Dev

Cron Parser (describe expression)

Paste a cron expression and see in plain text when it will fire (e.g. "every day at 9am" for `0 9 * * *`). Lists the next N runs. Everything in your browser.

In plain English
—

Understand a cron expression

The cron syntax, those five fields like 0 9 * * *, can do a great deal but is undecipherable at first glance. This tool translates the expression into natural language and tells you in plain English when it will fire, something like "every day at 9am".

Beyond the spelled-out explanation, it lists the next runs with concrete dates and times the task would execute. You can check whether the schedule turned out as expected before pushing it to the server. It also helps you track down that stubborn cron that insists on running at the wrong time.

The interpretation runs in the browser. Paste the expression and see right away what it means and when it will happen.

Frequently asked questions

Does it show the next dates the job will run?
No. The page returns a one-line reading of the expression, written in Portuguese: 30 8 1 * * shows up as "às 08:30, no dia 1". There is no next-run calculation and no list of upcoming dates. Time zones stay out of it as well, since that is settled by the server where the crontab lives, and the reading here is literal, field by field. To know the real firing time, cross the result with the TZ set on that machine.
Which field formats does it understand?
Asterisk, a plain number, a hyphen range (1-5), a comma list (1,3,5) and a step (*/15). The expression must carry exactly five space-separated fields, in the order minute, hour, day of month, month and weekday; with four or six an error in red appears and no reading comes out. Left out: three-letter names such as MON-FRI, which print "undefined" where the day belongs, the @daily and @reboot shortcuts, the sixth seconds field from Quartz, and the characters L, W and #.
Why does the sentence sometimes read wrong?
Because the text is assembled from fixed chunks, with no agreement between the article and whatever follows it. The weekday prefix is always "na", so 15 14 * * 0 turns into "às 14:15, na domingo" where Portuguese would want "no domingo", and a range yields "na de segunda a sexta". An hour list gets no special handling either: 0 9,18 * * * comes out as "às 9,18:00". The reading still tells which field is set, but do not read it as polished prose.

Related Tools

⏱

Cron Expression Editor

Parse and build cron expressions with human-readable descriptions, next execution times and shortcuts for common schedules.
⏲️

Cron Generator

Generate cron expressions (5 fields: minute, hour, day, month, weekday) with common presets and natural-language description.
🔑

Authorization Header Parser

Identify the scheme (Basic, Bearer, Digest) of an Authorization header and extract the payload, decoding Basic from base64.
🔗

URL Analyzer

Decompose any URL into its components: protocol, host, pathname, query parameters and hash. Inspect query strings individually.
📦

multipart/form-data Parser

Paste a multipart/form-data body with its boundary and inspect each part (Content-Disposition, filename, Content-Type, size).
🔣

Truth Table

Generate truth tables for Boolean logic expressions. Supports AND, OR, NOT, XOR, NAND and NOR. Auto-detects variables and shows all possible combinations. Processed in the browser.