Sending someone adult material is a social act with rules nobody writes down, which is why it goes wrong so often. Most of the awkwardness is avoidable and comes from three specific omissions: not asking, not explaining, and not thinking about where the message will land. None of this is prudishness. It is the same consideration you would apply to any other thing you send someone unprompted.
Ask before the first one
The first time is the one that matters. A single question — do you want me to send you this kind of thing — sets the terms permanently and takes ten seconds. After that you both know where you stand and nobody has to guess.
People skip it because asking feels more awkward than sending. It is not; it is briefly awkward instead of persistently awkward, and it transfers the choice to the person who has to receive it. That is the whole principle in one sentence.
The same reasoning that makes consent central to what is depicted in this work applies to how it is passed around, which is worth noticing.
Context is a courtesy
A bare reference asks the recipient to do the work of finding out what you sent. Add a title, an artist, and one line about why you thought of them. Now it is a recommendation instead of a dare, and it is far more likely to actually get read.
The line about why is what makes it personal rather than transactional. Something reminded you of them, or of a conversation you had, or of a thing they said they liked. That is the actual content of the message; the reference is just the attachment.
It also lets someone decline gracefully. Knowing what something is means they can say not my thing without opening it, which is the outcome everyone wants and which a bare number makes impossible. The receiving side of this is on checking before you open a reference.
Timing and channel
Messages arrive somewhere. A phone on a desk at work, a laptop shared with a partner, a tablet a child sometimes uses, a smartwatch that shows previews on the wrist. You do not control where your message surfaces, and a preview is enough to cause a problem.
So keep it to channels you both use for this, avoid working hours by default, and never put a description in a preview-visible first line. These are small adjustments that prevent an entire category of genuinely bad moments.
Group chats deserve extra care. A room where one person enjoys this and four do not is not a place for it, however friendly the group is.
What not to send at all
Anything crossing the hard lines is not a joke, a test, or a prank: material involving minors, real-person likenesses, or coercion presented approvingly should be reported rather than forwarded. Sending it to someone as a bit makes them a recipient of something they may have to deal with.
That standard does not shift for humour or for shock value, and it is the one stated on the understanding of this house.
Receiving well, too
The etiquette runs both ways. If somebody sends you something you did not want, saying so plainly once is better than silence followed by resentment. Most people adjust immediately, because they were not trying to impose anything.
Silence is the common response and the worst one, because the sender reads it as neutral and keeps going. A single sentence closes the loop and costs nothing, and almost nobody takes it badly when it is said plainly rather than left to build up.
And if you liked it, say why. That is how a shared taste develops into actual conversation rather than a stream of links, which is more or less the point of having someone to share this with.
Sharing a reference without the awkwardness
Ask once. Add a title and a reason. Think about where the message lands. Report rather than forward anything over the line. Four habits, each taking seconds, and they cover nearly every way this goes wrong.
What you share should meet the same bar as what you read: fictional adults, unmistakably grown, credited makers, nothing scraped. The record-keeping that makes recommending easy is on building an index you actually keep.