Is it rude to send someone your wishlist?

Updated 11 September 2026

Almost everybody who makes a gift list hesitates before sending it. The hesitation is reasonable, and the honest answer is not a flat "no, go ahead" — it depends on who asked, how the list arrives, and whether it reads as an offer or an invoice.

The short answer

Sending a list because somebody asked what you want is not rude. It is simply the answer to a question, and a straight answer saves the other person a fortnight of guessing and a receipt they would rather not need.

Sending a list nobody asked for, to people who were not planning to buy you anything, is where it goes wrong. Notice that the list is never the problem. The problem is a list arriving as though the gift had already been agreed.

Nearly every awkward case sits between those two poles, and the difference is usually a single sentence of framing. The rest of this guide is about that sentence.

When it genuinely lands badly

Five situations account for most of the discomfort people report. They are worth knowing because four of them are easy to avoid.

• Nobody asked, and no occasion was in view. A list that turns up in March, unprompted, reads as a request for presents rather than an answer about them.
• It went to everybody at once. A link broadcast to a whole contact list reads as a collection. The same link sent to the four people who actually asked reads as helpfulness.
• Everything on it is expensive. A list with nothing under the price of a dinner tells people who cannot spend that much that they are not really invited to give anything at all.
• It arrived with instructions. Sizes and colours are useful. A deadline, a delivery address and a note about wrapping turn a list into an order form.
• There is no graceful way to ignore it. If the sender will obviously notice that you did not take anything from the list, the list has become an obligation.

The last one is the only structural problem on that list, and it is the one people rarely think about. It is also the one a well-built list can actually solve, which is the subject of the final section.

Let people ask — then answer quickly

The cleanest route is to have the list ready and not send it until somebody asks. Somebody almost always does, usually two or three weeks before the occasion, and usually in a hurry.

When they ask, answer immediately and lightly. Speed is what makes it read as convenience rather than campaign: a list that appears within a minute of the question is obviously something you already had, not something you assembled in response to being offered a present.

If nobody has asked and the occasion is genuinely approaching — a wedding, a new baby, a milestone birthday where people are visibly planning — you can raise it yourself. Say what the list is for, and say plainly that nothing is expected. Both halves matter. The first stops it reading as a demand; the second is the part people skip.

What to actually say

The wording below is deliberately plain. Each one is short, names the reason the list exists, and leaves the other person an obvious way to do nothing. Copy one and change the names.

One habit worth adopting: never send the link on its own. A bare URL with no sentence around it is the version that reads coldest, and it is the version most people send.

Sending a list on a child’s behalf

This is the case where almost nobody objects, and where lists do the most good. Relatives buying for a child they see three times a year are guessing about sizes, reading ages and what the child already owns, and they usually know it.

The etiquette is the same, with one addition: make the price range obvious and wide. Grandparents and a colleague who is fond of your family are not in the same position, and a list that runs from a paperback to a bicycle lets both of them choose without asking you what is appropriate.

Keep the child out of the sending. A list written by a parent and shared by a parent is a practical arrangement. A message that appears to come from a six-year-old asking for a bicycle is a different document entirely.

Prices change how a list reads

More perceived rudeness comes from the shape of a list than from the act of sending it. The table below is the pattern worth checking before you share.

The last row is the one people resist and the one that matters most. A list with a genuinely inexpensive thing on it — a book, a jar of something, a plant — tells everyone reading that the list is about what you like, not about what they spend.

Why a list people can reserve from is the least rude kind

Return to the one structural problem: a list becomes an obligation when the sender can see exactly who took what, and who took nothing.

A list where guests reserve privately removes that. Visitors can see which gifts are already taken, so nothing is bought twice, but the person whose list it is never sees any of it — not who reserved, not what is gone, only how many things are still free. On this site that is enforced on the server rather than hidden in the page, so the owner’s own view of their list cannot leak a reservation even through view-source.

That asymmetry is what makes the list read as an offer. Nobody is being counted. Somebody who looks at the list and decides to bring a bottle of wine instead has left no trace, and the person who made the list is never in the position of noticing.

It also removes the reason most people give for not sending a list at all: the fear of watching people respond to it. If you cannot see the responses, there is nothing to watch.