Text My Wedding
Home / Wedding Guest List / Children
Wedding guest list

Should you have a child-free wedding?

Decide it once, as one rule for the whole list, and decide it by counting rather than by feel. On the worked list below, 22 of 160 guests are under 18 — so going child-free frees 22 seats and turns a list that is 10 over capacity into one that is 12 under. If a number like that is the difference between fitting and not fitting, a child-free wedding is an ordinary, defensible decision and nobody is entitled to overturn it. If your list already fits and there are four children on it, the honest answer is no: you would be buying a conversation with every parent you know in exchange for four seats you did not need. What makes a policy hold is that it applies to all 84 households with its exceptions named in advance, rather than being granted household by household as people ask. Below are 14 worked lists — four policies, the counting pass that picks between them, and the exceptions worth writing down.

Build my guest list →Browse the policies
Which policy, if any

Five situations, and the policy each one points at

Work down these in order and stop at the first one that describes your list. Each answer routes the whole Children circle into one tier rather than returning a verdict on a family, which is the difference between a policy you can repeat and a decision you have to defend twelve times.

1

Your list already fits, and the children on it are your niece and nephew

No policy at all — invite them. A children policy is a real cost: a conversation with every parent on the list, and a handful of households weighing up whether to come. It is worth paying when it buys seats you need. It is not worth paying for four seats on a list that already fits. In the builder, leave the Children circle in Tier B and spend the evening on something that is actually a problem.

2

You are over capacity and roughly a seventh of the names are under 18

Fully child-free, with the exceptions named the same day. This is the version that holds up, because the rule is the same sentence for your sister and for your colleague. Name the exceptions before anyone asks rather than after — an exception granted in advance is a policy, and an exception granted on request is the end of one. In the builder, re-tier the whole Children circle to Not inviting in a single pass and read the seat count; that number is the entire argument.

3

You want your niece and nephew there and no other children

Immediate-family children only, defined by relationship. Write the definition down before you say it out loud: a child is in if their parent is a sibling of one of you. Defined that way it is checkable by anyone and nobody can argue their way across it. Defined as "the children we're close to", it is not a rule — it is a ranking, and every parent on the list will work out where they came.

4

The problem is the evening rather than the day

Ceremony-only — but solve the 5pm question first. Children at the ceremony and adults at the dinner is a genuine middle, and it frees the expensive seats rather than all of them. It also creates twelve households who need somewhere for their children to be at five o'clock. Decide that part now: ceremony-only without childcare is the policy most likely to quietly become fully child-free six weeks later.

5

The problem is toddlers rather than teenagers

An age cut-off, held to the date on the calendar. Count before you pick the number. On this list an over-12 rule still removes 17 of the 22, so it is nearly the same decision in a gentler coat — and the moment it bends for one twelve-year-old it stops being an age rule and becomes a favor. Whatever age you choose, it runs on the wedding date, not on how grown-up a particular child is.

Those are the four policies, and choosing between them is arithmetic you can finish in an evening. What this page deliberately does not give you is the sentence that carries the decision on the invitation — that is a separate craft, it has its own page at adults-only invitation wording, and there is not one example of it here on purpose. If freeing the seats leaves you with room to fill, the number of invitations that fills it is worked out on the wedding attendance rate page, and its answer is exactly the capacity number the builder below takes.

The whole decision, four ways

🚸 Four policies, and what each one costs

These are the four that hold up. Each is a rule about the whole list, and each re-tiers every child on it in one pass rather than filtering some out and leaving the rest to be argued about later. All four run on the same invented list: 160 people, 84 households, 22 of them under 18, against a capacity of 150.

Example 01

POLICY 1 — FULLY CHILD-FREE Applies to · every household on the list, no household exempt Children re-tiered · 22 names → Not inviting Sofia Alvarez · Nina (8), Otto (5) → Not inviting Paloma & Tomas Alvarez · Mia (9), Theo (6) → Not inviting Camila Reyes · Sol (14), Isabel (11), Bruno (7) → Not inviting …12 households in all — 160 → 138 people. Frees 22 seats and takes the list from 10 over capacity to 12 under. Invitations stay at 84: no household disappears, only names inside twelve of them. This is the only version where the rule is the same sentence for your sister and for your colleague.

