We wrote this about a real Reddit thread with actual comments shared by readers in the wedding planning community.
Someone posted their wedding do-not-play list. It had 32 entries. Sweet Caroline. Mr. Brightside. I Wanna Dance With Somebody. Wannabe. Love Shack. Uptown Funk. The Electric Slide. The Cupid Shuffle. The entire genre of country. The thread generated nearly 400 comments in half a day, and the responses ranged from amused to genuinely alarmed on behalf of their dance floor.
The list is funny. It is also a useful window into a real tension that comes up at almost every wedding: the couple's taste in music versus what actually gets people out of their seats.
Why the overplayed songs are overplayed
Every song on that list became a wedding staple because it works. Sweet Caroline gets grandmothers and college friends singing together. Mr. Brightside creates a moment where everyone who went to any party in the 2000s suddenly becomes 22 again. I Wanna Dance With Somebody is an objectively great song that happens to also signal to every woman at the reception that it is time to get up. The line dances, much as they divide opinion, have one enormous advantage: everyone knows how to do them. No one has to be good. The awkwardness is the point.
These songs are overplayed at weddings because couples keep discovering that they work. That does not mean you have to play them. But it is worth understanding what you are opting out of before you opt out.
Why the dance floor goes quiet
One person in the thread shared an honest cautionary experience. She and her husband spent days building their playlist, keeping only music they genuinely loved. The dance floor was almost empty all night. Her photographer had to beg guests to come out for photos. The venue was beautiful. The food was great. But nobody moved.
"You want people to have moments where they go 'omg it's this one!' and run to the dance floor. A wedding is not the moment to say 'hey, have you heard of this cool indie band from New Zealand?'"
A wedding is not a concert where guests are there to listen to your taste. It is a party where guests want to feel welcome, have fun, and ideally do something together. Music is one of the primary mechanisms for that. When every song requires guests to not know the words, not recognize the beat, and figure out on their own whether this is a dancing song or a sitting song, many of them will just sit.
A wedding where the venue had to pull the plugs because guests refused to leave? Also in the thread. That couple's playlist had a lot of overlap with the do-not-play list above.
How to think about your playlist differently
The most satisfied couples in the thread had approached it the same way: build a playlist you love, then ask whether it will get your specific guests moving. Those are two separate questions, and the second one requires you to actually think about who is coming.
If your guest list skews young, shares your taste, and will show up ready to dance to whatever you put on, your personal playlist can carry the night. If your guest list includes parents, in-laws, older relatives, kids, and people who need a recognizable song before they will get off their chair, you are going to need at least a few anchors. A few minutes of the Electric Slide is a reasonable price for an uncle who otherwise would not have left his seat all night.
One commenter had it right: "I personally hate Cotton Eye Joe but my wife and some guests wanted it played so bad. I can suffer a little if everyone is enjoying themselves."
A smarter approach to the do-not-play list
The do-not-play list has a genuine place in your DJ conversation, just not as a substitute for a real playlist. Here is what it is actually useful for:
Songs that are personally painful. If a song is connected to a bad memory, a difficult person, or just genuinely ruins your night when you hear it, that belongs on the list. Your DJ absolutely should know this.
Songs with problematic content. Several people in the thread flagged artists whose royalties or reputations they are not comfortable supporting. That is a reasonable and clear boundary.
Songs that actively conflict with your vibe. If you are having an outdoor folk wedding, Cotton Eye Joe is probably not going to fit regardless of whether your aunt loves it. Vibe-based exclusions make sense.
The song request approach
Several couples in the thread found a middle ground that worked well: ask guests to submit a song request with their RSVP, then build the playlist primarily from your own selections but incorporate requests where you can. You still get to veto anything that really does not work. But you end up with music that your specific guests are excited to hear, and when their song comes on, they will be on the floor.
You will almost certainly get requests for songs on your do-not-play list. You are not obligated to play them. But you might find, reading through the requests, that more of your guests love Sweet Caroline than you expected. That information is worth having before the night.
Your call, your crowd
It is your wedding and you are allowed to play whatever you want. If a curated, personal playlist matters more to you than a full dance floor, that is a completely valid choice and some couples are genuinely happier with it.
But if a full dance floor matters to you too, and it usually does, then the playlist conversation is less about your taste and more about your guests. The best wedding playlists tend to be the ones where the couple took a night off from being cool and let some of the crowd-pleasers back in. Nobody remembers which songs they banned. Everyone remembers whether they danced.
Keeping your vendor notes, timeline, and guest details organized in one place makes the whole planning process smoother. MyWeddingDashboard gives you everything in one spot so the fun planning, like the playlist, stays fun.