The solutions change as your baby grows. Here's what's most likely going on at each stage, and what actually helps.
Newborns (0–3 months)
At this age, fighting sleep almost always means overstimulation or overtiredness. Newborns have tiny wake windows — 45 to 90 minutes — and the line between 'happily awake' and 'completely overwhelmed' is razor thin. If your newborn is crying and arching their back instead of settling, they've probably been awake too long. Other culprits: gas or reflux discomfort (they may squirm and grunt when laid flat), needing to be held (totally normal — they just spent nine months inside you), or too much noise, light, or activity in the room. The fix is usually simpler than you think: darker room, less stimulation, shorter wake windows, and lots of holding. This isn't a sleep problem — it's a newborn being a newborn.
4–6 months
Welcome to the era of sleep regressions and shifting schedules. The 4-month sleep regression is the big one — your baby's sleep cycles permanently reorganize, and suddenly the baby who fell asleep easily is fighting every single sleep. But regressions aside, the most common cause at this age is getting wake windows wrong. At 4 months your baby needs about 1.5 to 2 hours of awake time; by 6 months it's 2 to 2.5 hours. Too short and they're undertired. Too long and the cortisol kicks in. This is also when nap transitions start — going from 4 naps to 3 can throw everything off for a week or two. If sleep fighting started suddenly, check whether you're in the 4-month regression window. If it's been building gradually, look at your wake windows first.
6–12 months
Now the causes get more interesting. Separation anxiety shows up around 8 to 9 months — your baby has figured out that you exist when you leave the room, and that's terrifying. Motor milestones pile up: sitting, crawling, pulling to stand. Your baby's brain wants to practice these skills instead of sleeping. FOMO is real — they don't want to miss anything. And the 3-to-2 nap transition (typically 7 to 9 months) can create a week or two where no schedule seems to work. The fix depends on the cause. For separation anxiety: short, calm goodbyes and peekaboo during the day. For milestones: extra practice time during waking hours so the novelty wears off. For nap transitions: patience and an earlier bedtime to prevent overtiredness while the new schedule settles.
12–18 months
Independence is the new variable. Your baby is becoming a tiny person with opinions, and one of those opinions is 'I don't want to go to bed.' Walking — or learning to walk — consumes their brain and makes settling down nearly impossible some nights. The 12-month regression often tricks parents into dropping to one nap too early (most babies aren't ready until 14 to 18 months). And if the 2-to-1 nap transition does land in this window, you'll have a few rough weeks where one nap isn't enough but two won't fit. Stick with two naps as long as you can. If they skip a nap, move bedtime earlier. Give them extra active time during the day to burn off that walking energy. And hold your boundaries gently — they're testing, and that's healthy.
18 months–3 years
Toddlers fight sleep for different reasons than babies. Willpower and boundary testing are now front and center — 'one more book,' 'I need water,' 'there's a monster.' Genuine fears can start emerging around age 2. Bedtime stalling becomes an art form. The 18-month regression is often the most intense because it collides with a language explosion and the 2-to-1 nap transition for late transitioners. And between 2.5 and 3 years, many toddlers start dropping the nap entirely, which can cause overtired meltdowns at bedtime. The fix at this age is mostly about structure: a predictable routine, clear boundaries with warmth, limited choices ('do you want the blue pajamas or the green ones?'), and making sure they're getting enough physical activity during the day.
For detailed wake window ranges at every age, see our wake windows by age guide. If your baby's age lines up with a common regression, the sleep regression timeline will help you figure out if that's the driver.