UUID Studio

UUID Studio

Cron Parser

Understand cron schedule fields.

  • đź”’ No data stored or uploaded
  • ⚡ 100% client-side
  • 🆓 Free, no account
Click Convert when ready

Override only when Auto cannot parse your paste. Changing this loads a matching sample into Input — click Convert to run. Use Load sample to cycle every format example.

All conversions

Read-only representations of the same 16 bytes. Every textual form is listed here, not in “Prefer format”.

Paste two values: if both sides are valid JSON, a structural diff appears; otherwise UUID / bytes are compared when both decode to the same format.

A
B

Create or edit JSON here (syntax colors), then format, validate, or convert - same as MongoDB $binary UUID blobs on the Convert tab once detected.

New document

Hash, HMAC, AES-GCM/CBC + RSA-OAEP, codecs, JWT decoding, UUID v4, and secure random - all client-side. JWTs use Base64URL (three segments), not a single MIME Base64 block - use Decode JWT below, not raw Base64 decode.

Examples

  • Every 5 minutes 
    */5 * * * *

About Cron Parser

Cron syntax is dense enough that even experienced engineers have shipped a schedule that runs every minute instead of every hour because of one misplaced asterisk.

Paste a 5- or 6-field cron expression and get a human-readable description of when it actually fires. Treat it as a sanity check, though - always confirm the final schedule against your actual scheduler (cron, Kubernetes CronJob, AWS EventBridge), since implementations vary slightly.