Suno v6 Prompts: The Complete Guide With Copy-and-Paste Examples

I wasted most of an afternoon and a few hundred credits when Suno v6 dropped, because I kept feeding it the same short tag lists I had been using since v4.5. The results were fine. They were also flat, generic, and nothing like what the model can actually do.

Here is the short answer before we go deep. Suno v6 prompts work best when you treat the style field like a production brief, not a keyword dump. Describe genre, tempo, instrumentation, vocal character, and production feel in specific, concrete language, keep song structure in the lyrics box with bracketed section labels like [Verse] and [Chorus], and put anything you want gone in the Exclude Styles field. v6 is far more literal than older models, which means vague prompts get vague songs and specific prompts get surprisingly professional ones.

In this guide I will walk through how v6 reads your prompts, a template you can adapt, six copy-and-paste prompts I would actually use, and the iteration habits that save credits. I make music with these tools every week, I rebuild the good ones in my DAW, and I have released AI assisted tracks through regular distributors, so everything here comes from doing it, not from theory.

What Changed in v6 and Why Your Old Prompts Feel Off

Suno launched the v6 family on September 9, 2026, and it was less an update than a reset. According to Suno’s own v6 FAQ, every model before v6 has been retired. Your old songs still play, but anything new you generate runs on one of three models: v6, v6-wild, or v6-mini. It is also the first Suno generation trained in partnership with major rights holders, with Warner Music Group, BMG, and Believe involved in the release, which matters more for the legal side than the creative side, but it tells you how seriously Suno is treating this generation.

For prompting, three changes matter most.

First, v6 is literal. Earlier models would take a loose prompt like “chill pop song” and fill in the blanks with their own averaged taste. v6 does much less of that guessing. If you say nothing about vocals, you get whatever vocals the model feels like. If you say “soft male vocal, close mic, slightly raspy in the low register,” you get something very close to that. The model rewards specificity in a way v4.5 simply did not.

Second, v6 reads longer, richer descriptions. The style field holds 1,000 characters and the lyrics field holds 5,000, and an audit of 251 popular shared prompts found that the median community prompt uses only around 220 characters, about a fifth of the available space. Those short tag lists were written for older models. v6 responds better to full descriptive sentences that read like you are briefing a session band.

Third, v6 understands musician vocabulary. Suno said at launch that the model reads more of the language musicians actually use, from instrumentation and arrangement terms to mood and era references, and coverage of the launch backs that up. Terms like “gated reverb drums,” “fingerstyle guitar,” “stacked harmonies,” or “dry drum mix” land reliably now. That is the single biggest reason specific prompts beat generic ones in this version.

Where Every Instruction Belongs

Most bad v6 results I see come from people putting the right information in the wrong box. The first decision is mode. Simple Mode takes one conversational description and lets v6 invent the lyrics and structure for you, and in this generation it is genuinely capable, since you can now reference multiple inputs, including your own earlier Suno songs, audio uploads, and even images, in a single request. I use Simple Mode when I want the model to surprise me. For everything in this guide, though, switch Custom Mode on. Custom Mode is what separates your musical direction from your words, and it gives you three distinct places to direct a song, each with its own job.

The Style field is your sonic identity. Genre and subgenre, tempo, key instruments, vocal type and character, mood, era, and production notes all live here. This is the persistent DNA of the whole track. If something should be true for the entire song, it belongs in Style.

The Lyrics field carries your words plus the song’s map. Bracketed labels like [Intro], [Verse 1], [Pre-Chorus], [Chorus], [Bridge], and [Outro] tell v6 where sections begin, and you can attach short local cues to a label, like [Chorus - wider harmony, stronger drums]. These are commonly called metatags, and the convention is simple: square brackets only, never parentheses or curly braces, because bracketed text gets read as instruction rather than as words to sing. The guides at Jack Righteous on Suno metatags make a point I would underline twice: tags are signposts, not software commands. They influence the generation, they do not guarantee it, and the fix for a weak chorus is usually better chorus lyrics or a sharper local cue, not five more adjectives.