Fully child-freePersonalize
Example 02

POLICY 2 — IMMEDIATE-FAMILY CHILDREN ONLY In · Nina Alvarez (8) and Otto Alvarez (5) — children of a sibling Out · the other 20 children, across 11 households The definition, written down before anybody asks: a child is invited if their parent is a brother or sister of one of us. Not "close", not "we see them every week" — a sibling. — 160 → 140 people. Frees 20 seats. Two children in the room and one testable sentence covering everyone else, which is the entire reason to define the exception by relationship rather than by affection.

Nieces and nephewsPersonalize
Example 03

POLICY 3 — OVER-12 ONLY (cut-off: 13 on the wedding date) In · Sol Reyes (14) · Marta Reyes (17) · Kiran Raman (16) · Ravi Raman (13) · Freya Lindqvist (15) Out · 17 children aged 12 and under Borderline case, decided by the calendar: Erik Lindqvist turns 13 five weeks after the wedding, so Erik is out. — 160 → 143 people. Frees 17 seats. Choose the age by what you want the evening to be, then hold it to the date: an age policy that bends once for one twelve-year-old is not an age policy, it is a favor with a number written on it.

Age cut-offPersonalize
Example 04

POLICY 4 — CEREMONY-ONLY Ceremony · all 22 children invited Dinner and evening · none Seats freed · 22 at dinner, 0 at the ceremony — The genuine middle, and the one with a logistics bill instead of a social one. Settle the five o'clock question before you commit: twelve households need somewhere for their children to be, four of those households are traveling to get here, and childcare that does not exist by the spring is how ceremony-only turns into fully child-free in two weeks.

Ceremony onlyPersonalize

The children are the part you will type twice

Once with the whole family on the list while you work out what the policy costs, and again without them when you build the list you actually send from. Do it once here instead: put everyone on, re-tier the children in a single pass, and download the file so the version you send from is the version you decided.

Open the builder →
Before you pick one

🧮 Count the children first

Nobody should choose a children policy before counting the children, because the count decides which policies are even available. Put an age column beside the names on your own copy of the list — it is the only way to make this decision with your eyes open, and it is nobody's business but yours. Nothing typed into the builder below is stored, sent or measured either.

Example 05

CHILDREN ON THE LIST — 22 names, 12 households Sofia Alvarez · Nina 8 · Otto 5 Paloma & Tomas Alvarez · Mia 9 · Theo 6 Camila Reyes · Sol 14 · Isabel 11 · Bruno 7 Héctor Reyes · Marta 17 · Pablo 10 Diego Alvarez · Luca 2 Nico Alvarez · Elsie 4 months Priya & Sam Raman · Kiran 16 · Ravi 13 Jonah Bell · Rosie 3 Tess Okafor · Ada 5 Beck Turner · Milo 6 · Juno 4 Will & Jo Amari · Noor 8 · Sami 4 · Ida 2 Grace Lindqvist · Freya 15 · Erik 12 — 22 under 18, sitting in 12 of your 84 households. Write the ages down before you argue about the policy: most arguments about children at weddings are two people picturing a different age.

The age columnPersonalize
Example 06

EXCLUDE UNDER-18S — the recount Before · 160 people · 84 households · capacity 150 · over by 10 After · 138 people · 84 households · capacity 150 · under by 12 — Excluding under-18s frees 22 seats. That is the whole decision expressed as a number, and it belongs in front of you before anyone says the word policy: 22 seats is either the reason you can invite the cousins, or it is nothing you needed and the answer is no.

Frees 22 seatsPersonalize
Example 07

THE 22, BY CIRCLE Immediate family (your niece and nephew) · 2 First cousins · 9 Friends · 6 People whose weddings you went to · 3 Work · 2 — Where the children sit decides which policy is available. Nine of the 22 are in one circle, so "immediate-family children only" is a real option on this list. An over-12 rule, by contrast, still removes seven of those nine — nearly the same conversation in a gentler coat. Read your own distribution before you pick a policy off a list.

By circlePersonalize
Example 08

