← Back to blog

What Is a Do Not Play List for Weddings: Create Yours

August 16, 2026
What Is a Do Not Play List for Weddings: Create Yours

A do not play list is a written blacklist of songs, artists, or genres you hand to your DJ or band before your wedding reception. Start by writing 5–15 specific items and submitting them to your vendor at least 30 days before the event. That single document, handled correctly, prevents the one song that would clear your dance floor or ruin the mood you spent months building.

Professional DJs describe it as a specific set of instructions for songs, artists, or genres that are strictly off-limits and should be treated as non-negotiable. The Knot and The New York Times have both covered the practice extensively, and Fiesta Fusion builds music collaboration into every wedding consultation for exactly this reason.

Key Takeaways

A do not play list is most effective when it is short, clearly labeled, and submitted to your vendor at least 30 days before the wedding.

PointDetails
Keep the list conciseAim for 10–15 songs plus two or three genre notes to preserve DJ flexibility.
Label every entryMark each item as a hard ban or soft caution so your vendor knows what is absolute.
Submit 30 days outGive your DJ the list at least 30 days before the wedding, then confirm 1–2 weeks out.
Designate a point personAssign your maid of honor or best person to handle on-the-night music decisions.
Document vendor agreementConfirm hard bans in writing, ideally through a client portal or signed event notes.

Table of Contents

Why couples make a do not play list

The most common reason is vibe protection. Your reception has an emotional arc, and one wrong song can snap guests out of the moment faster than a bad speech. A do not play list keeps that arc intact.

Empty wedding dance floor with festive lighting

Beyond atmosphere, couples often have personal triggers: a song from a past relationship, a track that played at a funeral, or a genre one partner genuinely cannot stand. Family dynamics add another layer. A song that feels harmless to you might carry loaded history for a parent or sibling in the room.

Then there are the overplayed wedding clichés. Songs like the Chicken Dance and Cotton Eye Joe have been played at so many receptions that hearing them can feel like a parody of a wedding rather than yours. Banning them is not being difficult. It is being specific about what your night should feel like.

DJ guidance consistently recommends keeping the list concise, typically a moderate amount of songs plus a few genre notes, because a very long blacklist limits your DJ's ability to read the room and respond to what guests actually want in the moment. The New York Times documented one couple who submitted about 300 song requests to lock in their vibe, which illustrates how far couples sometimes go but also the real trade-off between control and flexibility.

Pro Tip: Separate your hard bans from your soft cautions. A hard ban means never, no matter what. A soft caution means "use your judgment." Giving your DJ that distinction in writing saves a lot of awkward moments.

Wedding DJ Services

What to put on your list: categories and examples

Think in categories first, then fill in specific songs. This approach gives your DJ a mental framework, not just a checklist.

Hard bans are absolute. No exceptions, no guest requests, no matter how much someone tips. Soft cautions are songs you dislike but could tolerate if the DJ genuinely reads the room and the crowd is asking for it.

Common categories to cover:

  • Overplayed wedding clichés: Chicken Dance, Cotton Eye Joe, YMCA, Macarena. These songs are not bad, they are just everywhere, and many couples want their reception to feel like their own.
  • Novelty and line-dance songs: Often requested by guests who want to participate, but they can derail a carefully built energy.
  • Breakup or grief-associated songs: "I Will Always Love You" by Whitney Houston is a stunning vocal performance, but its lyrical context is goodbye. Many couples flag it for exactly that reason.
  • Explicit-content songs: Specify whether you want clean versions only or a full ban on the artist.
  • Controversial or politically charged songs: Anything that could split the room along political or cultural lines.
  • Whole-genre exclusions: "No country," "no heavy metal," or "no explicit hip-hop" are valid genre-level bans.

Songs that appear on The Knot's list of commonly avoided wedding tracks include Blurred Lines (Robin Thicke), Stayin' Alive (Bee Gees), and the Chicken Dance, alongside breakup anthems that couples often forget to flag until they hear them at someone else's wedding.

Short annotations help. Writing "Stayin' Alive — hard ban, no exceptions" is clearer than just listing the title. "Blurred Lines — no version, no remix" removes any ambiguity. Vendor guidance recommends specifying the version, remix, and whether explicit or clean labels apply, because a DJ who plays the acoustic cover of a banned song technically followed the letter of your list, not the spirit.

Ready-to-copy do not play templates

Copy whichever format fits your situation and paste it into your vendor's client portal or attach it to your planning email.

Short template (5 items, minimal control):

  • Chicken Dance — hard ban
  • Cotton Eye Joe — hard ban
  • I Will Always Love You (Whitney Houston version) — hard ban
  • Any explicit-content songs without a clean edit — hard ban
  • [Genre: heavy metal] — hard ban

