Desire vs. Fantasy: Knowing the Difference (And Why It Changes Everything)
It took me an embarrassingly long time to work out that the thing I wanted wasn't the thing I was picturing.
For years I had a particular scenario in my head. I won't go into it, partly because it's mine and partly because the specifics would actively mislead you — which is the whole point of this post. I assumed, the way almost everyone does, that the scenario was the want. That if I ever said it out loud and we did it, I'd have gotten the thing.
Then I learned the Somatica framework — Celeste Hirschman and Danielle Harel's fourteen core desires — and found out my core desire is Being Seen. And the scenario I'd been carrying around for a decade suddenly read completely differently. It wasn't a plan. It was a delivery mechanism. My mind had built an elaborate piece of theater whose only job was to produce one specific feeling: the feeling of being looked at, fully, by someone who wasn't going to look away.
Which meant there were about forty other ways to get that feeling, several of them considerably simpler than the scenario. And it meant that if we'd enacted the scenario without understanding what it was for, we might well have executed it perfectly and left me feeling nothing.
That's the gap between fantasy and desire. It's one of the most useful distinctions in this entire field, and almost nobody makes it.
The Definitions, Plainly
Desire is the wanting itself. It's a drive — an appetite, a pull toward something. It has intensity and direction but no pictures in it. And underneath any specific desire sits something more stable: a core desire, the emotional experience you're actually after. To be wanted. To be seen. To be taken. To be safe. To be in control. To be adored.
Fantasy is content. It's a scenario — a story your mind constructs, with characters and a setting and a sequence of events. It has images, dialogue, a location. It's a piece of narrative.
The relationship between them is the thing to hold onto: fantasy is the vehicle, desire is the cargo. Your mind builds scenarios in order to generate feelings. The scenario is a means. The feeling is the end.
Which means two fantasies that look nothing alike can be carrying the identical desire, and two people with the exact same fantasy can be after completely different things. Justin Lehmiller's survey of 4,175 American adults found that 97% of people have sexual fantasies, and that seven broad themes cover roughly 96% of them. But a group-sex fantasy held by one person is about feeling overwhelmingly desired, and the same fantasy held by another is about novelty, and for a third it's about watching their partner be wanted. Same image. Three unrelated wants.
So the content of a fantasy tells you remarkably little on its own. You have to ask what it's for.
The Three Layers
Here's the model I use with clients, and it's just a matter of keeping three things separate.
Layer one: the core desire. Why. The emotional experience you're after. Fairly stable over a lifetime.
Layer two: the fantasy. The image. The scenario your particular history happened to construct to deliver that experience. Highly variable, often strange, frequently shaped by whatever you were exposed to around age fourteen.
Layer three: the behavior. What you'd actually do with another person in a real room. Constrained by consent, logistics, physics, and what both people genuinely want.
Nearly every mess people get into here comes from collapsing two of these layers into one.
Four Ways People Get It Wrong
Mistake one: hearing a fantasy as a request.
This is the most common and the most damaging. One partner finally says a fantasy out loud — which took them years — and the other hears a proposal. A to-do item. Sometimes an ultimatum.
Then one of two bad things happens. Either the listening partner panics, because they've just been handed something they don't want to do and believe their marriage now depends on it. Or they dutifully agree to attempt it, out of accommodation, which guarantees it goes badly — because the person performing it is managing their own discomfort the whole time, and everybody can feel that.
A fantasy disclosed is information, not a request. Lehmiller's data is clear that most people never act on their favorite fantasy and a great many don't want to. "I think about this" and "I want to do this" are different sentences, and a partner's first response to a disclosure should be curiosity about what it's for, not a decision about whether to schedule it.
Mistake two: trying to solve a desire problem with a fantasy.
Couples whose intimate life has gone flat reach for content. New positions, a new scenario, a toy, a weekend away. Sometimes that works. Often it does nothing, and the couple concludes that nothing works.
Here's why. Emily Nagoski's dual control model — originally developed by Janssen and Bancroft — holds that sexual response runs on two systems: an accelerator that responds to arousing input, and a brake that responds to everything saying not now. Stress, resentment, self-consciousness, exhaustion, fear of judgment.
Fantasy is accelerator. If the actual problem is a brake — and in long-term relationships it usually is — then more accelerator does nothing, and sometimes makes it worse, because now you've added performance pressure on top of whatever was already stopping you. You cannot novelty your way out of an inhibition problem.
Mistake three: judging yourself by your fantasy content.
If you believe a fantasy is a window into what you want to do, then having a disturbing fantasy means you're a disturbing person. That's the logic that keeps enormous numbers of people silent about their inner lives, and it rests on a false premise.
Fantasy is a space with no consequences — which is specifically why it works. It can run scenarios precisely because nothing is at stake. Your erotic imagination doesn't need policing, and the content of a fantasy is not a referendum on your character. It's a referendum on nothing at all.
Mistake four: enacting it literally and being disappointed.
The subtlest failure. A couple does the thing, technically correctly, and it's a letdown. Then both people quietly conclude something is wrong — with the fantasy, with them, with the relationship.
What actually happened is that they built the vehicle and forgot the cargo. They reproduced the scenario and missed the feeling, because nobody ever asked what the feeling was. A scenario executed without its emotional payload is set dressing.
The Diagnostic
Two questions, and they do most of the work.
"Do I want this to happen, or do I want to think about this?"
Be honest. Some things are better in the mind, where they're perfectly controlled and nobody's elbow is in the way, than in a body, where they're not. That's not a deficiency. A fantasy that works beautifully as a fantasy and would be mediocre or distressing in reality is functioning exactly as designed.
"If I could have the feeling without the scenario, would I take it?"
This is the one that cracks things open. If the answer is yes, the scenario is a vehicle and you have options. If the answer is no — if the specific imagery is load-bearing — then you've learned something real about what you're after, and that's worth knowing too.
How to Translate One Into the Other
When a couple brings a fantasy to me, we treat it as a design brief rather than a script. The process is roughly:
Name the scenario without evaluating it. Just get it in the room. No negotiation yet, no decisions, no reassurance. One person describes, the other listens.
Find the feeling. What's the best moment in it? Not the climax of the plot — the moment that carries the charge. Then: what does that moment feel like? Being wanted? Not having to decide anything? Being the center of someone's attention? Getting away with something?
That answer is the actual brief. Everything else was packaging.
Generate other vehicles for the same feeling. This is where it gets practical, and where couples usually get relieved. If the payload is being overwhelmingly wanted, there are a dozen ways to deliver that, most of them involving no logistics whatsoever. If it's not having to be in charge, same. The original scenario is now one option among several rather than a hurdle the relationship has to clear.
Then decide about behavior, separately. Some fantasies should be enacted. Some should be talked about during sex and never performed. Some should stay entirely in one person's head, and that's a perfectly good outcome. The point of the translation isn't to find a way to do everything. It's to stop treating the image as an obligation.
Why This Is Worth the Trouble
The practical payoff is that it defuses the two worst conversations in a marriage.
It defuses the one where someone discloses and their partner panics, because once you understand that the fantasy is a vehicle, a disclosure stops being a demand and becomes a clue. And it defuses the one where someone feels broken for what's in their head, because the content was never the thing being measured.
And it gives you something better than either: a way to actually answer the question most adults go blank on. Not what acts do you like, which keeps you at the surface, but what are you after. The first question has an awkward answer. The second one has a useful one.
Mine was Being Seen. I spent a decade carrying around an elaborate piece of theater built to deliver it, convinced the theater was the point.
It wasn't. Brittney looking at me — actually looking, not glancing — does the same job, and it doesn't require a cast.
Brittney and I built Coelle around the layer underneath the content. A guided session isn't a scenario to enact; it's a structure that puts both of you in a state where the feeling is available. Which is usually what you were after anyway.
And if you've got something you've never said out loud, or you've said it and the conversation went sideways, translating a fantasy into something you can both work with is the center of what I do. Book a free discovery call here.
Sources: Justin J. Lehmiller, Tell Me What You Want (Da Capo Press, 2018). Emily Nagoski, Come As You Are, on the dual control model (Janssen & Bancroft). Celeste Hirschman & Danielle Harel, the Somatica Institute framework on core desires.