WHAT THE POLICY ACTUALLY FREES Seats removed by the policy · 22 Households likely to decline because of it · 3 — Nico Alvarez (a four-month-old), Will & Jo Amari (three children under 8), Beck Turner (traveling with two) Adult seats those households were holding · 4 Net seats freed · 26, and three friends who are not at your wedding — The arithmetic runs further in your favor than you expect, and the cost is not measured in seats. Decide whether 26 is worth those three households now, while it is still a decision, rather than in April when it is an RSVP.

The knock-onPersonalize
Example 09

THE POLICY THAT DOES NOT PAY Children on the list · 4 — Nina (8), Otto (5), Mia (9), Theo (6) Seats freed by going child-free · 4 List · 128 people against a capacity of 150 — Do not do it. Four seats you did not need is the worst price anyone has paid for a conversation with every parent they know. If your list already fits, the answer to this page's question is no, and the fastest way to know that is to count before you deliberate.

When to skip itPersonalize
Named in advance, in writing

⚖️ The exceptions worth making

A policy with no exceptions is rare, and a policy with unnamed exceptions is worse than no policy at all — because every exception granted on request teaches the next person to ask. These are the four that couples actually make, in the order they usually come up, plus the one-screen ledger that keeps them checkable.

Example 10

EXCEPTION 1 — CHILDREN OF SIBLINGS Rule · a child is invited if their parent is a brother or sister of one of us In · Nina Alvarez (8) · Otto Alvarez (5) Out · every other child on the list, with no second test and no appeal — Defined by relationship it is checkable by anyone, and a cousin cannot argue their way into being a sibling. Defined by closeness it is not a rule at all: it is a ranking of the parents, and every parent on the list will work out where they placed.

Siblings' childrenPersonalize
Example 11

EXCEPTION 2 — CHILDREN IN THE WEDDING PARTY In · Mia Alvarez (9), flower girl · Pablo Reyes (10), ring bearer Also in, necessarily · one parent each, in the room for the whole day Not in · their siblings — Theo Alvarez (6) and Marta Reyes (17) — The exception guests accept without needing a reason. Read the second and third lines before you commit: two children in the ceremony means two adults who are not free at any point in the day, and two households holding an invitation that includes one of their children and not the other.

Flower girl, ring bearerPersonalize
Example 12

EXCEPTION 3 — INFANTS IN ARMS In · Elsie Alvarez (4 months) · any baby born between now and the wedding Out · every child who walks The rule as arithmetic · a carried infant is not a seat and not a meal, so this exception costs the policy nothing — This is the exception that keeps the other 21 out. Refusing it means asking the parent of a four-month-old to choose between leaving the baby and leaving the wedding, which is the most reliable way to turn a child-free policy into two declines and one very long phone call.

InfantsPersonalize
Example 13

EXCEPTION 4 — ONE NAMED HOUSEHOLD, WITH THE REASON RECORDED Will & Jo Amari · flying from Auckland with three children under 8 · exception granted Reason, written on the row · 24 hours of travel, no family here, no childcare available to them Every other household · policy applies — Person scope, not policy scope, and the distinction is the whole game. Written down, it is one household with a reason anybody can hear. Unwritten, it is a precedent — and the next family who hears about it will arrive with a reason of their own.

One householdPersonalize
Example 14

THE WHOLE POLICY, ON ONE SCREEN Policy · no guests under 18, applied to all 84 households Exception 1 · children of siblings — Nina (8), Otto (5) Exception 2 · wedding party — Mia (9), Pablo (10), plus one parent each Exception 3 · infants in arms — Elsie (4 months) Exception 4 · Amari household, traveling from Auckland — Noor (8), Sami (4), Ida (2) Children in the room · 8 · Children not invited · 14 · Seats freed · 14 — The version most couples actually land on, and the version worth printing. Eight of the 22 are in, every one of them traceable to a written exception rather than to how you feel about their parents. When somebody asks — and somebody will — you are reading from a list instead of defending a choice.

Exception ledgerPersonalize
Person, layer, or list?

A children policy is a whole-list rule with named exceptions

Almost every children-at-the-wedding argument is a whole-list rule being applied at person level, one household at a time, until there is no rule left. Name the level each sentence belongs to and the argument mostly disappears.

1

No children at the wedding

The whole list · The list as a whole. Applied household by household it is not a policy, it is a run of favors — and the households that did not get one will have compared notes by the end of the week.

2

