For weeks, bedtime was almost civilized. Then, overnight, it turned into a wrestling match: your baby arches, screams, rubs their eyes raw, and treats the crib like a personal insult. Naps have become a negotiation. You didn't change anything — so what broke?
Almost certainly nothing. A baby who suddenly starts fighting sleep is usually telling you one of three things: a developmental leap is scrambling their sleep, the nap timing has drifted out of sync with their changing needs, or they've tipped into overtired. None of those mean you've lost their good sleep for good. Let's sort out which one you're dealing with, because the fix is different for each.
What the science says: the three usual suspects
1. A developmental leap (a "sleep regression"). This is the most common reason a good sleeper abruptly revolts. The word "regression" is misleading — nothing is going backward. Your baby's brain just leveled up, and the new skills are crowding out sleep. The National Sleep Foundation notes that temporary sleep disruptions cluster around 4, 6, 8, 12, and 18 months, driven by teething, growth spurts, illness, shifting naps, and milestones like learning to roll, crawl, walk, or talk. A baby too busy practicing a new skill — or newly aware that you exist when you leave the room — fights the very sleep they need. We map each one in sleep regressions by age.
2. A wake-window mismatch. As babies grow, they can stay awake longer, and an old nap schedule quietly stops fitting. If your baby is fighting a nap they used to take happily, the window before it may now be too short (not enough sleep pressure has built up — they're simply not tired yet) or too long (they sailed past the drowsy window into overtired). Both look like "fighting sleep" and have opposite fixes. We cover the rough awake-time ranges and how to read them in wake windows by age.
3. Plain overtiredness. This is the sneaky one, because it's counterintuitive: an overtired baby fights sleep harder, not less. When you blow past the window, cortisol and adrenaline rise and act like a second wind — the frantic crying, back-arching, eyes-screwed-shut routine. The fix isn't to push them to even more tired; it's an earlier next sleep and a calm, dim wind-down.
How to tell which one it is
A little detective work usually cracks it:
- Did it start suddenly, around a known age or a new skill? (Rolling, crawling, pulling up, first words, a tooth coming through.) That points to a regression — hold your routine and ride it out. Most last 2 to 6 weeks.
- Is your baby cheerful and chatty in the crib, playing rather than melting down? That's the classic undertired signal — the sleep pressure isn't there yet. Try a slightly later nap.
- Is your baby frantic, arching, eyes screwed shut, hard to settle? That's overtired — try an earlier next sleep and a calmer wind-down.
- Is there a tooth, a cold, a fever, or obvious pain? Treat that on its own merits before assuming a schedule problem.
The single most useful rule: don't overhaul everything on the first hard night. One or two rough nights is a blip — teething, a leap, a cold. Watch for a pattern over several days before you change the schedule, and resist the urge to bolt on three new sleep crutches you'll have to undo later.
What helps, whatever the cause
A few moves steady the ship regardless of which suspect is behind it:
- Hold your routine consistent. A predictable, calm, dim wind-down is what shortens a regression and reassures a baby in flux. Now is not the moment to reinvent bedtime.
- Nudge the timing, don't blow it up. If it's a window issue, shift the nap 15 to 20 minutes in the right direction for a few days rather than rebuilding the whole day.
- Protect the total, not the battle. What matters across 24 hours is total sleep — per the AASM consensus, 12 to 16 hours for 4–12 months, 11 to 14 for ages 1–2. During a rough patch your baby may temporarily land at the low end; that's expected.
- Try drowsy-but-awake when it's calm. The AAP suggests putting a past-newborn baby down sleepy but not fully asleep, so the middle-of-the-night surfacing is less alarming for them.
- Front-load connection during the day. Especially in the separation-anxiety leaps, lots of daytime closeness and floor practice for new skills means less urgent rehearsing at 2 a.m.
One note on age: if your baby is under about 4 to 6 months, formal sleep training isn't appropriate yet — focus on routine, safe sleep, and reading the cues.
When to call your pediatrician
Sudden sleep-fighting is overwhelmingly developmental and self-limiting. But call your pediatrician if:
- Disrupted sleep drags on much longer than about 6 weeks with no developmental explanation.
- Your baby seems in pain, is pulling at an ear, or has a fever.
- You notice snoring, gasping, mouth-breathing, or pauses in breathing during sleep.
- There's poor weight gain, persistent daytime lethargy, or a baby who seems genuinely unwell rather than just busy and overtired.
- Your own exhaustion has tipped into something heavier — persistent sadness, anxiety, or hopelessness. See perinatal mood, baby blues, and PPD, and don't wait to ask for help.
The reassuring headline: a baby who suddenly fights sleep is almost always a baby who's growing, not one whose sleep is broken. Find the suspect, make one small adjustment, hold the routine, and give it a couple of weeks. If you want to see the pattern instead of guessing, logging naps and wake-ups in the TinyWins app often reveals that the "random" chaos is tracking a new tooth, a new skill, or a window that drifted.
This article is educational and not medical advice. Always check with your pediatrician/provider.