Postdrome fatigue and postdrome brain fog aren't the same symptom, and your neurologist needs to know which one you have

Article ยท 4 min read

Brain fog is a bucket, and your neurologist can't treat a bucket.

Word-finding failure and exhaustion get logged as one 'brain fog' tag. Splitting them shows a neurologist whether a preventive fixed your thinking or only your pain.

The word that won't come back

The headache broke last night. By mid-afternoon you're typing an email to your manager, and halfway through a sentence the next word simply isn't there. You know its shape. You know it starts with a p. You delete the sentence, start over, and lose it again.

Then you reread the paragraph above it. Twice. Three times, because none of it is landing.

You aren't sleepy. You could stand up and walk around the block if you had to. What you can't do is think in a straight line, and when you open your tracker that evening, the only box that fits is the one labeled brain fog. So you tap it, maybe add "tired," and close the app.

That entry is honest. It's also close to useless for the person deciding whether your preventive is working.

Brain fog is a bucket, not a symptom

We call it the Bucket Problem. "Brain fog" has become the catch-all for whatever goes wrong in your head after the pain lifts, and it swallows at least two different things.

One is cognitive postdrome: word-retrieval gaps, processing lag, the inability to hold a thought long enough to act on it. The other is postdrome fatigue: heaviness, exhaustion, a sleep drive that drags at you mid-afternoon.

They feel adjacent. Both flatten the day after. But they break down in different ways, and a log that pours both into one bucket can't tell anyone which one is still hanging around on day two, which one a new medication touched, or whether it touched either.

Why "tired" hides the signal

Most migraine trackers are built around the attack. Start time, peak pain, medication taken, end time. Whatever follows usually gets a single tag at best, and brain fog is the tag on offer.

Patients collapse it too, for understandable reasons. Describing a cognitive symptom takes exactly the kind of effort you don't have while you're in it. "Tired" is one word. "Lost nouns mid-sentence until mid-afternoon and missed the exit on a drive I do every week" is a paragraph, and nobody writes paragraphs the day after an attack.

So the record flattens. And a flattened record invites the easy read: a clinician sees "tired" and hears ordinary post-attack exhaustion, the kind anyone would expect after a bad night. Cognitive failure that lingers through most of a day looks, on paper, exactly like needing a nap.

A log that says "tired" can't tell a neurologist which part of you the medication fixed.

What AMF says, and what patients keep describing

The American Migraine Foundation's postdrome material describes cognitive symptoms, the fog, the word-finding trouble, the slowed thinking, as something separate from fatigue, not just tiredness wearing a different name. How long it lingers isn't the headline here. What matters is that the site treats it as its own thing, not a subset of being tired.

The research literature draws the same line. Giffin and colleagues' 2016 electronic diary study of the migraine postdrome, published in Neurology, recorded tiredness and difficulty concentrating as separate symptoms rather than one blended complaint.

The patient side matches if you read closely. On r/migraine, people describing the day after rarely say "I had brain fog" and stop there. They describe the functional failure: the word that vanished, the page read over and over, the conversation they couldn't follow. The distinction already lives in how people talk about it. It just disappears somewhere between the experience and the log.

Cognitive postdromePostdrome fatigue
What failsOutput: finding words, processing what you read or hear, holding a thoughtEnergy: stamina, staying upright, staying awake
What it looks likeLosing a word mid-sentence, rereading the same paragraph, missing a turn on a familiar driveHeavy limbs, needing to lie down, sleep pulling at you in the afternoon
The vague log entry"Brain fog""Tired"
A log a clinician can compare"Word-finding gaps through the afternoon. Couldn't finish an email. Cleared by evening.""Napped after lunch. Couldn't stay on my feet through dinner. Better next morning."
Functional anchors for the two postdrome categories AMF distinguishes. The bottom row is example log language, not clinical criteria.

The pattern in practice: one patient, two logs

Take a hypothetical patient three months into a CGRP preventive. Their attacks are shorter and less frequent. Every attack, before the medication and after, carries the same postdrome entry: brain fog, tired.

At follow-up, the neurologist sees fewer headache days and shorter attacks. Good response. Continue.

Now split those same three months into two tracks. The fatigue line has shrunk: they used to lose the whole next day to the couch, and now it's an early night. The cognitive line hasn't moved. Words still drop out through the following afternoon, every time, and they still reread emails before sending because they don't trust what they wrote.

That second version is a different clinical conversation. Pain is better. Energy is better. Thinking isn't. A preventive that shortens the headache but leaves someone unable to draft an email for 18 hours is an incomplete response, and only the split log makes that visible.

The reverse shows up too. Cognition clears fast on a new medication while exhaustion drags on, and that's a separate question worth raising, about sleep or about what the medication itself might be doing.

What to log instead

If the Bucket Problem is real, the fix is small and specific. Three changes make a postdrome log comparable across treatment periods:

  1. Log cognition and energy as separate entries after every attack, even when one of them is mild. 2. Anchor each one to something you couldn't do. "Lost words mid-sentence," "reread the same paragraph," and "missed a familiar turn" all beat "foggy." 3. Note when each one lifted. Comparing two treatment periods takes end times, and cognitive and physical recovery won't always share one.

That third change carries the most weight. Preventive follow-ups tend to center on headache days. The hours after the headache, where a lot of the lost function lives, rarely make it into the exam room unless you carry them in.

New cognitive symptoms aren't postdrome until a clinician says so

Sudden trouble speaking or understanding speech, confusion, facial droop, or weakness on one side needs emergency care, especially if it's new for you or different from your usual pattern. Don't log it and wait.

Why the timeline keeps running after the pain stops

We built Postdrome because of migraines in our lives, and because the apps we tried stopped recording the moment the pain did. The people we care about kept losing the next day to symptoms nobody wrote down.

So the timeline keeps going through the after-phase. Brain fog and fatigue get logged as separate symptoms instead of one post-attack checkbox, and aura mode keeps entry possible when looking at a screen is its own problem.

Your data stays on your phone, and you can export it before an appointment. That's the whole case for splitting the bucket: a record your neurologist can read side by side, before the preventive and after, with thinking and energy on their own lines.

Start logging the after-phase, with thinking and energy on separate lines.

Postdrome is a migraine tracker built for the hours after the headache: a continuous symptom timeline that keeps recording through the postdrome, separate entries for brain fog and fatigue, aura mode for logging when screens hurt, on-device storage, and an export you can hand to your neurologist. One lifetime price, no subscription.