Intermittent Fasting Calculator

Plan your eating and fasting windows for the day.

Enter an eating-start time and choose a protocol.

How this intermittent fasting calculator works

An intermittent fasting calculator turns a daily eating-start time and a Protocol into an eating window and a fasting-end time. Choose 16:8 (default), 14:10, 18:6, 20:4, or OMAD (23:1). Enter Start eating (hours) (0–23) and Start eating (minutes) (0–59). The headline is eat-start–eat-end as HH:MM–HH:MM.

Both start Hours and Minutes must be filled. Either empty shows Enter an eating-start time and choose a protocol. The eating window starts at that clock time. Fasting ends when the fast hours after the eating window wrap around 24 hours.

How to use the intermittent fasting calculator

  1. Enter Start eating (hours) (0–23) and Start eating (minutes) (0–59). Both fields are required. Midnight is 0/0.
  2. Choose Protocol: 16:8, 14:10, 18:6, 20:4, or OMAD (23:1). The first number is fasting hours; the second is eating hours.
  3. Optional: open Custom protocol and enter Fasting hours and Eating hours that add up to exactly 24. The on-form hint is Custom hours must add up to 24 to replace the selected protocol.
  4. Read Eating window (the headline) and Fasting ends. Times wrap past midnight.

Custom protocol

The Advanced trigger is labelled Custom protocol — the same GPA contract as other calculators on this site. Closed, the selected Protocol is used even if custom hours stay typed. Open custom applies only when both Fasting hours and Eating hours are greater than 0 and sum to exactly 24. Open empty, 0, or 15 + 8 = 23 still uses the preset. Closing the section is an opt-out back to the preset.

Window formulas

Eating hours and fasting hours always total 24 on a successful custom split. Clock math uses minutes in a 1440-minute day.

Eating window end
eat end=eat start+eat hours
When fasting ends
fast end=eat end+fast hours

Times wrap with modulo 1440 minutes. 16:8 from 12:00 ends eating at 20:00 and ends fasting at 12:00 the next day.

Worked examples

Example: 12:00, protocol 16:8

Eating hours are 8, so the window is 12:00–20:00. Fasting hours are 16, so Fasting ends is 12:00 the next day. The headline is 12:00–20:00.

Example: 18:00, OMAD (23:1)

One eating hour makes 18:00–19:00. Fasting ends at 18:00 the next day.

Example: Custom protocol open, 15 fasting + 9 eating, start 08:00

15 + 9 = 24, so the custom split replaces 16:8. The window is 08:00–17:00 and Fasting ends is 08:00. Close Custom protocol and the preset 16:8 returns even if 15 and 9 stay typed. Open with 15 + 8 = 23 still uses the preset.

Things to keep in mind

This is a clock schedule, not a nutrition plan. Real digestion, sleep, and daily life vary. Intermittent fasting is not suitable for everyone — speak to a clinician if you have a medical condition, are pregnant, or take medications timed to meals.

Intermittent fasting calculator FAQ

Which fields are required?

Start eating (hours) and Start eating (minutes) must both be filled (0–23 and 0–59). Either empty shows Enter an eating-start time and choose a protocol. A Protocol is always selected (default 16:8).

What happens when I close Custom protocol?

Custom hours are unused even if they stay typed — the same GPA contract as other calculators on this site. The selected Protocol (16:8, 14:10, 18:6, 20:4, or OMAD) is used instead.

When do custom hours replace the protocol?

Only while Custom protocol is open, both Fasting hours and Eating hours are greater than 0, and they sum to exactly 24. Open 15 + 8 = 23 still uses the preset.

Does the eating window wrap past midnight?

Yes. Eat end and Fasting ends use modulo 1440 minutes, so a late start can finish the next calendar morning.

What does OMAD (23:1) mean here?

23 fasting hours and 1 eating hour. From 18:00 the window is 18:00–19:00 and Fasting ends at 18:00 the next day.

Does this intermittent fasting calculator store my numbers?

Completed results can be saved in this browser’s local history so you can reopen them later. They stay on your device and are not sent to our servers or to analytics.