Let’s talk about the elephant in the enchanted castle.
Beauty and the Beast is one of the most beloved romantic archetypes in existence—and also one of the most debated. Because underneath the rose petals and the ballroom dancing and the beast learning to love again, there’s a foundation that modern readers increasingly can’t look away from: she was his prisoner.
If you’ve been writing beast romance or forced proximity romance and feeling vaguely uneasy about the captivity element—you’re not wrong to feel that way. But you’re also not stuck. Writing captivity romance that works for contemporary readers isn’t about sanitizing the darkness out of the premise. It’s about understanding exactly what makes it problematic, and building your story so that the romance develops on solid ground.
That’s what this post is for.
(If you’re building a beast love interest from scratch, you might want to start with Writing the Beast: How to Create Monstrous Love Interests Readers Root For—this post picks up where that one left off, specifically on the captivity question.)
Stockholm syndrome is a psychological survival response. When someone is held captive, their nervous system can generate positive feelings toward the captor as a coping mechanism — a way of managing fear and powerlessness when escape isn’t possible. It’s not love. It’s adaptation.
The problem with romanticizing it in fiction is that it frames a trauma response as evidence of genuine connection. The feelings are real, but they’re produced by fear and constraint, not by free choice. Remove the captivity, and there’s no way to know whether those feelings would survive.
That matters in romance, because romance—at its core—is a genre about choice. Two people who could walk away, who have a full life and other options, choosing each other anyway. When you remove real choice from the equation, you don’t have a love story. You have a survival story with romantic feelings layered on top.
This doesn’t mean you can’t write a story that begins with captivity. It means the romance cannot be built on it.
Here’s the reframe that will do the most work for you: forced proximity and actual captivity are not the same thing, and the difference matters enormously.
Forced proximity means circumstance keeps two people together. Neither one controls whether the other stays. They’re snowed in, stranded, assigned to the same mission, bound by a magical contract neither chose, stuck in an arranged marriage they’re both trying to navigate. The tension is external. Neither is the other’s captor.
Actual captivity means one person controls whether the other leaves. The power to go rests entirely with the person holding the keys—literally or figuratively.
Forced proximity is one of romance’s most reliably effective engines. Actual captivity is a power imbalance that needs to be named, addressed, and actively dismantled before the romance can stand on stable ground.
The good news: most “captivity” romance premises can be reframed as forced proximity with a small amount of structural rethinking. What if they’re both trapped in the castle by the curse, not just her? What if she seeks him out because she needs something only he can provide? What if she has skills or knowledge he genuinely needs, creating real mutual dependence from the start? These aren’t workarounds — they’re stronger story foundations.

Even in stories that begin with genuine captivity, your heroine’s agency doesn’t have to disappear. Physical constraint and mental agency are not the same thing.
A character can be physically limited and still make active choices about how she responds, what she resists, what boundaries she holds, what she decides to reveal or conceal. She can have skills, knowledge, or emotional power that the beast genuinely needs. She can negotiate. She can refuse. She can make the captivity uncomfortable enough for him that he has to reckon with what he’s done.
What kills reader sympathy — and reader investment in the romance — is a heroine who becomes entirely passive. Who stops having her own interiority. Who exists only to react to him, soften toward him, eventually love him. Even in constraint, she needs her own goals, her own sense of self, her own reasons for doing what she does.
The structural principle here: give her power within the constraints, then expand those constraints over time. Trust builds, freedoms grow, the power dynamic shifts—so that by the time the romance properly develops, she is choosing from a position of genuine agency, not desperation.
This is where most captivity romance goes wrong, and it’s a craft problem as much as an ethical one: the romantic feelings develop while she is still powerless.
The rule of thumb is simple. She can notice him in Act One. She can find him interesting, even compelling. She can register attraction in the way that any person might register another person’s appeal. But genuine romantic feelings—the kind that means something, the kind that asks the reader to root for the relationship—need to develop after the power has started to shift.
A structure that works:
In Act One, establish the captivity or forced proximity, make the stakes clear, and let her begin to see him as a person rather than a threat. In Act Two, the power dynamics actively shift—she gains freedoms, he gives things up, mutual vulnerability develops, they begin to move toward something like equality. In Act Three, they are choosing each other as equals, or close enough to it that the choice feels real.
The romance that pays off is the one in Act Three. Everything before is groundwork.
The most compelling captivity-adjacent romances tend to feature mutual vulnerability alongside the power imbalance. He has physical power or social power; she has emotional or intellectual power. Neither is completely dominant. Both have something to lose.
Green flags to build into your story: he gives her the keys without being asked. He tells her she can leave. He helps her find an exit even when it costs him something. These are the moments that transform a captor into a love interest—not grand declarations, but concrete proof that her freedom matters more to him than his own desires.
Red flags to avoid: possessiveness romanticized while she’s still his prisoner. Physical intimacy before the power balance has shifted. Forgiving genuinely harmful behavior because “he loves her” or because understanding his past trauma explains it. The story implying she “earned” his humanity by staying despite the captivity.
There’s a version of this that your characters can actually address within the narrative. She can say: “You were my captor. That’s not a foundation I can build on.” He can recognize it: “I know what I did. I don’t expect you to forgive it—I’m asking you to let me prove I’ve changed.” She can leave, come back by choice, and mean it. Stories that name the problem inside themselves tend to earn more reader trust, not less, because they signal that the author sees it too.
Here’s the thing: the captivity element in Beauty and the Beast stories isn’t actually what readers fall in love with. What they fall in love with is the forced proximity, the tension of two people who shouldn’t work being unable to stay away from each other, the slow reveal of tenderness beneath something frightening, the fantasy of being truly seen.
All of that survives when you fix the captivity problem. None of it depends on her being unable to leave.
Some of the most satisfying modern takes on this premise work precisely because they subvert the power dynamic creatively—she stays because she’s hiding from something worse and he’s the safest option, she has her own research or agenda that requires access to the castle, he’s actually trying to get her to leave because he knows what he is and doesn’t trust himself. These premises generate the same tension, the same slow burn, the same eventual pay-off—without requiring readers to quietly paper over a coercion foundation.
You can also flip it entirely: she holds the power, he is in some way constrained, and the story becomes about her reckoning with what she’s doing. That’s a different emotional arc, but a rich one.
Contemporary romance readers—especially romantasy readers—are sophisticated about tropes. They know the archetypes, they’ve read the discourse, and they bring that critical lens to their reading. What this means practically is that you don’t need to write a sanitized, conflict-free romance. You need to write one where the problems are legible and the story takes them seriously.
Readers will accept complex, morally ambiguous beginnings. They will accept forced proximity with real tension and constraint. They will accept power imbalances that evolve and shift. What they won’t accept—or won’t accept uncritically—is a story that romanticizes coercion without acknowledging it, or frames Stockholm syndrome as proof of love.
The good news is that addressing these dynamics tends to make stories richer, not safer or flatter. A heroine who is actively wrestling with her own feelings, who distrusts her attraction because she knows the context in which it developed, who chooses to leave specifically so she can come back freely—that’s a more interesting character than one who simply falls in love against a picturesque backdrop.
The captivity trope works when it’s actually about something: about power and trust, about what it means to choose freely, about the kind of love that holds up when all the circumstances change. Keep that as your north star, and you can write a romance that honors the fairy tale while giving readers a story they can root for without reservation.
Want feedback on whether your captivity romance premise has the right foundation? A Mini Manuscript Critique looks at exactly this—the structural and relational dynamics of your opening chapters, so you know what’s working before you’re 80,000 words in.