Bedtimes (or wake times) aligned to 90-minute cycles.
Each cycle is ~90 min. The calculator adds ~14 min to fall asleep. Aim for 5–6 cycles for full restoration.
Waking up groggy after eight hours and bouncing out of bed after six is one of those everyday paradoxes that has a tidy explanation: humans sleep in repeating cycles of roughly ninety minutes, each cycle moving from light sleep through deep sleep to REM and back to light. The least disorienting time to wake up is during the light phase at the start or end of a cycle, not in the middle of deep sleep when an alarm clock yanks you out of slow-wave activity and your brain takes thirty minutes to catch up. Most people also need a buffer of about ten to fifteen minutes to actually fall asleep after their head hits the pillow, which spreadsheets and ad-hoc bedtime math forget. This calculator takes a desired wake time (or a planned bedtime) and computes the four most reasonable bedtimes (or wake times) that align to 90-minute cycle boundaries while accounting for the time it takes to fall asleep. The output is four candidate times rather than one because the right number of cycles depends on how rested you need to be: 4 cycles (six hours) for a single short night you can recover from, 5 cycles (7.5 hours) for a typical good night, 6 cycles (nine hours) when you are sleep-deprived or recovering from illness.
The arithmetic is simple but worth being explicit about. From a wake time T: bedtime = T − (n × 90 min) − 14 min, for n in {3, 4, 5, 6}. The fourteen-minute buffer is the median time to sleep onset reported in adult sleep studies; it is shorter for tired people and longer for people lying in bed checking their phones. From a bedtime T: wake time = T + (n × 90 min) + 14 min, for the same n. The cycle length of ninety minutes is itself an average — individual cycles range from about seventy-five to a hundred and twenty minutes, and they tend to lengthen as the night progresses (the first cycle is shorter and deeper, the last cycle is longer and richer in REM). This is why people report better dreams in the second half of the night even though their total time asleep does not change. The calculator picks 90 as the central reference value, which gives a good first approximation; users who track their sleep with a wearable can refine the number by averaging their device's per-cycle measurements over a couple of weeks.
Two inputs: a direction toggle ("I want to wake up at…" or "I will go to bed at…") and an hour:minute pair representing the anchor time. The defaults are a 7:00 wake-up. The result panel shows four cards, one for each of 3, 4, 5, and 6 sleep cycles, with the corresponding bedtime (or wake time), the number of cycles, and the equivalent number of hours of sleep. Cards earlier in the night give fewer cycles and less restorative sleep; cards later give more. The four-card layout is deliberate: rather than presenting one "correct" answer, it lets the user pick the trade-off appropriate to the night ahead.
You want to wake up at 7:00 AM. Subtracting fourteen minutes for sleep onset, the latest plausible bedtime is 6:46 AM minus n cycles. For 6 cycles (nine hours): 6:46 − 9:00 = 9:46 PM the night before. For 5 cycles (7.5 hours): 6:46 − 7:30 = 11:16 PM. For 4 cycles (six hours): 6:46 − 6:00 = 12:46 AM. For 3 cycles (4.5 hours): 6:46 − 4:30 = 2:16 AM. A teen who is consistently struggling to wake up at 7 AM after going to bed around 11:30 PM is sleeping inside a cycle, not at its boundary — pushing bedtime to 11:16 PM (5 cycles) is a small change with an outsized effect on morning alertness. Reverse the direction: if you go to bed at 11:00 PM, then with the fourteen-minute buffer you fall asleep at 11:14 PM, and the four candidate wake times are 4:14 AM (3 cycles), 5:44 AM (4 cycles), 7:14 AM (5 cycles), 8:44 AM (6 cycles). The 7:14 AM and 8:44 AM marks are the two least-painful options for a typical adult.
First, treating the ninety-minute number as universal. It is an average; your cycle could be eighty or a hundred minutes. If a wearable device tells you your average is 95 minutes, recompute by hand with that figure (or use the device's own "smart wake" feature, which accounts for it). Second, ignoring chronotype. Morning chronotypes ("larks") wake easily even mid-cycle; evening chronotypes ("owls") suffer disproportionately from off-cycle alarms. The calculator helps everyone but helps owls more. Third, optimising bedtime cycles while keeping caffeine, alcohol, and screen-light habits unchanged. Cycle alignment buys you maybe fifteen minutes of perceived alertness; a stable circadian rhythm buys you several times that. Fourth, applying the 90-minute model to babies and young children — their cycles are shorter, around fifty to sixty minutes, and they have far more REM. Fifth, using cycle math to justify chronic short sleep. Three cycles is 4.5 hours, which the calculator will obediently compute, but that is sleep deprivation, not optimisation; do not confuse "this is the least bad short sleep" with "this is enough sleep."
The ninety-minute cycle was first identified by William Dement and Nathaniel Kleitman in the 1950s using EEG recordings; the modern refinement, including the slow-wave sleep / REM split, has been mapped in detail by sleep labs around the world since. Polyphasic sleep schedules (Uberman, Everyman) attempt to shorten total sleep by clustering short naps strategically; the scientific consensus is that they degrade cognitive performance regardless of how many cycles they preserve. Circadian rhythm is a separate, slower (twenty-four-hour) cycle that controls when you can sleep efficiently; cycle math controls how you sleep within a given window. Wearables (Oura, Whoop, Apple Watch, Fitbit) estimate per-cycle stages from heart-rate variability and movement; their accuracy is moderate (correlation with polysomnography is around 0.6 to 0.8) but enough to refine the 90-minute default. Smart-alarm apps (Sleep Cycle, Pillow) use the same arithmetic and add a sound-and-motion sensor to wake you within a 30-minute window aligned to a light phase. The underlying calculation in all of those is the simple add-or-subtract that this calculator exposes directly, without the device.