Long template (15+ items with genre notes and soft cautions):

Hard bans:

  • Chicken Dance — hard ban
  • Cotton Eye Joe — hard ban
  • Macarena — hard ban
  • YMCA — hard ban
  • Blurred Lines (Robin Thicke) — hard ban, no version or remix
  • I Will Always Love You (Whitney Houston) — hard ban
  • Stayin' Alive (Bee Gees) — hard ban
  • [Song tied to personal history] — hard ban
  • Any explicit-content track without a clean version available — hard ban

Soft cautions (DJ discretion):

  • Electric Slide — only if crowd requests it organically
  • Wobble — soft caution
  • [Specific artist] — soft caution, read the room

Genre notes:

  • No country music
  • No heavy metal
  • Hip-hop: clean versions only

Practical templates like this one recommend labeling every entry clearly so vendors can act on it without a follow-up call.

When two partners have different lists, merge them by starting with hard bans both agree on, then negotiating the soft cautions. If one partner loves a song the other hates, it goes on the soft-caution list with a note: "only if both partners approve on the day."

How and when to give the list to your vendor

Timing matters as much as content. A list delivered the morning of your wedding gives your DJ almost no time to prepare.

  1. 30 days before: Submit the complete list through your vendor's client portal, as a PDF attached to an email, or in a shared Google Doc. This is the primary deadline.
  2. 1–2 weeks before: Confirm the vendor has received and reviewed the list. Ask them to flag any songs they have questions about.
  3. Day-of checkpoint: At your venue walkthrough or sound check, verbally confirm the hard bans with your DJ or band leader. Thirty seconds of confirmation prevents a lot of grief.

Vendor portals and shared Google Docs are the most reliable formats because both parties can see the same version in real time. A PDF attached to a contract email works too, but confirm the DJ has opened and read it, not just received it.

For your submission email, a subject line like "[Your Names] Wedding — Do Not Play List + Music Notes" keeps it easy to find. In the body, include one line: "Please treat all items marked 'hard ban' as absolute. Items marked 'soft caution' are at your discretion."

Also confirm these vendor policy items before the wedding:

  • Will the DJ honor hard bans even if a guest requests the song directly?
  • How does the DJ handle guest requests that conflict with the list?
  • Will the DJ confirm the final list in writing before the event?

How DJs handle guest requests on the night

Most professional DJs follow a clear hierarchy: the couple's hard bans come first, always. A guest request that conflicts with a hard ban gets declined, politely and without drama.

Common tactics vendors use to deflect unwelcome requests:

  • Telling the guest the song "isn't available in the system tonight"
  • Offering an alternative in the same genre or energy level
  • Logging the request and never playing it

Soft-caution songs are where a good DJ earns their fee. They read the crowd, gauge the energy, and decide whether the moment calls for it. That is exactly why distinguishing hard bans from soft cautions in writing matters so much.

Guest tipping is a real dynamic at receptions. A guest slipping a DJ $20 to play a banned song puts the vendor in an uncomfortable position. Professional DJs treat hard bans as absolute regardless of tips or pressure, and any vendor worth hiring will tell you that upfront.

Pro Tip: Designate a point person, your maid of honor or best person, to handle on-the-spot music decisions. Give them a copy of the list and authority to make calls so you are not pulled off the dance floor mid-reception.

Questions to ask your DJ about honoring the list

Use this checklist at your consultation or planning call:

  1. How do you store the list? Ask whether it goes into their event management software, a printed sheet, or a shared doc. You want it somewhere they cannot lose it.
  2. Are hard bans truly absolute? A professional DJ should answer yes without hesitation.
  3. How do you handle a guest who requests a banned song? Listen for a specific, practiced answer, not a vague "I'll figure it out."
  4. Will you confirm the final list in writing before the event? This protects both parties.
  5. What happens if you are unsure whether a song is on the list? The answer should be: "I check before I play, not after."

Document the vendor's answers in your contract or event notes. If your DJ uses a client portal, upload the list there and screenshot the confirmation. Fiesta Fusion includes a dedicated music planning process as part of every wedding package, covering both must-play and do-not-play coordination before the event.

Commonly banned wedding songs: a starter list

Pull from this list and delete what does not apply to you. Every couple is different.

Overplayed classics:

  • Chicken Dance — novelty, often feels dated
  • Cotton Eye Joe (Rednex) — line dance, polarizing
  • Macarena — novelty, very 1990s
  • YMCA (Village People) — crowd participation song many couples skip
  • Stayin' Alive (Bee Gees) — overplayed at receptions despite being a great song

