Changing Your Last Name in Marriage: A Biblical Look
Short answer: The Bible never commands a wife to take her husband's last name, and it never forbids it. Genesis 2:23-24 establishes the one-flesh union and the leaving-and-holding-fast that defines marriage, and it records the man naming the woman, but it does not legislate a naming practice. What we call a last name is a relatively recent legal convention, and Scripture speaks to it only indirectly through customs of family identity, inheritance, and household order. Christians have freedom here. A wife may take her husband's name, keep her own, or hyphenate, and none of those choices is sin. What matters is that the decision is made in love, honesty, and unity rather than from pressure, superstition, or a mistaken claim that God requires it. Couples should weigh conscience, culture, family, and practical consequences together.
What Genesis 2:23-24 actually says and does not say
The passage opens with the man's exclamation over the woman: Genesis 2:23 says, "This is now bone of my bones, and flesh of my flesh. She will be called 'woman,' because she was taken out of Man." Notice what is happening. The man is recognizing sameness of nature and closeness of relation. He names her by what she is, not by a family line. This is a declaration of kinship and delight, and it precedes the fall. The verse is poetry and recognition, not legislation about surnames, which did not exist in the ancient Near East.
Then Genesis 2:24 draws the conclusion: one flesh. The verse grounds marriage in leaving, holding fast, and becoming one. This is the verse Jesus quotes in Matthew 19 and Mark 10, and Paul quotes in Ephesians 5. It is about the covenant bond between husband and wife, not about what a bride writes on a government form. To read a surname requirement into this verse is to import a modern legal category into an ancient text. The text simply does not address the question.
That does not make the passage irrelevant. It tells us that marriage creates a new primary bond. A woman and a man leave father and mother and cleave to one another. Their loyalty, household, and future are now joined. Any naming decision is downstream of that reality. If a surname choice expresses the new union, it can be fitting. If it expresses independence from one's spouse, that is worth examining. The verse tells us what marriage is; it leaves the paperwork to wisdom.
So the honest answer is that Genesis 2:23-24 establishes the meaning of marriage and the fact that the man named the woman, but it establishes no command about surnames. Anyone who tells you God requires a wife to take her husband's name is going beyond the text. Anyone who tells you taking his name is inherently degrading is also going beyond the text. The passage is about who we are to each other, not what we are called on documents.
The man named the woman, but naming in Scripture is a broader category
In Genesis 2:23 the man names the woman, and in Genesis 3:20 he names her Eve, mother of all living. Naming in Scripture often carries authority or significance. Adam names the animals in Genesis 2:19-20, which many readers connect to dominion and stewardship. But naming is not only an act of authority. It is also an act of identification, blessing, and relationship. The same word can carry very different weight depending on the context, so we should be careful before building a rule for modern marriage out of this one moment.
Consider the range. God renames Abram Abraham and Sarai Sarah. Parents name children. Prophets give symbolic names to children as signs. Jesus renames Simon as Peter. In Ruth 4:11, the elders bless the couple and speak of the woman who has come into the house, invoking Rachel and Leah as those who built the house of Israel. The language is about building a household, a shared name and legacy, not about which legal surname the bride carries. That is a different world from ours.
What we can say is that Scripture treats names as meaningful. They carry identity, memory, and hope. That means a Christian couple's naming decision should be meaningful too, not automatic on the one hand or defiant on the other. If a wife takes her husband's name because it joyfully pictures the new household, that is good. If she keeps her name for reasons she can explain in good conscience, that is also good. The category of naming in Scripture is broad enough to hold both.
We should also note that the Bible does not treat a woman as property transferred by a label. The man's naming of the woman in Genesis 2:23 is intertwined with his recognition that she is his own flesh. He is not claiming chattel; he is celebrating kinship. Any use of the naming theme to justify treating a wife as a possession is a misreading. The trajectory of Scripture runs the other way, toward the husband's sacrificial love and the wife's honored dignity.
Marriage as one flesh is the real issue behind the surname question
The heart of the matter is unity. Genesis 2:24 says the two become one flesh. That is a profound statement about covenant, intimacy, children, household, and shared life. A surname is one small sign among many of whether a couple is actually living as one. If a marriage is marked by secrecy, rivalry, separate finances kept hidden, and divided loyalties, the surname on the license is irrelevant. If a marriage is marked by shared purpose and open hands, the surname is a detail.
Paul develops this in Ephesians 5:22-33, where he calls wives to submit to their own husbands as to the Lord and then calls husbands to love their wives as Christ loved the church. The whole passage is about mutual devotion under Christ, not about administrative control. The husband's calling is sacrificial love, not the enforcing of preferences. A husband who demands his wife change her name is not exercising authority in the pattern of Ephesians 5; he is asserting himself in a way that passage does not authorize.
Conversely, a wife who refuses to consider her husband's name at all, purely as a way of keeping him at arm's length, may have a heart problem worth addressing, though the name itself is not the sin. The question should be, what does this choice communicate about our union? Names are not the substance of oneness, but they can be a sign. Signs matter, but they are not the covenant itself. Couples should talk about what they want their name to say and why.
This is where freedom becomes genuinely freeing. If oneness is the goal, a couple can choose a surname arrangement that serves it. That might mean the wife takes the husband's name, or keeps hers professionally while using his socially, or they adopt a shared hyphen. It might mean a new name entirely in some circumstances. Scripture gives no formula. It gives a direction: living as one, in love, before God.
Ancient Israelite households and the modern surname are not the same thing
We need to be clear about history. Surnames as we know them, inherited family names used in legal records, are not a biblical institution. In the Old Testament, people were identified by patronymics such as son of Nun or daughter of Zelophehad, by clan, and by town. Numbers 27:1-11 records the daughters of Zelophehad coming before Moses with a real inheritance concern. Their father had died without sons, and they asked for a possession among their father's brothers. God ruled in their favor and established a statute for Israel.
That account matters for this topic because it shows how family identity, land, and name worked together in Israel, and it shows that God was attentive to women's standing in that system. It was not a system in which women were erased, and it was not a system of modern surnames. The daughters of Zelophehad kept their father's name and received inheritance so that his name would not be removed from his clan. The concern was legacy and justice, not a rule about what a bride should be called after marriage.
In the New Testament world, Roman and Greek naming customs differed again. Women might keep their own family names. Households were complex, and identity was tied to citizenship, status, and patronage as much as to a shared marital label. When the New Testament writers address marriage, they address conduct and devotion, not naming. They assume the social world they lived in without making its particular customs binding on all Christians everywhere.
So when someone says we should follow the biblical model for changing last names, the first question is, which biblical model? There is no single one. There are several customs across several centuries and cultures, and none of them is commanded for the church. This is a matter of Christian liberty. Couples should study, pray, and choose, and they should not bind one another's consciences where God has not spoken.
What the New Testament says to wives and husbands about identity
First Peter 3:1-7 speaks to wives living with unbelieving or difficult husbands, urging a gentle and quiet conduct that may win them without a word. The emphasis falls on character, not on external markers. Peter then turns to husbands and calls them to live with their wives in an understanding way, giving honor as to a weaker vessel and as fellow heirs of grace. The passage is about how spouses treat each other, especially in hard situations. It never touches naming.
This is significant because 1 Peter is often the passage people reach for when they want to argue for a wife's submission. But submission in this letter is Christlike self-giving, not the surrendering of identity or legal personhood. Peter honors wives as heirs together with their husbands. A wife who keeps her birth name is still an heir of grace. A wife who takes her husband's name is still an heir of grace. The identity that ultimately defines her is in Christ, not on a marriage certificate.
First Corinthians 7:1-5 addresses marital intimacy and the mutual authority of husband and wife over each other's bodies. Paul is answering questions from the Corinthian church about marriage and self-control, and he insists on reciprocity. The husband does not have authority over his own body, and neither does the wife. That mutuality undercuts any use of marriage to dominate a spouse. A naming decision imposed unilaterally is out of step with this pattern.
Put together, the New Testament vision is of two people, each fully a person in Christ, bound in a covenant of love. Their shared life may express itself in a shared name, and that can be beautiful. But the identity that matters is who they are before God. Any teaching that makes a surname the test of a wife's obedience or a husband's headship has imported a cultural custom into the place where the gospel belongs.
Avoiding two errors: traditionalism and contempt
The first error is to treat a cultural custom as a divine command. Taking the husband's name has been common in many Western countries, and it can be a good and meaningful choice. But common practice is not the same as biblical mandate. When a church or family treats a wife who keeps her name as disobedient, rebellious, or not really married, they are adding to Scripture. That is serious. Jesus warned against teaching human traditions as doctrines of God, and this is exactly that kind of overreach.
The second error is to treat the tradition with contempt. Some discussions assume that any wife who takes her husband's name is naive or oppressed. That is also uncharitable and untrue. Many women choose it gladly, as a sign of the new family they are building, and their choice deserves respect. Scripture does not despise ordinary customs; it redeems them. A surname chosen in love and gratitude can be a small, honest picture of two becoming one.
Wise couples do not make this decision as a power struggle. They talk about family expectations, professional considerations, children's names, and what they want their household to look like. They may consult pastors and parents. They may find that one spouse feels strongly and the other does not, and they can honor that. They may also decide to revisit it later. The goal is not to win an argument about names but to build a marriage that reflects the one-flesh union.
Where Christians differ, we should say so plainly and still love each other. This is not a gospel issue. Nobody is justified by a surname. The couple who prays together, serves together, and honors Christ together is living out Genesis 2:24 far more than any couple whose paperwork matches but whose hearts are divided. Freedom in this area is not a concession to the world; it is the proper fruit of a gospel that has set us free from human regulations.
Practical wisdom for couples making the decision
Start with Scripture, and be honest about what it does and does not say. Genesis 2:23-24 gives you the meaning of marriage, not a rule about names. Ephesians 5 and 1 Peter 3 give you the character of Christian marriage: sacrificial love, honor, and mutual devotion. Take those to the decision. Ask whether your choice builds up oneness or quietly undermines it. Ask whether you are acting from conviction, love, and freedom, or from fear of what people will think.
Consider the practical realities. Names affect legal documents, professional identity, children's schooling, travel, and family relationships. Those practical matters are not unspiritual; they are part of wise stewardship. A wife with an established career may reasonably keep her name. A couple may choose to give children the father's name, the mother's name, or a hyphenated form. None of this is commanded, so none of it is forbidden, and couples should feel free to make the arrangement that serves their household best, as long as it is made together.
Watch for pressure and manipulation. If a husband threatens or sulks to get his way, that is not leadership; it is coercion. If relatives shame a wife for her choice, that is not godly concern; it is control. If a wife uses the decision as a weapon, that is not honesty; it is warfare. The surname question is small enough to solve with a conversation and large enough to expose whether a couple is actually practicing the love and honor the New Testament commands.
Finally, hold the decision loosely. A couple may change names now and adjust later for children or family reasons. Christians are free. What cannot change is the covenant: two people, by God's grace, becoming one flesh, loving and honoring each other as heirs together of the grace of life. If your name serves that, use it with joy. If it does not, you are free to choose otherwise, and no one may bind your conscience where God has left you free.
Where faithful Christians differ on this practice, the difference is real but not a matter of salvation. Couples should seek the Lord, seek counsel, and extend grace to those who decide differently.
Biblical fidelity check
What Genesis 2:23-24 does establish: the man recognized the woman as his own flesh, marriage is a covenant of leaving and holding fast that produces one flesh, and Jesus and Paul both treat this verse as the foundation of marriage. What it does not establish: any command about surnames, any requirement that a wife surrender her legal name, or any rule that a husband must impose his name on his household. The passage predates surnames by thousands of years and addresses the nature of the marriage bond, not its administrative details.
A common misreading is to say that because Adam named Eve, God requires wives to take their husbands' names. That reasoning fails on several counts. Naming in Scripture is a broad category used for children, places, and symbolic acts, not only for wives. Adam's naming in Genesis 2:23 is a poetic recognition of kinship, and Genesis gives no command attached to it. Building a moral requirement on a narrative detail, without any apostolic instruction, turns description into law. The New Testament never mentions surnames. Such teaching adds to Scripture and burdens consciences where God has not spoken.
Other passages that speak to Genesis 2:23-24
Several related studies help frame this question. For the shape of Christian marriage as a covenant of self-giving love, see Ephesians 5:22–33: Marriage That Lasts. On how Scripture calls believers to unity and to speak with one voice, What Does 1 Corinthians 1:10 Mean? Context, Theology, and Application is helpful. The foundation of that unity in God's faithful calling is treated in What Does 1 Corinthians 1:9 Mean? Context, Theology, and Application. For a broader survey of the opening chapter of 1 Corinthians, see 1 Corinthians 1: Called, United, and Boasting in the Lord.
Frequently asked questions
Does the Bible require a wife to take her husband's last name?
No. Scripture never mentions last names, which are a much later cultural development. Genesis 2:23-24 establishes the one-flesh union and the leaving-and-holding-fast pattern of marriage, but it gives no command about surnames. The New Testament addresses the character of marriage, not its legal paperwork. A wife may take her husband's name, keep her own, or use a hyphen, and none of these choices is commanded or forbidden. What matters is that the decision is made in love, unity, and good conscience before God, without pressure from anyone.
Does Adam naming Eve in Genesis 2:23 set a pattern for husbands naming wives today?
It does not establish a rule for surnames, though it is a meaningful moment. Adam is recognizing sameness of nature and kinship, and he calls her by what she is: woman, taken from man. Naming in Scripture covers children, places, and symbolic acts, so we cannot reduce it to a marriage regulation. Later, Adam names her Eve in Genesis 3:20 as the mother of all living. Reading a modern legal naming requirement into these verses goes beyond what the text says and burdens consciences where God has been silent.
Is it wrong for a Christian wife to keep her maiden name?
No. Keeping one's birth name is not sin, and it is not rebellion against Scripture. A wife who keeps her name may still honor her husband, submit to him in the Lord, and live out the one-flesh union. The New Testament never ties a wife's obedience to a surname. What would be wrong is using the decision as a weapon against one's spouse, or refusing to consider the marriage bond at all. Couples should decide together, in prayer, weighing conscience, family, and practical needs, with freedom and grace toward one another.
