There’s been a particular panic in naming discourse lately about “masculine names for girls” being some kind of trend that needs managing. The assumption is that there’s a right way and a wrong way, a authentic way and a trend-chasing way. The thing is: this conversation reveals way more about our anxiety about gender than it does about names.
Here’s the actual history: most names don’t have genders. We assigned them. And we’re currently in a moment where that assignment is being actively reconsidered. That’s not a problem. It’s actually the most interesting thing happening in contemporary naming culture.
The question isn’t whether girls can use traditionally “masculine” names. They always could. The real question is whether you’re doing it consciously—with intention, understanding, and clarity about what that choice signals.
Why This Matters: Gender and Naming as a Political Question
First: understand that “masculine names for girls” isn’t a neutral category. It’s a cultural assertion. The fact that we have a concept of “masculine names” at all tells you that names carry gender coding. Some names feel “safe” for girls precisely because they’ve been read as feminine for decades. Others feel “bold” or “masculine” because they’ve been traditionally masculine and we’re now applying them across gender lines.
This is actually about what names signal about values and identity—and yes, gender is part of that signal. But understanding that signal is different from being controlled by it.
The historical reality is simpler than the current discourse makes it: names move across gender categories constantly. Margaret was masculine in some contexts. Alexander became Alexandra. James became Jamesina. The idea that names have fixed genders is relatively recent and entirely constructed.
The History: How We Got Here
The Victorian moment and gendering names. The 19th century saw an explosion of distinctly gendered naming conventions. Before that, you had Charles and Caroline, James and Jane—the gender differentiation was usually a suffix or a prefix. But the Victorians became obsessed with making names sound gendered. Soft, vowel-heavy names for women. Consonant-heavy, sharp names for men. This wasn’t natural; it was cultural engineering.
And it worked. We internalized it. We still carry that gendering in our intuitive response to names.
The 20th century and name-borrowing. As women entered professional spaces, some girls started getting names that had traditionally been masculine—James, Alexander, Henry. Not because parents were trying to make a statement about gender, but because they liked the names and saw no reason the names couldn’t apply to their daughters. This was particularly common in certain cultures and classes. When names work across languages and cultures, they work across gender categories too.
The late 20th century and feminism. The feminist movement reframed “masculine names for girls” as a choice. Not a borrowing, but an assertion. Giving your daughter a “masculine” name became a political statement about refusing to soften her identity before she even existed. Names that carry strength and weight were reframed as tools for signaling values.
The contemporary moment and gender fluidity. Now we’re in a moment where gender itself is being reconsidered, and names are following. The question isn’t “can girls have masculine names?” It’s “what even is a masculine name?” And that’s a much more interesting question.
The Authentic Question: What Does This Actually Mean?
Here’s where intention enters. When you’re thinking about giving your daughter a name that’s traditionally been masculine, the question isn’t “is this okay?” It’s “am I doing this consciously, or am I doing this because it’s trending?”
Authentic reasons to use a traditionally masculine name:
You genuinely love the name, regardless of its gender coding. This is the most honest reason. If you love James and you have a daughter, name her James. The name itself is what matters. When you understand what your naming preferences actually reveal about your taste and values, you’re making intentional choices rather than trend-chasing ones.
You’re honoring family tradition or cultural heritage. Many cultures don’t gender names the way English-speaking cultures do. If you’re drawing on a family name that happens to be traditionally masculine in English but carries different cultural significance in your heritage language, that’s authentic. Cross-cultural naming ethics matter here—you’re not appropriating; you’re honoring.
You’re making a deliberate statement about gender and identity. If you’re conscious about the fact that you’re choosing a name that carries “masculine” coding and you’re doing it because you want to signal something about how your daughter gets to take up space in the world—that’s authentic. The consciousness is the key.
You’re drawn to names that carry strength, weight, and substance and many of those names happen to be traditionally masculine. This is a legitimate aesthetic and values choice. Not every “strong” name has to be reframed as “bold for a girl.” Some names are just strong.
Inauthentic reasons to use a traditionally masculine name:
You’re using it because you think it will protect your daughter from discrimination or make her seem more professional. This is fear-based naming, and it usually backfires. The hidden class politics of naming means that names don’t protect or harm in the way we think they do. And if you don’t trust your first name choice enough to stand behind it, the solution isn’t a “safer” name—it’s reconsidering what you actually want to signal.
You’re doing it because it’s trendy and you want your daughter’s name to feel modern or edgy. Trends fade. Authenticity lasts. The names that feel new but are actually very old are the ones that work because they have substance beyond the trend. If you’re choosing a “masculine” name solely because masculine-coded names for girls are trending, you’re not thinking about your daughter’s identity; you’re thinking about what feels current.
You’re doing it because you’re uncomfortable with femininity and want your daughter to be “more than” a typical girl. This is a deeper issue, and the name won’t solve it. Names that carry actual substance don’t require gender-coding reassignment. Your daughter’s identity is broader than her name.
The Names That Work: Understanding What “Masculine-Coded” Actually Means
Let’s be clear about what we’re actually talking about when we say “masculine names for girls.”
Names that have traditionally been masculine but work across gender:
Alexander (al-ig-ZAN-der)—”Defender of men,” and the gender coding here is so deeply embedded that giving Alexander to a girl feels bold. But here’s the thing: the name itself is strong, it’s accessible, and it works. If you’re drawn to names with that kind of weight and substance, Alexander doesn’t stop working because you’re applying it to a girl. Lex or Ali as nicknames work across gender naturally.
Julian (JOO-jun)—”From Julius,” and Julian carries that understated sophistication that works regardless of gender. The name has literary weight (Julian in Brideshead Revisited, Julian Lennon). Jules as a nickname is warm; Julian is the full statement. The masculine coding here is light—the name transcends it naturally.
Elliott/Eliot (EL-ee-ut)—”The Lord is my God,” and Elliott has been climbing for girls in recent years. The name is accessible, it’s literary, it works. The gender coding is light enough that it doesn’t feel like a statement; it just feels like a good name. When names carry intellectual weight without requiring gender confirmation, they do so naturally.
River (RIV-er)—”Water current,” and River is the prototype of the contemporary “masculine name for girls” that doesn’t feel like a statement anymore. It just feels like a name. The nature association is gender-neutral; the sound is strong without being aggressive. Names rooted in nature transcend gender coding naturally.
Rowan (RO-un)—”Tree with red berries,” and Rowan works across gender because the name is strong without trying. The botanical association carries substance. When names feel grounded and rooted in something real, gender coding becomes secondary to the name’s actual presence.
Morgan (MOR-gun)—”Sea-born,” and Morgan has already crossed the gender boundary so thoroughly that arguing about its “real” gender is pointless. The name is strong, it’s literary (Morgan le Fay), it works. The gender coding is flexible because the name itself is strong enough to carry whatever identity you bring to it.
Cameron (KAM-run)—”Crooked nose,” and Cameron has been steadily used for all genders for decades now. The name is strong, it’s accessible, it works. The gender coding is so light at this point that it feels almost quaint to discuss whether it’s “really” masculine.
Names that are more traditionally masculine but increasingly used for girls:
James (JAYMS)—The masculine baseline name, and James for a girl is no longer shocking. The name is strong, it carries weight, and it works. If you’re drawn to names with genuine substance, James is the prototype—it ages beautifully regardless of gender. The boldness is in the name itself, not in the gender assignment.
Henry (HEN-ree)—”Estate ruler,” and Henry for a girl signals something specific: you’re not trying to make her “safer” or more “professional.” You’re saying this name matters more than the gender coding attached to it. The name carries weight, it works, and when you understand what your naming choices signal, you’re making conscious rather than anxious choices.
Oliver (AHL-i-ver)—”Olive tree,” and Oliver for a girl is increasingly common because the name is strong without being aggressive. The botanical association is gender-neutral. Names that carry substance do so regardless of the gender you apply them to.
Elliot (already mentioned above)—The intellectual name that works across gender naturally.
Gabriel (GAB-ree-ul)—”God is my strength,” and Gabriel is biblical, it’s strong, it works. The gender coding is lighter than you’d think because the name’s substance transcends it. When names carry weight across languages and cultures, they also transcend gender coding.
Lucas (LOO-kus)—”From Lucania,” and Lucas for a girl is no longer a statement; it’s a choice. The name is strong, it’s accessible, it works across contexts. The gender coding is light enough that the name carries more weight than the gender assignment.
Leo (LEE-oh)—”Lion,” and Leo is short, strong, and powerful regardless of gender. The name works because the name itself is strong, not because you’re making a statement about gender. The boldness is inherent to the name.
Kai (KY)—Hawaiian origin meaning “sea,” and Kai works across gender naturally because the name is strong and the cultural association is gender-neutral. This is the future of “masculine names for girls”—names where the gender coding is so light that the question becomes irrelevant.
Names that are moving across the gender boundary rapidly:
Phoenix (FEE-niks)—The mythical bird, and Phoenix is increasingly used for all genders because it carries strength and narrative weight. The gender coding is light; the substance is real. Names that carry meaning and power do so regardless of gender.
Justice (JUS-tis)—A virtue name, and Justice for a girl is no longer shocking. The name carries weight, it signals values, and the gender coding is almost irrelevant at this point. This is what happens when substance matters more than gender assignment.
Asher (ASH-ur)—”Happy, blessed,” and Asher for a girl works because the name is strong and accessible. Names that work across gender categories are increasingly common because parents are choosing names they love rather than names that fit gender categories.
The Pitfalls: What Not to Do
Don’t use a masculine name as apology for femininity. If you’re choosing a “masculine” name because you’re uncomfortable with typical feminine names, that’s a deeper conversation—about your values, about what femininity means to you, about what you’re actually trying to signal. The name won’t solve that. Don’t project that discomfort onto your daughter.
Don’t choose a traditionally masculine name and then treat it as if it’s still masculine-coded. If you name your daughter James, commit to that. Don’t call her “Jamie” because you’re uncomfortable with the boldness of your own choice. Names that carry weight should be worn clearly, not hedged with nicknames that soften them.
Don’t treat masculine-coded names as protection against discrimination. The research on names and discrimination is complicated, and the protection that comes from a “masculine” name is contingent on other factors (race, class, geography). If you’re choosing a masculine name because you think it will protect your daughter, you’re making an anxious choice. If you’re choosing it because you love the name, that’s different. Understanding the hidden class politics of naming means understanding that names don’t protect or harm in the way we think they do.
Don’t choose a traditionally masculine name and act like you’re doing something radical. If you’re choosing James or Henry for your daughter in 2025, you’re making a choice that’s increasingly mainstream. That’s fine. But don’t act like you’re breaking barriers. The real work is in making conscious naming choices, not in which gender category the name traditionally belonged to.
The Authentic Framework: How to Choose Well
Ask yourself: why do I love this name?
If the answer is “because I love how it sounds” or “because it has literary weight” or “because it honors family,” you’re choosing well. If the answer is “because it’s masculine and I want to seem edgy” or “because I think it will protect her,” you’re choosing anxiously.
Understanding what your naming preferences actually reveal helps you make conscious rather than reactive choices.
Ask yourself: am I comfortable wearing this choice?
If you name your daughter Julian, are you genuinely comfortable with that, or are you hedging with nicknames and explanations? Because your daughter will inherit whatever hesitation you carry into the choice. If you’re all-in, she gets to be all-in. If you’re hedging, she gets to be hedged.
Ask yourself: what values am I signaling?
Names signal values—about identity, about culture, about what you think matters. What do you actually want to signal? Strength? Heritage? Literary taste? If you’re clear about that, the “masculine or feminine” question becomes less important than the “does this name carry what I actually want to signal” question.
Ask yourself: does this fit with my other naming choices?
When you think about how names work as a family set, you’re thinking about coherence. Is this name coherent with your other choices? Or does it feel like you’re making a different statement with each kid? Consistency matters across a family.
Ask yourself: ten years from now, will I be proud of this choice?
This is the real test. Not “will this be trendy” but “will this feel true to who I am and what I believe.” Names that feel grounded and intentional stand the test of time.
The Real Conversation: Beyond Gender Coding
Here’s what I actually care about: that you’re making conscious choices. That you’re not choosing names out of anxiety about gender. That you’re not hedging your bets with “masculine” names because you’re uncomfortable with femininity. That you’re not trending without thinking.
The question isn’t “can girls have masculine names?” They can. The question is “are you choosing this name because it matters to you, or because you think it will protect or define your daughter in ways you can’t actually control?”
When you understand what your child’s name actually signals—about culture, identity, values, and the stories you’re telling before they exist—you’re ready to make naming choices that matter. Whether those names are traditionally “masculine,” “feminine,” or completely ungendered becomes secondary to the fact that you’ve chosen with consciousness.
If you’re looking for a framework that helps you think through not just individual names but what they signal, how they work in your family, what values they carry—get your Personalized Name Report. It’s the tool for moving beyond trend and anxiety into intentional, grounded naming choices.
Because the real boldness isn’t in choosing a “masculine” name for your daughter. It’s in making any naming choice with full consciousness of what you’re signaling and why it matters.
Related Reading
Your Name Report
Ready to think beyond gender and trend? Get your Personalized Name Report at https://app.thenamereport.com/—because the right naming choice comes from consciousness, not anxiety.