Children of our siblings are the exception

A whole layer · Every household in the circle. Left as "the children we're close to", it re-opens for every parent on the list who believes they qualify, and each of them is asking you to rank them.

3

The Amaris are bringing their three, because they are flying from Auckland

One person · One named individual. Explained as a general principle it repeals the policy. Recorded as one household with a written reason, it survives being repeated to anyone who hears about it.

4

Children come to the ceremony but not to the dinner

The whole list · The list as a whole. Offered to some households and not others, it is the same split as before with a later start time, and it is just as visible.

5

Your parents' 30 seats cannot be spent on children

An allocation · Each contributor's bucket. Left unsaid, a contributor fills their allocation with grandchildren and the policy is gone before you have seen their list.

This page decides the policy and stops there. The sentence that carries it on the invitation is a different craft entirely and belongs to adults-only invitation wording — there is deliberately not one example of it here. To turn the seats you free into a number of invitations you can actually send, use the wedding attendance rate, whose output is exactly the capacity number the builder above takes. Whether an adult guest's partner is on the list at all is settled by the plus-one rules, a household you would rather hold back until later belongs with second-wave invitations, and once the names are settled, collecting their numbers is the next job — this builder never asks for one.

The rules that hold up

Four rules that keep a policy a policy

Written down these are boring. Unwritten, every one of them becomes a separate conversation with a separate parent, and each conversation quietly moves the line for everybody else.

1

One rule, one list

The policy applies to all 84 households or it is not a policy. There is no version of this where your cousin's children are a judgment call and your colleague's are a rule — the second household to find out is the one that decides how it reads.

2

Exceptions are named in advance, and in writing

An exception decided before anyone asks is part of the policy. The identical exception granted after someone asks is the end of it, because it teaches every remaining parent that asking works. Write the list, keep it, and stop adding to it.

3

An age cut-off runs on the date, not on the child

Pick the age, then apply it to the wedding date and let it fall where it falls — including on the child who turns 13 five weeks later. An age rule that makes one exception for maturity has become a favor with a number painted on it.

4

Deciding it and phrasing it are two different jobs

Settle the policy first, with the count in front of you. How the decision is expressed on the invitation is a separate craft with its own page, linked in the section above — nothing on this page tries to write that sentence for you.

Common mistakes

What goes wrong with a children policy

Every one of these has been survived by thousands of couples. They are still worth avoiding, because each costs a conversation you did not need to have and usually costs it several times.

✕

Deciding it family by family

It feels like kindness and it reads as ranking. Twelve households with children will each learn what the others were offered, and the only question they will be able to answer is which of them mattered more. Decide the list, not the family.

✕

Granting the first exception to whoever asks first

The first ask is almost always the most confident person on the list, not the household with the strongest case. Once they have it, every subsequent no is measurably unfair — and you will be explaining the difference between them for months.

✕

Picking an age you have not counted against

"No children under 10" sounds like a compromise until you count and find that 14 of the 22 are under 10 anyway. If the number barely moves the list, you have paid the full social price of a policy for a fraction of the seats.

✕

Assuming everyone will come regardless

Some households will decline, and they will be the ones with the youngest children and the longest journeys. That is a legitimate price, but it should be a price you chose knowingly rather than a surprise in the second week of March.

✕

Letting the policy travel by rumor

Telling one aunt and letting it spread means twelve households hear a version of it, none of them hears the exceptions, and you spend the spring correcting a rule you already decided. Settle it, write it down, then tell people yourself.

Free, and it never leaves your browser

Put the children in their own circle and watch the number move

The list opens with the Children circle armed and two of its three children invited — exactly the split a policy exists to remove. Re-tier the whole circle in one pass, watch the seat count change, and download the file once the decision is one rule rather than a run of favors. Nothing you type is stored or sent anywhere, and there is no autosave: closing the tab loses the list, which is why the file matters.

Wedding guest list templateFree · no sign-up · runs entirely in your browser

Children sit in their own circle so a policy is one filter, applied to the whole list, instead of a run of favors.

This is how many people you can invite, not how many will come — turning one into the other is what the attendance-rate page does: to seat 100, invite 118 to 128.

5 circles are on this list. A circle is what the consistency check reads.

15

