Suno v6 Duet Prompts: Keep Each Singer on the Right Lines (2026)

Duets are where Suno v6 reports disagree the hardest. In the first two days after launch, one r/SunoAI thread carried a report of a duet converted cleanly in Simple mode and finished with a tagged Cover; another, titled "v6 is so disappointing," said duets still fail; and in a third, a commenter said the singers were finally harmonising without swapping mid-sentence. The most-cited failure of all, the 100-generation "v6 doesn't sing" post, was trying to make a slow male and female country duet. Same model, opposite results, and the difference is almost entirely in how the lyric was labelled.

This guide covers one thing: two singers, and keeping each one on the right lines. It gives you a two-singer lyric template, separates the three duet shapes that need three different prompts, a singer-to-line mapping sheet, and a straight comparison of a fresh generation against a Cover of a solo track. It does not repeat the general vocal-delivery advice, which has its own guide on v6 vocal prompts, and it does not re-cover which v6 model to use. It does cover release, because a duet that finally works is a track you will want on Spotify, and Undetectr works with Suno V6 to remove the AI watermarks distributors screen for.

Three duet shapes, three different prompts

"Make it a duet" is not one instruction. It is at least three, and v6 handles them very differently. Decide which shape you want before writing a line, because the labelling strategy changes for each.

Most real duets are a mix: alternating verses, a call-and-response pre-chorus, a harmonised chorus. That is fine. The rule is that every section uses the labelling that matches its own shape. Mixing them inside a section is what produces the random switching.

Set two distinct identities before you touch the lyric

v6 cannot keep two singers apart if they are not apart in the style prompt. "Male and female duet" gives the model two genders and nothing else, and on a genre where the registers overlap (indie folk, for example) it will drift. Give each singer a register and a texture that the other one does not have. Suno's v6 FAQ says the flagship v6 "consistently delivers polished music genres and styles" when you know what you want; that consistency depends on the description being unambiguous.

Three details in that prompt do the work. "Alto" and "baritone" put the voices in different octaves, so even a mis-assigned line is audibly the wrong singer and easy to catch. "Slight rasp" against "breathy" gives them different textures. "Chorus in close harmony" tells the model in advance that the one section where they overlap is meant to overlap. If you use a Persona or a Voices clone for one of the singers, put the description of the other one in the text anyway; the model needs the contrast.

The singer-to-line mapping sheet

Before you paste a lyric, map it. Unlabelled lines are where v6 improvises, and in a duet an improvised line means the wrong singer. The sheet below is the whole method: every section gets a shape, a singer, a register cue and a line count.

Then write it. Here is a complete original two-singer template using that map. Copy the structure and replace the words.

Notice the pre-chorus. Each line carries its own singer in parentheses, and each line is short enough that the model cannot hand it over halfway. That is the entire fix for mid-sentence swapping. The chorus uses one label for both singers and identical words. The bridge shows how to bring the second singer in partway through a section: a new tag at the join, not a parenthetical mid-line.

What the tags actually do, and what they do not

A warning that applies to every bracket in this guide: section tags are suggestions the model weighs, not commands it obeys. "[Verse 1: A]" is not a switch. It is text that, combined with a distinct identity in the style prompt and a contrasting register cue, makes the assignment overwhelmingly likely. Several syntaxes float around r/SunoAI ("[Female Verse]", "[Male:]", "[Duet]", "(A)" vs "A:"), and none of them has been documented by Suno. Treat them all as things to test on the same lyric rather than as reliable grammar.

• Test one syntax per generation. Change the tag style, keep everything else, listen for the assignment. Do not change the identity prompt at the same time or you will not know which change helped.
• Short lines beat any syntax. A five-syllable line labelled with the wrong syntax is still more likely to stay with one singer than a fifteen-syllable line labelled perfectly.
• Keep names out of it. "(Sarah)" and "(Tom)" invite the model to sing the name. "(A)" and "(B)" do not. If you use a Persona, its name in the style field is fine; keep it out of the lyric.
• Use v6, not v6-wild, for the assignment pass. Wild is built to be unpredictable, which is the opposite of what a duet needs. Sketch on v6-mini for free, then assign on v6.

That poster stacked six workarounds on one prompt. The mapping sheet approach is the opposite: one change per roll. If the singers swap in the pre-chorus, fix the pre-chorus labels and nothing else. It is slower per generation and much faster to a keeper.

Fresh generation vs Cover: two routes to the same duet

The most useful disagreement in the launch-week threads was between people generating duets from scratch and people taking a finished single-voice song and making a Cover of it with a second singer added. Both work. Both fail. They fail for different reasons and suit different starting points.

For the Cover route, the sequence that keeps coming up is: generate the solo song on v6, get the melody and the first singer right, then open Cover, keep the lyric, and rewrite only the style field so that it now describes two singers and which sections are shared. The lyric labels still matter here. A Cover with no singer labels in the lyric will usually hand the whole thing to the new voice or blend the two throughout.

For the fresh route, the mapping sheet is the whole workflow, and Studio is the safety net: if one section comes back with the wrong singer, regenerate that section rather than the song. Suno's launch material makes a point that v6 can change one section while preserving everything else. On a duet that is the feature you will use most.

Two singers, one clean file, one upload

Here is the part duet guides leave out. When the singers finally hold their lines and the chorus harmonises, you have a track worth distributing, and distributors screen AI audio before it reaches Spotify or Apple Music. The screening looks for the embedded watermarks and spectral artifacts generators leave in the file. It does not care that there are two voices. A duet that took twelve rolls can still bounce at the aggregator, and each re-export you try burns one of Pro's 20 monthly downloads.

Undetectr works with Suno V6 and removes the AI watermarks and artifacts distributors screen for, so the duet gets onto Spotify, Apple Music and the other stores without the takedown loop. It takes the MP3, WAV or FLAC Suno exports, processes the watermark layer, and returns a file that still sounds like your two singers. One payment, no subscription, and it works on any generator's output, so a Suno duet and a Udio sketch go through the same step.

The duet checklist

1. Pick the shape per section. Alternating, call and response, or harmony. Write the shape next to each section before you write a word.
2. Give the two singers different octaves and textures in the style field. Alto against baritone, rasp against breath.
3. Label every section, and every line in call-and-response sections. Keep those lines to seven syllables or fewer.
4. Sketch on v6-mini, assign on v6. Never judge singer assignment on v6-wild.
5. Change one thing per roll. Labels, then identity, then line length. Not all three.
6. Fix one section in Studio instead of re-rolling a take that is nine-tenths right.
7. Clean the export with Undetectr, upload once. The rejection guide covers what happens if you skip this step.