The Exclude Styles field is where unwanted elements go. If a genre keeps dragging in an instrument or habit you hate, name it here. Exclude works best for removing meaningful conflicts, like keeping acoustic ballads out of an EDM prompt, not for micromanaging. One warning from experience: do not write negatives inside the Style field itself. Writing “no drums” in Style often does the opposite, because the model latches onto the word drums. Either omit the word entirely and reinforce the opposite, something like “solo piano, completely beatless, rubato,” or put drums in Exclude.

One more placement rule that trips up almost every beginner. If you write planning notes next to your lyrics without brackets, v6 will happily sing them. I have heard a model perform the line “make this part more emotional” with full conviction. Keep the lyrics box to two things only: words you want sung and bracketed labels or cues.

A Prompt Template That Actually Fits v6

The template below is the one I keep pinned. It descends in priority order, because v6, like earlier versions, weighs what comes first in the style field most heavily. SONIQ’s prompt guide recommends keeping prompts under roughly 800 characters so the important material sits up front, and that matches my results exactly. You have 1,000 characters, but you do not owe the box a full word count.

Style field, in this order:

Genre and subgenre first. Not “pop” but “synthpop” or “bedroom pop.” Not “rock” but “desert rock” or “2000s pop-punk.”

Tempo second. A number works better than a word. “92 BPM” beats “mid-tempo,” though both are read.

Core instruments third, three to five of them, named precisely. “Fingerstyle acoustic guitar, upright bass, brushed drums” tells the model far more than “guitar, bass, drums.”

Vocal character fourth, or the word instrumental. Gender, register, texture, delivery. “Female vocal, warm and breathy, mid register, close mic.”

Mood and era fifth. “Melancholic, nostalgic, 2010s indie production.”

Production notes last. “Analog warmth, light tape saturation, spacious reverb on vocals, dry drums.”

Lyrics field: your words under bracketed section labels. A dependable default map is [Intro], [Verse 1], [Pre-Chorus], [Chorus], [Verse 2], [Pre-Chorus], [Chorus], [Bridge], [Final Chorus], [Outro]. Keep verses at four to eight lines and choruses at four to six. Line breaks matter too: v6 reads blank space as musical space, so an empty line creates a breath and two empty lines create a longer pause or transition.

Exclude Styles: anything that keeps sneaking in. For a stripped folk song, I usually exclude “EDM, trap, autotune.” For an instrumental, excluding “vocals” alongside writing “instrumental” in Style is belt and suspenders, and worth it.

Copy-and-Paste Prompts You Can Use Today

These six cover the requests I see most often. Paste the Style text into the style field, use the structure notes in your lyrics box, and swap in your own words. I have run variants of all of them on v6; I will note where the model tends to wobble.

1. Warm acoustic folk.

Style field: Acoustic folk, 74 BPM, intimate and nostalgic. Fingerstyle acoustic guitar, soft harmonica, light shaker, upright bass low in the mix. Female vocal, warm and breathy, mid register, close mic. Campfire feel, natural room sound, unpolished and honest, minimal effects.

Lyrics structure: [Intro - solo guitar], [Verse 1], [Chorus], [Verse 2], [Chorus], [Outro - guitar and hum fading]. Exclude: drums kit, pop production, autotune.

Watch for: v6 sometimes over polishes folk. If it comes back too clean, add “slight pitch drift, fingers audible on strings” to the production notes.

1. Upbeat modern pop.

Style field: Upbeat pop, 124 BPM, bright and summery, radio ready. Shimmering synth leads, crisp electronic drums, round bass guitar, subtle piano stabs. Male vocal, clear and confident, lifting to a higher register in the chorus, stacked harmonies on the hook. Polished modern production, wide stereo chorus, punchy and compressed.

Lyrics structure: [Intro - drums and synth], [Verse 1], [Pre-Chorus - rising tension], [Chorus - full width, layered vocals], [Verse 2], [Pre-Chorus], [Chorus], [Bridge - stripped back], [Final Chorus - biggest moment]. Exclude: acoustic, ballad, rap.