15 people in 8 householdsEveryone in tiers A, B and C is counted here; 2 people are in the not-inviting pile and stays out of the file. Set a capacity to see where the line falls.

First nameLast nameHouseholdCircleTierPlus ones
Two people with the same household label are one invitation.

Everything here runs in your browser. Nothing you type is stored or sent anywhere — there is no account, no saved list and no cookie holding your guests (we count anonymous, bucketed usage of the tool itself, never a name, a number or a list size). That also means closing this tab loses the list, which is why the button says download.

Where the line falls

  • ATier A — no wedding without them10 in this tier · 5 households · 10 with everything above it10
  • BTier B — you want them there5 in this tier · 3 households · 15 with everything above it5
  • CTier C — only if there is room0 in this tier · 0 households · 15 with everything above it0
  • Not invitingNot inviting2 in this tier · 2 households · left out of the export2
  • 2 of 3 college friends are on the list and 1 are not. Invite the layer or cut the layer — a split one is visible to everybody in it.
  • 2 of 3 children are on the list and 1 are not. Invite the layer or cut the layer — a split one is visible to everybody in it.

Downloads a CSV of everyone still on the list — tiers A, B and C, minus any tier you have switched off above. The not-inviting pile stays on this page.

✓
Keep exploring

More on deciding who to invite

Who to invite to your weddingThe whole decision, circle by circle→Friends, and who invited youReciprocity, friend groups and the honest test→Inviting coworkersThe test that keeps a team from being split→Estranged familyA named decision, made once and recorded→Telling someone they're not invitedWhat to say, when to say it, and to whom→Who to invite to a small weddingWhere the line falls at 20, 50 and 75→
Good to know

Child-free wedding questions

Should we have a child-free wedding?

Only if it buys you something you need. Count the under-18s on your list first: if excluding them frees enough seats to make the list fit, or the evening you want is genuinely not one children fit into, it is an ordinary and defensible decision. If there are four children on a list that already fits, the answer is no — you would be paying for a conversation with every parent you know in exchange for four seats.

Is it rude to have a child-free wedding?

No. Deciding who is on your guest list is entirely yours to do, and a child-free wedding is a common one. What is genuinely rude is inconsistency: inviting one family's children and not another's, or granting exceptions to whoever asks loudest. One rule for the whole list, with its exceptions named in advance, is what makes the decision land as a policy rather than as a judgment on somebody's family.

What age counts as a child on a wedding guest list?

Whatever age you write down — but write it down, and hold it to the wedding date rather than to how grown-up a particular child seems. Eighteen is the cleanest line because it needs no explaining. Twelve or thirteen is the common middle, chosen when the concern is toddlers rather than teenagers. Count before you pick: an age rule that only removes a handful of names has cost you the whole social price of a policy for a fraction of the seats.

Can we invite some children and not others?

Yes, as long as the difference is a rule and not a preference. "Children of our siblings" is a rule: it is checkable, and nobody can argue their way across it. "The children we're close to" is a ranking of the parents, and every parent on the list will work out where they placed. Write the boundary down before you say it out loud, and make the exceptions a short, closed list.

Do we have to invite our nieces and nephews?

No. Plenty of couples go fully child-free including their own family, and it is the easiest version to explain precisely because nothing is exempt. It is also the most common exception people make, and it survives well when it is defined by relationship — the child of a sibling — rather than by how close you feel to any given family.

Will people decline if we have a child-free wedding?

Some will, and you can usually predict which: households with children under five, households with no family nearby, and households traveling a long way. On the worked list on this page, three households out of twelve would likely decline, which costs four adult seats on top of the 22 the policy frees. That is a fair price for the seats — it is just worth deciding it knowingly rather than discovering it in the RSVPs.

What if a guest brings a child anyway?

That is almost always a symptom of a policy that was never clearly one — granted here, refused there, and never written down. The fix is upstream: settle the rule, name the exceptions, and make sure the households with children hear it from you rather than from each other. If it still happens, hand it to someone who is not you on the day; nobody should be negotiating their own guest list at their own wedding.

A list is names on a page.
Until you send it, that is all it is.

Build the list here, download it, and import the file into Text My Wedding — the same names then carry the invitation, the RSVP and every reminder, without anybody retyping them.

Build my guest list →
✓