| # | Event | Offset | Local time | Chimes | Copy |
|---|---|---|---|---|---|
| {{ r.idx }} | {{ r.label }} | {{ r.offsetDisplay }} | {{ r.local }} | {{ r.chimes }} | |
| No events. Adjust settings above. | |||||
| Field | Value | Copy |
|---|---|---|
| {{ r.label }} | {{ r.value }} | |
| No stats to show. | ||
Meditation sessions are timed periods of attention that benefit from clear openings and gentle cues. A meditation timer with interval bells helps you settle, return to the breath, and finish without checking a clock.
Choose a fixed length or run open ended with periodic chimes. Add a short countdown so you can get into position, then let the bell mark the beginning and the end while you stay with the practice.
You decide how many chimes sound at the start, during intervals, and at the end so every cue is unmistakable. A running progress display and a next event readout keep pacing effortless and reduce the urge to look away.
For extra feedback you can enable a small vibration and a subtle visual pulse when a cue fires. The schedule lists each event with a local time so you can line up sits with your day or share a plan with a group.
Timers support rhythm but do not judge the quality of attention. Very long sessions can drift a little if the device sleeps or a tab is moved to the background.
The timer measures elapsed time during a sit and schedules cue events at defined offsets. The main quantities are the planned session length, the interval length between mid‑session cues, and the number of chimes associated with each cue type.
From these inputs it computes a progress percentage when a fixed session length is set and it produces a complete event schedule. Events are of three kinds: a start cue, zero or more interval cues, and an optional end cue. Each event may play several chimes to make its role clear.
Results present as a tabular schedule with offsets and local times, a running percentage indicator, and a next event string. Local times use the device locale and timezone; offsets remain relative to the planned start.
Comparisons across runs are valid when you keep session length, interval length, and chime counts the same. Displayed times follow whole‑second rounding, so values near boundaries may appear to pause for a second before progressing.
| Symbol | Meaning | Unit/Datatype | Source |
|---|---|---|---|
| s | Planned session length | s | Input |
| i | Interval length between mid‑session cues | s | Input |
| t | Elapsed time since start | s | Derived |
| n | Number of interval events | integer | Derived |
| , , | Chimes at start, interval, and end | integer | Input |
| δ | Trigger tolerance for event firing | 0.0001 s | Constant |
| Field | Type | Min | Max | Step/Pattern | Error Text |
|---|---|---|---|---|---|
| Session length | number (minutes) | 0 | — | step 1 | — |
| Countdown | number (seconds) | 0 | — | step 1 | — |
| Interval | number (minutes) | 0 | — | step 1 | — |
| Start bells | number (count) | 0 | — | step 1 | — |
| Interval bells | number (count) | 0 | — | step 1 | — |
| End bells | number (count) | 0 | — | step 1 | — |
| Audio volume | range (%) | 0 | 100 | step 1 | — |
| Tone frequency | number (Hz) | 100 | — | step 1 | — |
| Tone length | number (ms) | 40 | — | step 10 | — |
| Bell gap | number (ms) | 60 | — | step 10 | — |
| Vibrate / Keep awake / Visual flash | boolean | — | — | — | — |
| Visual flash length | number (ms) | 40 | — | step 10 | — |
| Input | Accepted Families | Output | Encoding/Precision | Rounding |
|---|---|---|---|---|
| Session minutes, countdown seconds, interval minutes | numeric | Offset list with local times | string times via device locale | whole seconds |
| Chime counts and audio options | numeric and boolean | Audible chimes, vibration, visual pulse | device output | durations in ms |
| Schedule/Stats export | — | CSV and JSON | UTF‑8 text | fixed values |
Schedule generation is linear in the number of events. Chime playback is queued using discrete gaps, so extended runs depend on device timers and power policy.
Processing is browser based. No data is transmitted or stored server‑side. Clipboard and file downloads occur only on your explicit action.
Set the session concept and cue pattern to produce a clear, shareable schedule with audible and visual prompts.
You now have a predictable rhythm with clear auditory and visual cues.
No. Everything runs locally. Nothing is sent to a server, and exports are created only when you ask for them.
Clipboard and downloads require a user action.Accuracy is good for typical sessions. Backgrounding, battery saving, or heavy load can introduce delays of a few seconds on some devices.
Session and intervals use minutes. Countdown uses seconds. Offsets and displays use whole seconds with mm:ss or hh:mm:ss formatting.
Yes. Once loaded, it runs without a network connection. Audio and vibration depend on device capabilities.
No payment is required. Use it as often as you like on supported devices.
Ensure device volume is up, silent mode is off, and the page has focus. Some platforms require interaction before allowing audio playback.
Open the schedule view and use the copy option to place a CSV version on the clipboard, or download a file for later.
All planned events have fired for the chosen session length. You can stop to reset or start again with the same settings.
Tip Match interval length to a consistent count of breaths for steadier pacing.
Tip Use a short countdown to settle posture before the first bell.
Tip Increase the end chimes slightly to signal a clear close when sitting in a group.
Tip Lower tone length or raise the gap when using higher chime counts.
Tip Keep the device awake during long sessions to reduce timer throttling.
Tip Preview the schedule and share it to coordinate starts with friends.