How long does postdrome usually last?

Across a population, postdrome commonly runs anywhere from a few hours to a couple of days. That range is accurate but nearly useless for planning your own week, because your personal after-phase tends to cluster much tighter than the population spread. Your real number only shows up once you've tracked enough of your own attacks past pain resolution.

Why is my postdrome duration so unpredictable?

It usually isn't as random as it feels. Once you log the after-phase across twenty to thirty attacks, most people find their duration clusters against a few specific variables: attack severity, which rescue medication class you used, hormonal phase, and how much sleep debt you were carrying. The unpredictability is mostly missing data, not genuine randomness.

Can you actually predict how long postdrome will last?

Not from a population statistic, and not for a first-ever attack. But from your own tracked history you can build a personal distribution that's tight enough to plan a recovery window around, for example knowing that a triptan-aborted attack tends to leave you functional within a day while an untreated one runs longer.

Does postdrome count toward migraine disability scores like MIDAS?

It should. MIDAS and HIT-6 ask about days your activity was limited and how much headache affects daily functioning, which includes fog, residual photophobia, and reduced-capacity days in the after-phase. If your tracker stops at pain resolution, those days go uncounted and your disability score can come in systematically low, weakening your treatment case. MIDAS asks five questions covering the past 3 months and produces a disability grade (I through IV) based on the total days lost or impaired across work, school, housework, and social activities, Grade IV being the threshold most commonly cited in insurance prior-auth and disability documentation. HIT-6 is a complementary six-question instrument with a shorter recall window focused on recent weeks, scoring headache impact on a scale from little-or-no to severe; the two tools are designed to work together, with MIDAS capturing cumulative disability and HIT-6 capturing current functional impact.

How many attacks do I need to track before I see my pattern?

Our working sense is somewhere in the twenty-to-thirty range before a personal postdrome distribution stabilizes enough to plan on, though that's a pattern we're still confirming against aggregate data rather than a settled figure. The key is logging the after-phase, not just the headache, so the duration is in the record at all.

Your postdrome duration is predictable, if you're tracking it

Article · 4 min read

Your postdrome duration is predictable, if you're the one tracking it.

Every authority answers 'how long does postdrome last' with a population range. Your real number is tighter, personal, and hiding in your own attack log.

Six hours to several days tells you nothing about Tuesday

"Six hours to several days." That's the answer nearly every major source hands you when you ask how long postdrome lasts. It's accurate. It's also useless the second you're staring at Tuesday's calendar trying to decide whether to keep the meeting or move it before the fog has even lifted.

A range that wide isn't a forecast. It's a shrug with a citation attached.

The gap between six hours and three days is the entire difference between "fine by lunch" and "write off the week." And that's the one distinction the published number refuses to make for you.

Your postdrome has a number, and it isn't the average

The published range is clinically correct and personally worthless at the same time. Postdrome duration across a whole population genuinely does span that wide. But you aren't a population. Your after-phase has a characteristic length, and for most people it clusters far tighter than the textbook spread suggests.

The number was never unknowable. It's just that it lives in exactly one dataset, and that dataset is yours. Twenty or thirty attacks with the after-phase actually recorded, and the shrug turns into a distribution you can plan against.

Your postdrome has a number. It just isn't the average, and it's only in your own data.

Why every authority gives you the same useless answer

Every authority answers a personal question with a population statistic. Mayo Clinic Connect, the American Migraine Foundation, WebMD, Buoy Health, the r/migraine thread you found at 2am. All correct, all citing roughly the same span, all treating "how long does postdrome last" as if there's a single answer that fits everyone.

There isn't. Asking a population range to predict your Tuesday is like asking your city's average commute time to tell you when you'll get to work. Technically related. Practically no help. The range is doing exactly the job it was built for, which is describing everyone at once. It was never built to forecast one person's week.

The population range is not a planning tool

"6 hours to several days" is the honest summary of everyone's postdrome at once. It is not a prediction of yours. Treating it as one is how you cancel weeks you'd have been fine for, or commit to days you weren't. A population average describes everyone at once; it can't forecast one person's week.

