There is a version of the small wedding that happens by default. The budget runs out, the families are complicated, the venue has a low maximum and nobody fights it. That wedding exists, and there is nothing wrong with it, but it is not the one worth talking about. The one worth talking about is the wedding of thirty that someone chose, deliberately, when they could have had more.
The chosen version is rarer, partly because it requires saying something nobody wants to say out loud: that a smaller number of people makes for a better day. Not a cheaper day. Not a scaled-down day. A better one, for reasons that have nothing to do with money and everything to do with what a room full of people who actually know each other feels like from the inside.
What you are actually choosing
A wedding of thirty is not an edited version of a wedding of a hundred and twenty. It is a different occasion. The structure of the evening changes. The speeches land differently when everyone in the room has the context. The dinner is a dinner rather than a catered event. The photographs contain faces rather than crowd. These are not consolations. They are the thing itself, and you cannot get them by cutting a long list short. You can only get them by building from thirty up rather than from a hundred and twenty down.
That distinction matters because the two processes produce different guests. Cutting down produces the survivors of a cull, which is a subtly uncomfortable thing to be. Building up produces the people you would call if something happened, which is a different category entirely and one that most lists of thirty satisfy almost automatically.
A wedding of thirty is not an edited version of a wedding of a hundred and twenty. It is a different occasion.
The pressure that runs the other way
The received idea is that a large wedding is the generous one and a small wedding is the withholding one, as though invitation were a resource to be distributed as widely as possible. It is a strange idea when you hold it up. A wedding is not a dividend. The generosity in it is not proportional to headcount.
What the received idea actually reflects is that a large wedding is easier to explain. You can say you invited everyone, or as many as the venue held, and the explanation closes. A small list requires you to say that you chose these people and not those people, which is truthful in a way that makes people uncomfortable, though it is true of every list at every size. The discomfort is not evidence that you have done something wrong. It is evidence that you have done something explicit.
The people who will take it hardest are usually the ones who read the size of the wedding as a signal of where they rank, which is its own problem, and one that a larger invitation would not solve so much as defer. You are not responsible for managing that reading indefinitely. You are allowed to have the wedding that fits the people in your life, in the proportions that are actually true.
What a room of thirty does that a room of a hundred cannot
The obvious thing is that you see everyone. Not in the brief, grazing way of a large reception, where you spend the evening crossing a room to have half a conversation before someone else needs you, but properly. A table of thirty sits together, or close enough. You know where everyone is. You hear the same things at the same time. The day has a shared texture rather than thirty separate experiences happening in parallel.
Less obviously, the people there know why they are there. At a large wedding, some guests are present because the list grew, because the numbers needed balancing, because someone's feelings would have been hurt. At a wedding of thirty, everyone is there because you want them in the room. That is felt. It changes the quality of the occasion in a way that is difficult to describe and unmistakable to experience.
There is also what the scale does to you. A hundred and twenty people require a performance. You are presented, introduced, displayed. Thirty people require your presence. The difference between a day spent being looked at and a day spent being with people is significant enough that it is worth building a whole occasion around.
The thing the small wedding asks of you
It asks you to stop treating the list as a reflection of everyone who deserves acknowledgement and start treating it as a description of the day you want to have. Those are not the same exercise, and conflating them is what makes the list agonising when it does not need to be.
Everyone you leave off the list is someone you could have invited. They are not someone you have wronged. The invitation is not a certificate of worth. It is a practical limit on how many people can be in a room while it still feels like the occasion you chose. Thirty is a meaningful number, not a small one, and the day it produces is not a lesser version of something larger. It is exactly what it is.
The weddings that stay with people, described years later in the specific rather than the general, tend to be the ones where the room was right. Not the largest rooms. The right ones. There is usually a number, different for every couple, at which a wedding stops being an event and becomes an evening, and the people who find that number and hold to it, against the assumption that more is more, tend to feel it was the correct decision for longer than almost any other one they made.