Free online tools that run in your browser
Your files never leave your device · No login required · 100% free
Convert, compress, calculate, generate, edit and check files right in your browser — fast, private and easy to use.
Search results
Popular tools
View all toolsBrowse by category
Popular file conversions
View all convertersProgramming
Learn and practise programming in your browser. Pick a language: write code, run it in a real terminal and follow the lessons step by step.
Why Shiklo Tools?
Simple, private tools that just work — right in your browser.
- Private Everything runs in your browser. Files are never uploaded.
- Secure Encrypted HTTPS connection, and nothing you open is stored on our servers.
- No login required No account, no sign-up, no email. Just open a tool and use it.
- Fast No upload or download wait — results appear instantly.
- Free All tools are free to use, with no limits.
- Works everywhere Phone, tablet or computer, in any modern browser.
🆕 New tools
★ Popular tools
Recently used
Frequently asked questions
Are my files or text uploaded anywhere?
No. Every tool runs inside your browser on your own device. Nothing you enter or open is sent to a server.
Do I need to create an account or log in?
No login is required. There are no accounts — open any tool and start using it straight away.
Are the tools really free?
Yes. All tools are free, with no limits or watermarks. The site is supported by ads.
Does it work on my phone?
Yes. The tools work in any modern browser on phones, tablets and computers.
Can I use the tools offline?
Once a tool has loaded it does its work on your device, so it keeps working even if your connection drops.
Which file types are supported?
PDF, Word, Excel, PowerPoint, OpenDocument and RTF documents, JPG, PNG, WebP, HEIC, AVIF, GIF and BMP images, MP4, MOV, WebM and MKV videos, MP3, WAV, M4A, OGG and FLAC audio, ZIP, 7z, RAR, TAR and GZIP archives, CSV, JSON, XML and plain text. Each tool lists exactly what it opens.
All tools with descriptions →
Cron Expression Generator
Build or paste a cron expression, read it in plain English, and see the next 10 run times in any time zone. Crontab, GitHub Actions, Kubernetes.
Cron expressions are short but cryptic: is 0 9 * * 1-5 nine in the morning on weekdays, or something else? The Cron Expression Generator answers that instantly. Pick a common schedule, use the pickers for each field, or paste an expression you found in a config file, and the tool explains it in plain English and lists the next 10 times it will run.
The run times are shown in any time zone you choose, with daylight-saving changes taken into account, so you can see exactly when a job will fire on a server in UTC or a cluster in another country. Each field is checked with a clear message, and ready-to-paste snippets are provided for crontab, GitHub Actions and Kubernetes CronJobs. Everything runs in your browser.
How to use Cron Expression Generator
- Click a preset such as “Weekdays at 9:00”, or type or paste a cron expression.
- Fine-tune minute, hour, day of month, month and day of week with the field pickers.
- Read the plain-English description and fix any field marked as an error.
- Choose the time zone to see the next 10 runs, then copy the expression or a snippet.
Features
- 11 presets for the most common schedules.
- A picker and a text box for each of the 5 fields, kept in sync with the expression.
- Plain-English explanation of any expression.
- Next 10 run times in any time zone, with the UTC offset and how long until each run.
- Daylight-saving aware: times skipped when clocks go forward are reported.
- Optional seconds field (6 fields) for schedulers such as Spring and node-cron.
- Macros: @yearly, @annually, @monthly, @weekly, @daily, @midnight and @hourly.
- Names for months and days (JAN–DEC, SUN–SAT); 0 and 7 both mean Sunday.
- Copy-ready snippets for crontab, GitHub Actions and Kubernetes.
The five cron fields
A standard cron expression has five fields separated by spaces. Each field says when the job may run; the job runs at every moment that matches all of them. An asterisk means every value.
| Position | Field | Allowed values |
|---|---|---|
| 1 | Minute | 0–59 |
| 2 | Hour | 0–23 (0 is midnight) |
| 3 | Day of month | 1–31 |
| 4 | Month | 1–12 or JAN–DEC |
| 5 | Day of week | 0–7 or SUN–SAT (0 and 7 are Sunday) |
Special characters
Four characters let one field describe many values. They can be combined, for example 0-30/10 means minutes 0, 10, 20 and 30.
| Character | Meaning | Example |
|---|---|---|
| * | Every value | * in the hour field: every hour |
| , | A list of values | 1,15 in day of month: the 1st and the 15th |
| - | A range | 1-5 in day of week: Monday to Friday |
| / | A step | */15 in minute: every 15 minutes (0, 15, 30, 45) |
Common cron examples
These schedules cover most jobs. Click the matching preset to load one and see its next runs.
| Expression | Runs |
|---|---|
| * * * * * | Every minute |
| */5 * * * * | Every 5 minutes |
| 0 * * * * | At the start of every hour |
| 0 0 * * * | Every day at midnight |
| 0 9 * * 1-5 | At 09:00, Monday to Friday |
| 0 0 * * 0 | Every Sunday at midnight |
| 0 0 1 * * | At midnight on the 1st of every month |
| 0 0 1 */3 * | On the 1st of January, April, July and October |
| 30 2 * * 6 | At 02:30 every Saturday |
Day of month and day of week together
When both day fields are restricted, classic cron runs the job on days that match either of them, not both. So 0 0 13 * 5 runs at midnight on every 13th of the month and also on every Friday, not only on Friday the 13th. If either field starts with an asterisk, a day must match both, so a plain asterisk simply leaves the choice to the other field, while 0 0 */2 * 1 means Mondays that fall on an odd-numbered day. The next-run list follows this rule, so you can check the result before deploying.
Time zones and daylight saving
Cron runs in the time zone of the machine or service that runs it. Most servers, GitHub Actions and many cloud schedulers use UTC, while a laptop uses local time. Choose the zone here to see the real run times. In zones with daylight saving, a time like 02:30 does not exist on the night the clocks go forward, so that run is skipped and the tool tells you; on the night the clocks go back, 01:30 happens twice and the job runs once. To avoid surprises, schedule important jobs outside the hours of 01:00 to 03:00, or use UTC.
Seconds and other cron dialects
Linux crontab, GitHub Actions and Kubernetes use the five fields above. Some schedulers, such as Spring's @Scheduled and node-cron, add a seconds field at the start, making six fields; turn on Seconds field to build those. Quartz and AWS EventBridge use their own variations (for example a year field, ? and L, or 1–7 for the days of the week starting on Sunday), so check their documentation before copying an expression across.
Frequently asked questions
What does * * * * * mean?
Every minute of every hour of every day. Each asterisk means every value of its field: minute, hour, day of month, month and day of week.
How do I run a cron job every 5 minutes?
Use */5 * * * *. The step */5 in the minute field matches minutes 0, 5, 10 and so on up to 55.
How do I run a job on weekdays only?
Put 1-5 in the day-of-week field, for example 0 9 * * 1-5 runs at 09:00 from Monday to Friday.
Which time zone does cron use?
The time zone of the system that runs it. Servers and GitHub Actions usually use UTC. Choose the zone in the tool to see the actual run times there.
Why does my expression never run?
The day and month fields can describe a date that does not exist, such as 0 0 30 2 * (30 February). The tool tells you when a schedule never runs.
Is 0 or 7 Sunday?
Both. In standard cron, 0 and 7 both mean Sunday, and you can also write SUN.
Can I use a seconds field?
Yes. Turn on Seconds field, or paste a 6-field expression, for schedulers like Spring and node-cron. Standard crontab, GitHub Actions and Kubernetes do not support seconds.
Is my data sent anywhere?
No. The expression is parsed and explained in your browser, and nothing is uploaded or stored.