AITA for not hyphenating my last name?

A man recently found himself revisiting a decades-old decision about something many couples discuss before marriage: last names. Nearly twenty years ago, during the engagement period, his future wife suggested hyphenating their surnames. Her reasoning was simple—she was the only child of a father who was also an only child, and without some version of the name continuing, her family’s surname would disappear.

The conversation between the couple remained civil but firm. The idea of their children carrying a hyphenated surname felt completely unacceptable to him, and the disagreement nearly escalated to the point where the wedding itself might not happen. In the end, his wife dropped the request and their three children all received his family’s last name. For two decades the issue never resurfaced—until a casual comment from his brother made him question whether he had been unfair.

‘AITA for not hyphenating my last name?’

During their engagement, the couple had a serious conversation about family names.

The disagreement nearly escalated into a much bigger conflict before the wedding.

After receiving strong reactions online, the poster shared an unexpected update.

Disagreements over surnames are surprisingly common during marriage planning. For many people, a last name represents family heritage, identity, and tradition. When partners come from different family structures—such as being the last person able to pass on a surname—the discussion can become emotionally significant. Couples often consider several options, including hyphenation, creating a new surname, or choosing one parent’s name for practical reasons.

In this situation, the tension seemed to stem from differing values rather than hostility. One partner saw the surname as a symbol of preserving a family line, while the other viewed a hyphenated name as something he strongly disliked. Conflicts like this highlight how deeply personal cultural expectations around names can be. In many societies, traditions historically favored one parent’s surname continuing, which can make negotiations feel uneven.

However, the later revelation adds another layer to the story. The wife had not been advocating for the change herself but was attempting to shield her partner from direct pressure coming from her father. That detail shows how family expectations can influence relationship decisions in unexpected ways. Ultimately, the conversation years later opened the door for honest communication and reflection, demonstrating how revisiting old disagreements can sometimes strengthen understanding within a long-term relationship.

Here’s what people had to say to OP:

Many commenters strongly criticized the poster and believed he handled the situation poorly.

Some commenters expanded on the argument by pointing out the imbalance in the compromise.

Others reacted with blunt or sarcastic remarks while still criticizing the decision.

This story shows how something as simple as a surname can carry emotional weight tied to tradition, identity, and family expectations. What seemed like a closed chapter from years ago resurfaced unexpectedly, prompting the poster to reflect on whether his stance had been too rigid. The surprising update added another dimension, revealing that outside family pressure had played a role in the original disagreement.

It also raises interesting questions about how couples handle decisions tied to heritage and legacy. Should both partners compromise when it comes to children’s last names, or is it reasonable for one tradition to take priority? And if you were in this situation, would you choose a hyphenated surname, create a new one, or stick with one family name?