Suno v6 Intro and Ending Prompts: Unwanted Humming, Long Outros and Cut-Off Lyrics (2026)

The edges of a Suno v6 track are where the small failures live. A creator in the "Opinions of v6" thread on r/SunoAI reported asking the model to remove the humming from an intro and getting more humming. The "Unofficial Suno v6 Prompting Guide" posted the day after launch listed cut-off lyrics as one of its recurring problems and proposed explicit instrumental boundaries as the fix. Long outros that will not end, a song that stops mid-line, a guitar in an intro that was meant to be drums only: none of these is a quality problem. They are boundary problems, and they have their own fixes.

This guide is about the first and last twenty seconds. It gives you three original opening and ending templates you can paste, shows how to use the documented Exclude field for the things you do not want at the edges, and gives you a decision tree for when to fix the prompt, when to use Exclude, when to edit in Studio, and when to just regenerate. It does not cover the middle of the song: verse arrangement is in the rock prompts guide and vocal delivery in the vocal prompts guide. It does cover release, because a track with clean edges is one you will upload, and Undetectr works with Suno V6 to remove the AI watermarks distributors screen for.

The four boundary problems creators report on v6

The thread that ties these together is that v6 fills silence. An intro with no instruction is a space the model populates from the style prompt, and a vocal is the most "musical" thing it can put there. An ending with no instruction is a chorus it can repeat. The fixes all amount to the same move: describe the boundary explicitly enough that there is nothing left to fill.

Use Exclude, and stop arguing with the prompt

The single most useful thing to know about intros on v6 is that negative instructions in the style field do not work the way you want. "No humming," "no vocals in the intro," "without piano" all put the unwanted word into the text the model is generating from, and with Variety above zero that text can be rewritten anyway. Suno provides a separate field for this. Its help article on excluding elements describes the steps: start a Custom Mode song, open Advanced Options, and enter "any information (instruments, etc) that you do not want in your track" in Exclude.

A day after the v6 launch a creator posted a list of exclusion words they had found useful in exactly this field ("the style exclusions section of More Options of advanced mode") and reported it had made a real difference to their results. The specifics vary by genre, but for boundary problems the list is short and consistent.

Exclude is a fence. It stops the model reaching for something; it does not put anything in its place. Pair it with an affirmative intro instruction in the lyric box, which is the second half of the fix and the subject of the templates below. Also worth checking while you are in Advanced Options: the Variety slider. If it is above zero, Suno's v6 FAQ says it will be "adjusting and updating your style prompts," which can reintroduce exactly the elements you excluded. Our guide to the v6 controls covers that in full.

Three opening and ending templates

Each template is a matched pair: an [Intro] tag and an [Outro] tag with an explicit instruction, meant to be pasted at the top and bottom of your lyric. Replace the instruments with your own. The bar counts are suggestions the model weighs rather than exact measures, but stating them consistently produces intros and outros of consistent length, which is the point.

Template 1: instrumental bookends (most tracks)

Clean edges, easy to edit in Studio, and the intro names what plays (drums and bass) as well as what does not (vocals). If you want a melodic intro, name the one instrument: "(instrumental, 4 bars, single electric guitar, no drums, no vocals)." The word "only" in the drums-and-bass version does a lot of work; without it the model treats the list as a minimum.

Template 2: cold open, hard stop (pop, hip-hop, hook-driven songs)

The cold open is the surest way to kill an unwanted humming intro, because there is no intro. Starting on the chorus also tends to make the model commit to the hook. The outro instruction names three things not to do; on a hard stop that redundancy helps, because "hard stop" on its own is sometimes read as "stop, then a short tail."

Template 3: long tail (ambient, post-rock, ballads)

This is the template for tracks that want a long outro, and it is also the answer to the long-outro complaint: the problem was never that the outro was long, it was that it had no shape. "Repeat the last line twice, softer each time" gives the model a destination. The stated fade length gives it a stopping point.

Fixing a cut-off lyric

A lyric that stops mid-line is a length problem, and the fix is arithmetic rather than tags. v6 generates a fixed maximum length per take. If your final section has six lines and the song reaches the limit after three, the model stops. It will not speed up to fit them in, and it will not shorten the intro to make room.

• Count the lines in the last two sections. If the song is cutting off, remove lines from the final section first, not the first verse. Four-line final choruses cut off far less than six.
• Add an explicit [Outro] tag with a stated length. It tells the model where the end is before it gets there, so it paces the last chorus to arrive at the outro rather than running out of road.
• Shorten the intro if the outro is what you care about. Every bar of instrumental intro is a bar the last section does not get.
• If the take is otherwise right, extend it in Studio rather than regenerating. A cut-off ending on a good take is a section edit, not a new song.

One caveat that applies to every bracket in this guide: section tags are suggestions the model weighs, not commands it obeys, and they are not a cure for a generation that failed for other reasons. If a take is wrong in the middle as well as at the edges, no [Outro] instruction will save it. Regenerate.

Prompt it, exclude it, edit it, or regenerate?

Four possible fixes for a boundary problem, and they are not interchangeable. Use the cheapest one that matches the cause.

The Studio route matters more than it used to because of the download caps. Pro is 20 downloads a month and every exported re-roll is one of them. Trimming a long outro or replacing a cut-off ending inside Studio, then exporting once, is the workflow that keeps you under the cap. The caps and plan details are in the v6 vs v5.5 comparison.

Clean edges, clean file, clean upload

The ending is also where distributors notice a bad export, and even a good one gets screened. DistroKid, TuneCore and the aggregators behind Spotify and Apple Music look for the watermarks and spectral artifacts AI generators embed in the file. A track whose intro and outro are finally right can still bounce at the aggregator, and the rejection loop is where the download cap gets spent on nothing.

Undetectr works with Suno V6 and removes the AI watermarks and artifacts distributors screen for, so your music gets onto Spotify, Apple Music and the other stores without the takedown loop. It takes the MP3, WAV or FLAC that Suno exported and returns a cleaned file with the intro, the outro and everything between exactly as you approved. One payment, no subscription, and it works on any generator's output.

The boundary checklist

1. Every lyric gets an [Intro] and an [Outro] tag with an explicit instruction, even if the instruction is "none."
2. Unwanted elements go in Exclude, never as a "no" in the style field.
3. Name what plays and what does not in the intro instruction. "Drums and bass only, no vocals."
4. Give the outro a shape and a length. A final line, a repeat count, a fade in bars, or a hard stop.
5. Cut-off lyric: remove lines from the last section first.
6. Good take, bad edge: fix it in Studio, export once.
7. Clean the export with Undetectr and upload once. The distribution guide covers the rest.