Breakup or grief-associated songs:

  • I Will Always Love You (Whitney Houston) — lyrically about leaving
  • We Are Never Getting Back Together (Taylor Swift) — obvious reasons
  • My Heart Will Go On (Celine Dion) — associated with the Titanic, a tragedy

Explicit-content songs:

  • Blurred Lines (Robin Thicke) — explicit lyrics and cultural controversy
  • WAP (Cardi B) — explicit, often flagged for mixed-age crowds
  • Closer (Nine Inch Nails) — explicit, not suitable for family receptions

Controversial or divisive tracks:

  • Any song with strong political messaging
  • Songs with lyrics that reference specific cultural or religious groups in a negative way
CategoryExample SongsSuggested Label
Overplayed classicsChicken Dance, Cotton Eye Joe, YMCAHard ban or soft caution
Breakup/grief songsI Will Always Love You, My Heart Will Go OnHard ban
Explicit contentBlurred Lines, WAPHard ban or clean version only
Novelty/line danceMacarena, Electric SlideSoft caution

The Knot's curated list of 26 commonly avoided wedding songs is a useful starting point for building your own version. Personalize it: a song on someone else's hard-ban list might be your must-play, and vice versa.

A do not play list works best as part of a broader music planning system, not as a standalone document.

  • Must-play list: The positive counterpart to your DNP list. These are songs you want played at specific moments: first dance, cake cutting, last song of the night. Give this to your DJ at the same time as the DNP list.
  • Guest request filtering: Some vendors offer a portal where guests can submit requests in advance. You review them before the event and approve or reject each one. This removes the awkward on-the-night dynamic entirely.
  • Genre-level bans vs. item-by-item bans: Genre bans are faster to write and easier for DJs to follow. Item-by-item bans give more precision but require more effort. Use genre bans for categories you feel strongly about and item bans for specific songs with personal significance.
  • Playlist curation links: Attaching a Spotify playlist of songs you love gives your DJ a sonic reference point, not just a list of what to avoid. It is one of the most useful things you can send alongside your DNP list.

Letting guests request freely with vendor moderation is a middle-ground approach. The upside is a more spontaneous dance floor. The downside is that without a clear DNP list in place, a banned song can slip through. If you go this route, make sure your hard bans are locked in the vendor's system before any guest requests are even considered.

For a deeper look at how entertainment choices affect music control, the wedding entertainment options guide covers the difference between live bands and DJs and how each handles playlist restrictions.

The part most wedding advice gets wrong

Most articles treat the do not play list as a formality, something to dash off and forget. That framing undersells it. The list is actually one of the clearest signals you send your DJ about who you are as a couple and what kind of night you want.

The conventional advice says: keep it short, be polite, trust your DJ. That is mostly right, but it skips the harder truth. The couples who get the most out of this tool are the ones who think through the why behind each entry, not just the what. Banning Chicken Dance because everyone bans it is different from banning it because you genuinely want a sophisticated, uninterrupted dance floor. The first is reflexive. The second gives your DJ real context.

The other thing most guides miss: the do not play list is a conversation starter, not a final decree. Your first draft should go to your DJ before your planning meeting, not after. That way the list becomes a reference point for a real discussion about your vision, your guests, and the moments that matter most. A DJ who reads your list and asks follow-up questions is a DJ who is paying attention.

The couples who end up disappointed are usually the ones who either handed over a 200-item blacklist that paralyzed their vendor, or handed over nothing and assumed the DJ would figure it out. The sweet spot is a tight, annotated list delivered early, followed by a real conversation. That combination, more than any specific song choice, is what makes a reception feel intentional.

Sources

Consult your booked vendor's music portal or contract terms directly, since policies on guest requests and hard ban enforcement vary by company.

FAQ

What is a do not play list for a wedding?

A do not play list is a written document you give your DJ or band listing songs, artists, or genres that are off-limits at your reception. Hard bans are absolute; soft cautions give the vendor discretion based on the crowd.

What songs are most commonly banned at weddings?

The most frequently flagged songs include Chicken Dance, Cotton Eye Joe, Macarena, YMCA, Stayin' Alive, I Will Always Love You, and Blurred Lines. Breakup anthems and explicit-content tracks also appear on many lists.

When should I submit my do not play list?

Submit it at least 30 days before your wedding, then confirm receipt 1–2 weeks out. A brief verbal check-in at the venue sound check adds a final layer of confirmation.

How many songs should be on a do not play list?

DJ guidance recommends 10–15 specific songs plus two or three genre-level notes. Lists that run much longer can limit your DJ's ability to read the room and respond to what guests actually want.

Will a DJ always honor a do not play list?

Professional DJs treat hard bans as absolute, regardless of guest requests or tips. Confirm this policy in writing before your event, ideally documented in your contract or client portal.