What your tracked postdrome actually clusters against

Longitudinal tracking turns the shrug into a distribution you own. Once you have twenty or thirty logged attacks with the after-phase recorded, the question changes. Not "how long does postdrome last" anymore, but "what does my postdrome cluster with."

Four variables tend to carry most of the signal. Your specific mix is yours, but the point is that it's discoverable at all. A wide-looking spread usually turns out to be a few tight clusters stacked on top of each other, and once you can see the clusters, you can plan around them.

The four dimensions personal postdrome duration most often clusters against. Your mix is specific to you; the point is that it's recoverable from your own log.
Dimension	What tight clustering looks like	What it buys you
Attack severity	Severe attacks reliably run longer after-phases than mild ones	You can forecast the tail from the peak
Rescue medication class	Triptan-aborted, gepant-treated, and untreated attacks recover on different timelines	Medication choice becomes a recovery-time decision, not only a pain decision
Hormonal phase	Perimenstrual-window attacks trail longer postdromes	Those weeks get planned around instead of pushed through
Sleep debt	Attacks on short-sleep nights carry heavier, longer fog tails	Protecting sleep becomes visibly load-bearing, not just advice

How the pattern shows up after two months of logging

Say your log fills in over two months. The pattern that surfaces: triptan-aborted attacks leave you foggy for about a day, but the ones you ride out without rescue meds run closer to two and a half. Severity barely moves your number. Medication timing moves it a lot.

That's not a fact any published range could have handed you. And now Tuesday looks different. You took a triptan early Sunday, so by your own distribution you're likely functional Monday afternoon and solid by Tuesday. You keep the meeting. Six months ago you'd have cancelled it on a guess and spent the recovered day wondering whether you'd needed to.

Your postdrome is quietly deflating your MIDAS score

Your calendar isn't the only thing an undercounted postdrome distorts. Your chart is too.

MIDAS and HIT-6, the two disability instruments your neurologist scores you on, are implicitly asking about postdrome cost. MIDAS counts the days your activity was limited over the recall window. HIT-6 asks how much headache affects your daily functioning. Neither says "count only the hours you were actually in pain." But that's exactly what gets recorded if your tracker closes the attack at pain resolution.

The fog day, the day you worked at 40 percent, the residual photophobia that ate your focus: those are disability days the instrument wants counted. If you never logged them, your score comes in low. Systematically low. And your treatment case, the argument for the next preventive or the CGRP appeal, gets built on an undercount. MIDAS uses a 3-month recall interval across its five questions, selected to balance accuracy of self-reported disability information. ([source](https://www.researchgate.net/publication/12039031_Development_and_testing_of_the_Migraine_Disability_Assessment_MIDAS_Questionnaire_to_assess_headache-related_disability))

Why most trackers can't give you your number

Most trackers close the attack when the pain stops. That's the quiet design decision that throws away your postdrome data, and with it your number. If the timeline stops at pain resolution, the after-phase was never in the file to cluster.

Postdrome keeps the timeline running through the after-phase: residual photophobia, neck stiffness, brain fog, mood, logged as the continuous symptom trail it actually is. This isn't about logging more for its own sake. Your duration only lives in the record if something kept recording after the headache let go. Aura Mode exists for the same reason. The days you most need to log are the days you can't stand a bright screen, so the interface adapts instead of asking you to squint through it.

What we're still trying to pin down

The open question we keep circling: how few logged attacks it takes before a personal postdrome distribution stabilizes enough to plan on. Our working sense is somewhere in the twenty-to-thirty range, but that's a pattern we want the aggregate data to confirm, not a number we'll pretend is settled. When it firms up, the honest version of "how long will this one last" stops being a range at all. It becomes your range.

Keep your own timeline running past the headache and let your real postdrome number surface from your own attacks. One-time purchase, no subscription, your data stays on your device.

Postdrome is built around the after-phase instead of ending at pain resolution, which is the whole point: your duration number only exists if the timeline kept running past the headache. Lifetime pricing, stated up front. On-device and exportable, so the dataset that holds your number stays yours.

Get Postdrome