Watch for: if the chorus does not lift, the problem is usually that your verse and chorus lyrics have the same density. Shorten the chorus lines and add repetition before touching the style prompt.

1. Lo-fi chill instrumental.

Style field: Lo-fi hip-hop instrumental, 82 BPM, relaxed rainy afternoon mood. Soft felt piano, mellow electric bass, dusty slow drum loop, faint vinyl crackle, warm and slightly muted. Steady throughout, no vocals, no sudden changes, gentle sidechain breathing on the pads.

Lyrics field: leave it empty with instrumental toggled on, or just [Intro], [Main loop], [Variation], [Outro]. Exclude: vocals, EDM drops, trap hi-hats.

Watch for: this is the easiest genre to prompt and the hardest to make interesting. Ask for one featured texture, like “a short melodic motif on muted trumpet every eight bars,” or every generation will sound like every other lo-fi track on the internet.

1. Emotional piano ballad.

Style field: Piano ballad, 62 BPM, heartfelt and dramatic. Grand piano only, spacious hall reverb, lots of air between phrases. Female vocal, tender but powerful, restrained in the verses, opening up with real intensity in the chorus. Expressive rubato timing, dynamics from near silence to full voice.

Lyrics structure: [Intro - soft piano], [Verse 1 - quiet, close], [Chorus - swelling], [Verse 2 - even quieter], [Chorus - stronger], [Outro - piano fading]. Exclude: drums, strings, synths.

Watch for: “grand piano only” is a claim the model will test. If strings creep in, move them to Exclude; that fixes it nearly every time.

1. Retro synthwave.

Style field: 1980s synthwave, 116 BPM, neon, cinematic, nostalgic. Analog style retro synths, gated reverb drums, driving eighth note bassline, atmospheric pads underneath. Male vocal, smooth and slightly distant, light chorus effect. Analog warmth, tape character, wide and glossy.

Lyrics structure: [Intro - pads and arpeggio], [Verse 1], [Chorus], [Verse 2], [Chorus], [Instrumental - synth solo], [Final Chorus], [Outro]. Exclude: modern EDM, trap, acoustic.

Watch for: the instrumental tag is where v6 shows off. Give it a cue like [Instrumental - soaring lead synth solo over driving drums] and it will usually deliver something you would keep.

1. Dark storytelling trap.

Style field: Melodic trap, 140 BPM, minor key, dark and cinematic. Haunting bell melody, booming 808 bass, crisp rolling hi-hats, sparse atmospheric pads. Male vocal, half sung half rapped, confident and low, tight doubles on key lines. Modern polished mix, heavy low end, moody.

Lyrics structure: [Intro - bells only], [Verse 1], [Hook], [Verse 2], [Hook], [Bridge - beat drops out], [Hook], [Outro]. Exclude: pop punk, acoustic, happy.

Watch for: write the hook as two to four short repeatable lines. Long hooks in trap come out as a third verse with a label on it.

Treat all six as starting points. The point of the template is that once you understand the priority order, you can write a better prompt for your song than anyone else can hand you.

Picking Between v6, v6-wild, and v6-mini

The v6 family is three models, and the one you pick changes what kind of prompt works. The flagship v6 follows instructions most precisely, v6-wild deliberately takes more risks and surprises you, and v6-mini is the fast, free sketchpad. An early hands-on review at eesel describes v6 as the reliable one and v6-wild as the experimental sibling, and that matches my experience: wild is where I go when my own idea feels too safe, not when I know exactly what I want.

Access depends on your plan. v6-mini is available to everyone including free users, while v6 and v6-wild require a paid subscription. As of this writing, Suno Pro costs $10 per month and Premier costs $30 per month, with discounts on annual billing, 2,500 monthly credits on Pro and 10,000 on Premier, and commercial use rights only on the paid tiers. Prices and credit amounts change, so check the pricing page before you commit.

