Intermittent Fasting Window Calculator

Meal timing and fasting patterns reveal health information

The fact that someone practices intermittent fasting, and which protocol they follow (16:8, OMAD, Extended), says something about their health intentions and potentially their medical context. OMAD practitioners, for example, overlap with populations at elevated eating-disorder risk — a detail that insurers, employers, and health-data brokers have monetised in documented cases.

Meal timestamps are also behavioural data. ‘This user ends eating at 20:00 every day’ is a persistent lifestyle signal. Health and fitness apps accumulate that pattern under a user account, where it can be combined with location data, heart rate logs, and other signals to build a detailed health profile.

What health apps do with your fasting and meal data

Most dedicated fasting trackers require account creation and log meal times, fasting windows, and protocol choices to a server. That data has appeared in third-party health data broker marketplaces and has been used to inform insurance pricing in several jurisdictions. Broad health-app terms of service frequently permit sharing aggregated or de-identified data with partners — with de-identification that has repeatedly been reversed.

The protocol choice itself (is this person doing OMAD or 16:8?) is a high-value signal for dietary supplement, weight-loss, and health insurance advertisers. None of that inference can happen if the data never leaves your device.

Pure clock arithmetic, running only in your browser

The tool takes a last-meal time and a protocol’s fast duration and eating-window duration, then uses JavaScript Date arithmetic to compute the fast-end and next-fast-start times. Midnight wrap-around (e.g. last meal at 21:00 → fast ends 13:00 next day) is handled by plain date addition. The 24-hour heat-map is CSS and array arithmetic — no external API.

Open DevTools Network and make a change: you will see zero additional requests. The time you enter for your last meal never crosses the network.

Before and during fasting: what to keep in mind

This tool computes times only — it is not medical advice. Extended 36-hour fasts, and any fasting done by someone with a chronic condition or on medication, should be discussed with a physician first. OMAD especially risks inadequate caloric intake if not carefully planned.

The computed window is a guideline based on the protocol’s nominal hours. Individual metabolism, sleep pattern, and stress levels all affect the optimal window for any given person. Use the result as a starting point and adjust to how you feel.

Mealtime arithmetic and midnight wrap-around

Meal-time arithmetic in 24-hour notation frequently crosses midnight (21:00 last meal + 16 hours fasted = 13:00 the next day). A naive (hour * 60 + minute + duration) % 1440 gives minute precision but loses the date progression. This tool starts from a Date object’s getTime() value, adds duration * 3600000 ms, then formats with toLocaleTimeString. That handles both day boundaries and DST transitions in zones outside Asia/Tokyo, where the spring forward / fall back jump otherwise misplaces the result by an hour.

The 24-hour heat-map is an array operation over 24 one-hour cells labelled “fasting” or “eating.” When the eating window crosses midnight (an OMAD 19:00-20:00 followed by a 23-hour fast) the array wraps around. The Intl.DateTimeFormat option hour: 'numeric' automatically switches between 12-hour and 24-hour display by locale — ja and de default to 24-hour, en-US defaults to 12-hour with AM/PM. This tool follows the browser locale rather than imposing one format.

Research background and regional practice patterns

Common intermittent fasting protocols (16:8 Leangains, 18:6, 20:4 Warrior, OMAD = 23:1, 5:2, Alternate Day Fasting) come from different research lineages. 16:8 was popularised by Martin Berkhan in 2010, drawing on earlier Ramadan-window studies. OMAD revives a documented Roman soldier practice. 5:2 reached a mainstream audience with Michael Mosley’s 2013 book and includes two “modified-fast” days of 500–600 kcal rather than a complete fast. This tool computes only the time window — calorie management still has to happen separately.

Ramadan fasting (sunrise to sunset during the 9th month of the Islamic calendar) varies widely by latitude. In the Arctic Circle, summer Ramadan can stretch to 18–22 hours; religious authorities accept following Mecca time or the nearest Muslim-majority country’s schedule as an alternative. Medical guidance across jurisdictions cautions against extended fasts (over 24 hours) for people with chronic conditions like diabetes or a history of disordered eating, and pregnant women, breastfeeding mothers, and children in growth phases are typically advised against intermittent fasting entirely. This tool is a time calculator — medical decisions belong with a clinician. To design the fasting and sleep windows together in one daily rhythm, sleep-cycle-calc is the companion piece; for a live ticker counting down to your fast-end time, countdown renders the same moment as a visible clock; and to record the resulting fast length as an ISO 8601 PT16H value for journalling, duration-format keeps the data local too.