My honest workflow: sketch the idea on v6-mini until the lyrics and rough feel are right, then move the refined prompt to v6 for versions worth keeping. Free tier output does not carry commercial rights, so anything you plan to release needs to be generated on a paid plan anyway.

How I Iterate Without Burning Credits

The thread of advice I trust most in the Suno community is also the simplest: change one thing at a time. If a generation is close but wrong, resist the urge to rewrite the whole prompt. Change the tempo, or one instrument, or one vocal descriptor, regenerate, and listen for what moved. Rewriting everything at once teaches you nothing, because you cannot tell which change did what.

v6 adds a tool that changes this loop completely: section editing in plain language. You can now tell the model to rework one verse, swap the chorus instrumentation, or replace a vocal line while leaving the rest of the track alone, where previously an edit risked re-rolling the entire song. When the bones of a track are right and one section is weak, edit the section. Do not regenerate a whole song to fix a bridge.

Two settings are worth knowing because almost nobody mentions them. Max Mode tells v6 to spend more compute on a single generation when you want its best shot, and the Variety slider controls how much the model rewrites your style prompt behind the scenes. SONIQ’s documentation of the Variety setting notes that at zero, your prompt is kept exactly as written, while higher values introduce variation. When I have spent twenty minutes on a precise prompt, Variety goes to zero. When I am fishing for ideas, I raise it or jump to v6-wild instead.

Watch your credit spend too. Max Mode and the add-on features cost more than plain generations, and one detailed breakdown of v6 costs found that the ratio of generations to actual released songs is where most people’s credits quietly disappear. The cure is the sketch-then-commit workflow above, plus a rule I hold myself to: if three consecutive one-change iterations do not improve the track, the problem is my concept, not my prompt, and I walk away from it for a day.

References deserve a mention here too, because they are the quiet superpower of this generation. v6 can take an existing piece of audio, one of your older Suno songs, or a playlist as the starting point for something new, and it reads the feeling behind a reference rather than cloning it outright. In practice this means your best past generations become raw material: feed a track whose groove you loved into a new request with a fresh style brief, and you keep the feel while changing everything else. The line I hold myself to, and that I would urge on anyone releasing music, is to use references to explain your own idea, never to ask the model to recreate somebody else’s finished record. Beyond the ethics, prompts built on someone else’s hit tend to come back as weaker copies anyway, because you are competing with the original in the model’s memory instead of giving it something new to build.

A side note on using a chatbot to write your prompts, which has become a common workflow. It works, and it is a sensible way to turn a plain description of a mood into a dense style brief, especially if you ask for a specific character budget so you can still edit by hand. Just read what it hands you before pasting. Chat models love contradictions like “relaxed yet driving” and love padding a prompt with fifteen instruments, and both of those sink v6 generations for reasons we are about to cover.

Mistakes That Waste Generations

After a year of watching my own failures and everyone else’s shared prompts, the same handful of mistakes come up constantly.

Vagueness. “A nice upbeat song” gives v6 nothing to be literal about, so it averages its way to the most generic thing imaginable. Every vague noun in your prompt is a decision you are handing to the model. Say what kind of nice.

Contradictions. “Super fast and relaxing” or “minimal and epic” forces the model to split the difference, and the split is always mushy. Pick one primary energy level per song. If you genuinely want contrast, put it in the structure instead: a quiet verse cue and a big chorus cue, in the lyrics field, where contrast belongs.

Overloading instruments. List fifteen instruments and v6 will honor three of them and ignore the rest, and you will not get to choose which three. Three to five core instruments, named precisely, beats a full orchestra pit every time.

Burying the lede. The model weighs the front of the style field most heavily, and the community compiled Suno field guide also documents that adherence within a generation is strongest in the first thirty to sixty seconds of the song itself. Put your genre and defining instrument first in the prompt, and front load the elements you care about most.

Forgetting to say instrumental. If you want no vocals, say so explicitly in the style field and consider excluding vocals too. Left unsaid, v6 adds vocals more often than not.

Singable instructions. Any unbracketed text in the lyrics box is fair game to be sung. Brackets or nothing.

Fighting yourself across fields. If Style says “lush strings,” Lyrics says [Bridge - strings swell], and Exclude says “orchestral,” you have built a contradiction machine. When results get confusing, the fix is usually fewer instructions that agree, not more instructions that argue.

Chasing a bad seed. Sometimes a generation is simply a dud, and no amount of prompt surgery saves it. Two or three generations of the same prompt cost less than an hour of denial. If none of them have the spark, change the concept.

When a Prompt Cannot Fix It

I want to close with the part most prompt guides skip, because trusting a guide that pretends prompting solves everything will cost you money later.

A great v6 prompt gets you a great sounding generation. It does not get you a master that stands next to commercial releases, and it does not change what the track legally is. Suno’s output typically needs loudness and EQ work before distribution, and under current US Copyright Office guidance, purely AI generated music cannot be registered for copyright protection, because registration requires human authorship. Your Suno subscription gives you commercial use rights under Suno’s terms on a paid plan, which is a license, not the same thing as owning a registered copyright in the recording. For background listening or content beds that distinction rarely matters. For a song you believe in, it does.

Every v6 output also carries audio watermarking and fingerprinting, which is part of how distribution of v6 tracks works at all now, and it means your track is identifiable as AI generated regardless of how it sounds. Some creators do not care. Some platforms and sync libraries do.

If a track matters enough that ownership and sound quality are the point, you have two honest paths. One is to treat the Suno generation as a demo and rebuild it yourself in a DAW with real recorded parts. The other, if you do not play or produce, is to have real musicians re-record the song from your AI demo, which produces a new human performed recording you can register and release cleanly. Either way, the prompt skills in this guide still matter, because the better your AI demo, the better the blueprint for the real version.

Most of your tracks will not need any of that. They need a specific style brief, a clean structure map, one change at a time, and the patience to learn what v6 does with your words. Write one prompt tonight using the template above, generate it on v6-mini, fix one thing, and run it again. That loop, repeated, is the whole skill. Suno v6 prompts are not magic words to collect; they are a production language to learn, and it is a language you can get conversational in within a week.

Sources

• Suno Help Center, v6 FAQ: https://help.suno.com/en/articles/13924481
• i-SCOOP, Suno v6 explained with new models, features and licensed music: https://www.i-scoop.eu/suno-v6-explained-with-new-models-features-and-licensed-music/
• Rook Knows, The Best Suno Prompts After v6: 24 Rewrites and a 251-Prompt Audit: https://roo.beehiiv.com/p/best-suno-prompts-v6
• Rook Knows, Suno v6 Is Live: Every Feature and the 96% Credit Trap: https://roo.beehiiv.com/p/suno-v6-features
• eesel, Suno v6 review: are the new AI music models worth it?: https://www.eesel.ai/blog/suno-v6-review
• AI Musicpreneur, Suno v6 Release Date: v6, v6-wild and v6-mini Are Live: https://www.aimusicpreneur.com/ai-tools-news/suno-v6-v6-wild-v6-mini-launch/
• SONIQ, Suno Prompts That Actually Work in v6: Style, Tags & Limits: https://www.mysoniq.com/blog/suno-prompts
• Jack Righteous, Understanding Suno AI: A Comprehensive Guide to Metatags: https://jackrighteous.com/en-us/blogs/guides-using-suno-ai-music-creation/understanding-suno-ai-a-comprehensive-guide-to-metatags
• AI Music Daily, Suno Prompt Tags: The Complete Reference for v6 Structure and Style: https://aimusicdaily.com/suno-prompt-tags
• GPT Prompts, Suno Pricing in 2026: Free, Pro, and Premier Plans Compared: https://gptprompts.ai/suno-pricing
• GitHub (mttkllr), Suno Field Guide: https://github.com/mttkllr/suno-field-guide