How to Convert Suno v4.5 Prompts to v6: A Working Guide for Style and Lyrics Prompts

On September 9, 2026, Suno switched off every model older than v6, and in the same afternoon my folder of carefully tuned v4.5 style prompts turned into a folder of pretty good suggestions. Prompts that had reliably produced a specific groove, a specific singer, and a specific mix for a year suddenly came back with different energy, a different vocal, and sometimes a different genre entirely.

Here is the short answer if you only read one paragraph. Do not paste your old tag clouds into v6 and hope. Rewrite each v4.5 style prompt as a production brief in a fixed order, identity first and exclusions last, keep it under 1,000 characters, move every “when does this happen” instruction out of Style and into the Lyrics box as scoped section headers, and set Variety to 0 while you test so Suno doesn’t rewrite your prompt behind your back. That is the whole method. The rest of this guide is how to do each of those things well, where v6 will still fight you, and what to do when it does.

What Actually Changed When v6 Replaced Everything Older

Suno’s own announcement, Introducing v6 by Mikey Shulman, describes the release as a new generation of models developed with Warner Music Group, BMG and Believe, split into three variants: v6 as the flagship for Pro and Premier subscribers, v6-wild for exploration, and v6-mini as a faster version available to everyone. The same post says previous models would be retired as v6 rolled out, and that happened fast. As the Suno Help Center’s own FAQ confirms, every model before v6 is now retired, and new iterations of older songs run on the v6 family.

The mechanics that matter for prompt conversion are these. According to the Suno v6 FAQ, generations cost the same as before, ten credits for a pair of songs, while Max Mode costs more and is recommended for songs over two minutes, close covers, style transfer, and keeping vocals and style consistent across the whole track. The same FAQ explains that the Variety slider works by adjusting and updating your style prompt, and that if you want full control of your style tags you set it to 0. That single sentence explains a lot of the confusion people had in the first week, because an engineered prompt at any Variety setting above zero is not the prompt Suno actually used.

Character limits held steady. Third party API documentation for the v6 family, such as the sunoapi.org generate music reference, lists the Style field at a maximum of 1,000 characters and the lyrics field at 5,000 characters for v6, v6-mini and v6-wild, the same ceilings v4.5 and v5.5 had. So the box didn’t shrink. What changed is how much the model reads into each clause, which is exactly why a prompt built for v4.5 behaves differently now.

Early reactions were split. Boing Boing’s roundup of mixed reviews for Suno’s new model noted that v6 follows prompt specifications more closely and nails genre hallmarks, while a write-up at suno.hk found that reusing v5.5 prompts could change a track’s energy and genre entirely, that some styles came out muddy or buried the vocal, and that v6-wild drifted more on long tracks. Both observations are correct, and they are two sides of the same coin. A model that listens harder to your words punishes sloppy words harder.

The One Principle That Makes the Whole Conversion Work

Everything in this guide hangs on a single division of labor that I now treat as law. The Style prompt defines what the track is. The Lyrics prompt defines what happens when. If an instruction describes something true for the entire song, it lives in Style. If it describes a change at a particular moment, it lives in a section header inside Lyrics.

This is the core idea behind the community converter rules published on r/SunoAI by a user who built a two part rulebook for feeding into a language model, part one on style prompts and part two on model limits and diagnostics. I have been using a version of that workflow since launch, and the parts of it that survive contact with real generations are the parts I’m going to walk through here, filtered through what has and hasn’t worked on my own tracks.

The practical consequence of the principle is inheritance. Every section of your song inherits the global Style prompt. A section header only overrides the parameters it explicitly names, and everything it doesn’t mention keeps flowing from Style. Once you internalize that, half of your old prompt problems dissolve, because you stop writing “soft intimate verse” and start writing “vocals softer and closer, groove unchanged.”

Step One: Read the Old Prompt as Intent, Not as Text

The worst thing you can do with a v4.5 prompt is translate it word for word. Those prompts were tag clouds because v4.5 rewarded tag clouds. Half the words in them were there as insurance, repeated synonyms stacked up because one of them might land. In v6 every one of those words gets read, and the ones that don’t change a real musical decision are at best noise and at worst a genre pull you never asked for.

So the first step is to sit with the old prompt and ask what it was trying to get. Not what it says. What it wanted. A v4.5 prompt that reads “epic cinematic dark emotional powerful female vocals orchestral acoustic guitar strings piano tribal drums building anthemic 90 bpm haunting beautiful voice reverb” is really asking for maybe five things. A folk ballad with orchestral weight. A female singer who starts low and ends high. Acoustic guitar and cellos carrying the harmony. Tribal percussion as the engine. A build that pays off in a final chorus. That is the musical intent, and that is what you convert.

While you’re doing this, flag every word that does no work. “Beautiful voice” changes nothing. “Emotional” changes nothing. “Reverb” by itself tells the model nothing about what should be wet or how wet. Those get deleted, not translated. Then flag the words that do too much work, the ones I think of as gravity wells, which get their own section below. And flag contradictions, because v4.5 prompts are full of them and v6 will not resolve “intimate” and “anthemic” for you in the way you hoped.

The Eight Slots of a v6 Style Prompt, in Order

After a month of testing, the structure I use for every Style prompt is a fixed sequence of eight slots: identity, then pulse, then voice, then instruments, then arrangement arc, then mix, then emotion, then exclude. The order isn’t decorative. The model reads front to back, and the things that define the track should be the things it reads first, so that when it runs out of attention it has already committed to the right identity and groove.

Identity comes first and means one primary genre plus at most two supporting genres, each with a stated job. “Cinematic folk ballad as the foundation, chamber orchestration supplying harmonic weight, tribal percussion supplying the rhythmic engine” tells the model who is in charge. “Folk, orchestral, tribal, cinematic” tells it nothing about hierarchy and invites it to average the four into mush. If a genre only contributes one behavior, skip the label and write the behavior.

Pulse comes second and always means three things together: a BPM, a time signature, and a rhythmic feel. BPM alone is not enough, because v6 treats a number as a hint rather than a transport setting. “90 BPM, 4/4, straight eighths with a half-time feel in verses and full-time floor toms from the first chorus” reinforces the number with groove behavior, and in my experience that is what actually locks tempo. I have had far more tempo accuracy from describing the subdivision than from stating the number twice.

Voice comes third and gets treated as an instrument with a mechanical description. Type, register, timbre, chest or head balance, breathiness, articulation, vibrato, backing vocal behavior, and where it sits in the stereo picture. The single most useful conversion I make here is replacing “powerful” with register language, because “powerful” tends to raise loudness without raising pitch range, while “low-mid chest voice in verses, climbing phrase by phrase into a bright head-mix for choruses, highest sustained notes reserved for the final chorus” gives the singer an actual journey. Keep the vocal identity separate from vocal processing, so that a filter or a touch of distortion in one section doesn’t silently become a different singer.

Instruments come fourth, written as instrument plus function. “Fingerstyle acoustic guitar carries the harmonic pulse, low cellos drive a repeating ostinato, piano answers vocal phrases, floor toms and frame drums lock to the kick.” Each important instrument gets one or two jobs. Not every instrument gets to be important, and no instrument gets asked to be at full intensity all the time. If you catch yourself writing what looks like a full orchestration score, you have gone too far and the model will start dropping instructions at random.

Arc comes fifth and describes one energy journey across the song, stated in terms of what actually changes. Not “builds to an epic finale” but “verses sparse, choruses add violins widening the stereo image, bridge strips to voice and piano, final chorus adds layered backing vocals and fuller strings without raising master loudness.” Recurring song-wide behavior lives here. One-off events live in Lyrics.

Mix comes sixth and is one or two decisive relationships, not a console session. “Vocal clearly foregrounded, guitar and cellos yield beneath it.” That’s often all you need. Emotion comes seventh, as a progression rather than an adjective, something like “evoking grief that hardens into resolve,” and it stays subordinate to everything above it. Exclude comes last, every unwanted element written with a dash glued directly to the front of the term and no space, and it counts against your 1,000 characters.

A Worked Conversion, Start to Finish

Let me take that folk prompt from earlier and show the full before and after, because the shape matters more than any individual rule.

The v4.5 source prompt was this. Epic cinematic folk, dark, emotional, female vocals, powerful, orchestral, acoustic guitar, strings, piano, tribal drums, building, anthemic, 90 bpm, haunting, beautiful voice, reverb. Seventeen tags, no hierarchy, three gravity wells, and two words that do nothing.

The v6 Style prompt I converted it into reads as follows. Cinematic folk ballad as the foundation, chamber orchestration supplying harmonic weight, tribal percussion supplying the rhythmic engine, 90 BPM, 4/4, straight eighths with a half-time feel in verses and full-time floor toms from the first chorus. Female lead, low-mid chest voice in verses, breathy but close-miked and foregrounded, climbing phrase by phrase into a bright head-mix for choruses, highest sustained notes reserved for the final chorus. Fingerstyle acoustic guitar carries the harmonic pulse, low cellos drive an ostinato, piano answers vocal phrases, floor toms and frame drums lock to the kick. Verses sparse, choruses add violins widening the stereo image, bridge strips to voice and piano, final chorus adds layered backing vocals and fuller strings without raising master loudness. Vocal foregrounded, guitar and cellos yield beneath it, stable perceived loudness across the track. Evoking grief that hardens into resolve. Then the exclude list, each term with a dash in front: male vocals, synths, trap hi-hats, EDM drops, autotune.

That comes in just under the 1,000 character ceiling with the exclusions included. Notice what happened to each of the original tags. “Epic” and “cinematic” and “anthemic” collapsed into a foundation genre plus a concrete arc, because those three words together are the fastest way to get a generic trailer score with a shouting singer. “Dark” and “haunting” became a harmonic and emotional progression rather than tempo instructions, because in v6 “dark” has a habit of slowing things down. “Powerful” became register movement. “Reverb” disappeared, replaced by “close-miked and foregrounded” so the vocal stays present even while breathy. “Building” became a section by section description of what builds.

The one thing I want you to resist in your own conversions is adding detail just because there is room. The question for every clause is whether removing it would materially change the music. If not, cut it. A prompt at 700 clean characters outperforms a prompt at 990 padded ones almost every time I’ve tested the two side by side.

Genre Gravity Wells, or Why Epic Ruins Your Mix

Certain words in v6 do far more than they appear to. I call them gravity wells, and the converter rules name the usual suspects: heavy, doom, operatic, screaming, epic, cinematic, industrial, ambient, aggressive, anthemic. Each of these carries a whole bundle of conventions the model has learned to associate with it, and dropping one into an otherwise careful prompt can drag the entire generation toward a stereotype you didn’t ask for.

The fix is to replace the label with the mechanism. Instead of “heavy,” write that low guitars play dense palm-muted eighth notes with a hard transient attack. Instead of “operatic,” write that the singer uses a high sustained head-mix with wide vibrato and formal legato phrasing. Instead of “cinematic,” say what you actually want, which might be sustained low strings, a wide stereo image, and a slow harmonic rhythm. You get the sound without the baggage, and you get to keep the parts of the stereotype you like while dropping the ones you don’t.

This is also the single biggest reason old v4.5 prompts misbehave in v6. Those prompts leaned on gravity wells on purpose, because v4.5 needed the strong pull to commit to anything. In v6 the pull is still strong, but the model is now also reading all your other instructions, so you end up with a tug of war between “operatic” and “intimate close-miked vocal” that neither side wins cleanly. Pick the behavior, write it, and let the label go.

Intensity Is Not One Knob

The most common structural mistake I see in converted prompts, and the one I made most in my first week, is treating energy as a single dial. It isn’t. Vocal intensity, rhythmic intensity, subdivision speed, note density, harmonic density, transient strength, register, layer count, distortion, stereo width, and dynamic level are all separate, and v6 is capable of moving them separately if you tell it to.

The old habit was to write “big chorus” and let the model decide which of those eleven things got bigger. In practice that meant the chorus got louder, slower, broader, and simpler, which is the default pop move and often the wrong one. If what you actually want is a chorus that feels faster without changing tempo, you write that the subdivision doubles, the riff gets more notes per beat, and the syncopation tightens. If you want a chorus that feels bigger without getting louder, you write that violins enter, backing vocals widen, and the register rises, with perceived loudness held stable.

The flip side matters just as much. Soft vocals do not imply weak drums. Dark harmony does not imply slow tempo. A melodic, intimate vocal can sit on top of an abrasive, dense accompaniment, and some of the best tracks I’ve gotten out of v6 do exactly that. But you have to say so, because left alone the model will let one adjective bleed into unrelated dimensions. That’s why “vocals softer and closer; drums and bass keep the established driving groove” appears so often in my Lyrics headers. It isn’t paranoia. It’s scoping.

Writing the Register Journey for Vocals

If your old prompts had a wide range singer, you probably noticed v6 either staying in one register the whole song or jumping high in the first chorus and never coming back down. Both are fixable, and the fix follows the Style and Lyrics split exactly.

In Style, define the available range. Something like “wide tessitura, low-mid verses, bright upper mix, high sustained peaks” tells the model what the singer can do. In Lyrics, define where the register actually moves. Verse low-mid, pre-chorus rising, chorus high, bridge back to low, final chorus highest. Write it as relative movement rather than exact octaves. “Climb phrase by phrase into a higher tessitura” has been far more reliable for me than “sing one octave higher,” which v6 treats as a vague suggestion at best.

The step people miss is the return. After a high chorus you have to restate the lower register in the next section, or the singer stays up there for the rest of the song. I add a line like “vocals return to low-mid register, same tone and placement” at the top of the second verse and the bridge. Keeping “same tone and placement” in that line matters, because without it the model sometimes interprets a register change as a license to change the singer’s identity, and you end up with two different vocalists in one song.

Converting the Lyrics Prompt: Headers Are Instructions, Not Labels

In v4.5 a lot of us used section tags as labels and little more. A bracketed Verse, a bracketed Chorus, maybe a bracketed Bridge, and the lyric text underneath. In v6 the header is where the arrangement actually happens, and converting a Lyrics prompt means turning those labels into concise behavioral instructions with the most important change first. In the Lyrics box, each of the example lines below sits inside the usual square brackets. I’m leaving the brackets out here so the text reads cleanly.

Verbs beat adjective piles. The ones I reach for constantly are enter, drop, strip, rise, widen, sustain, rebuild, return, collapse, open, peak, fade, hold, answer, pulse, climb, and cut. “Chorus: violins enter and widen the stereo image, vocal climbs into head-mix, floor toms move to full-time” is an instruction. “Chorus: big, emotional, soaring” is a hope.

Verses stay structurally focused and inherit the global groove unless you say otherwise. If the verse vocal is meant to be quiet, scope it. “Verse 1: vocals close and low-mid; drums and bass keep the established groove.” Pre-choruses have to state what builds. Rising harmony, doubled subdivision, longer vocal phrases, additional backing vocals, wider stereo field, more bass motion. Pick one or two and name them. The word “building” on its own is the lyrics equivalent of “powerful” in Style, a request for something without saying what.

Choruses need the exact form of escalation written out, for all the reasons in the intensity section above. Bridges and breakdowns need genuine contrast, which means naming what leaves, not just what softens. “Bridge: drums and percussion stop completely; exposed vocal and piano only; cellos sustain without movement” produces a real breakdown. “Bridge: quieter” produces a slightly quieter verse. Solos need the featured instrument named, its job stated, and both the entry and the exit defined, because a bare Solo tag is a coin flip. And the final chorus gets its specific escalation spelled out: higher register, wider backing vocals, additional counterpoint, fuller harmony, more layers, with master loudness explicitly held, never just “bigger.”

Two more rules that saved me a lot of credits. Keep one-off effects local and define their exit, something like “Transition: short radio-filtered vocal phrase, then immediately return to the normal clean vocal tone,” because a filter instruction without an exit has a way of persisting across the whole second half. And when the task is conversion, leave the lyric text itself alone. Change the headers, change the formatting if it helps phrasing, but don’t rewrite words that were already working.

Here is the skeleton I converted the folk ballad into, headers only, so you can see the journey without the lyrics in the way. Intro: fingerstyle guitar and low cello ostinato only, no drums. Verse 1: vocals close and low-mid, frame drums enter softly, half-time feel. Pre-Chorus: piano answers each vocal phrase, cellos rise, vocal climbs phrase by phrase. Chorus: floor toms move to full-time, violins enter and widen, vocal in bright head-mix. Verse 2: vocals return to low-mid register, same tone and placement; groove unchanged. Pre-Chorus: as before, add low backing vocal hum. Chorus: as before. Bridge: drums and percussion stop completely, exposed vocal and piano only, cellos sustain. Final Chorus: full band returns, layered backing vocals widen, vocal reaches highest sustained notes, strings fuller, perceived loudness stable. Outro: strings and percussion drop out, guitar and cello ostinato fade.

Read only those headers and you can hear the song. That’s the test. If you can’t trace where energy rises, where it falls, where register moves, where instruments enter and leave, and what stays constant, the Lyrics prompt isn’t done yet.

The Settings That Make Testing Honest

Here is where a lot of conversion work gets undone. You write a careful Style prompt, you generate, the result ignores half of it, and you go back and rewrite the prompt. But if Variety was sitting at its default, the prompt you wrote wasn’t the prompt Suno ran. The v6 FAQ is plain about this: Variety introduces variety by adjusting and updating your style prompt, and only at 0 do you keep full control of your tags. An open issue in the bitwize claude-ai-music-skills repository tracking the v6 changes reports confirming on camera that at any setting above Off, Suno rewrites the Style box differently on every take, and that an engineered Style box is only used verbatim at Variety Off. That matches what I see in the song details after each generation.

So I separate prompt testing from creative variation, and I change one variable at a time. Moe Lueker’s Suno V6 guide, based on around 150 songs, makes the same two recommendations I’d make: set Variety to 0 when you’ve written a detailed style prompt so you can judge the prompt before adding another variable, and match Style Influence to how specific you were, higher for a precise sound and lower when you want room to explore. The table below is the workflow I settled on. Treat the numbers as starting points, not laws.

Max Mode deserves its own note because it changes the credit math. The same GitHub issue quotes the in-app description as using more compute to maximize consistency throughout the song at double the credits, which puts a Max Mode generation at twenty credits for the pair instead of ten. Suno’s FAQ says it is best for songs longer than two minutes, close covers, style transfer, and keeping vocals and style consistent through the whole track, and that standard mode is enough for quick ideas and shorter songs. I agree with that, and I’d add one thing: Max Mode is not a repair tool for a muddled prompt. Develop the direction first on standard mode, then spend the double credits on the candidate you actually want to keep.

On cost, since every one of these passes burns credits. As of late September 2026, according to Undetectr’s Suno plan comparison checked against suno.com/pricing, Free is $0 with 50 credits a day and v6-mini only, Pro is $10 a month or $96 a year with 2,500 credits a month, and Premier is $30 a month or $288 a year with 10,000 credits a month, all before tax. The same source lists UK pricing at £8 and £22 a month and eurozone pricing at €9 and €28, so readers outside the US should expect slightly different numbers on the checkout page. Lumi Music’s pricing breakdown notes that since September 3, 2026, downloads are capped at 7 lifetime on Free, 20 a month on Pro, and 60 a month on Premier, with no cap for Premier users exporting from Suno Studio. That download cap matters for conversion work more than you’d think, because iterating toward a keeper is cheap in credits but every version you want to pull into a DAW to audition properly costs a download.

One more cost note. Commercial use rights only come with the paid plans, and a track made on Free isn’t something you can release. That’s unchanged from v5.5, but worth remembering if you’re doing early control passes on a free account and planning to switch later: the keeper has to be generated on the paid plan.

When It Is the Model and Not Your Prompt

The hardest discipline in all of this is knowing when to stop rewriting. Better prompting improves compliance, but it cannot force behavior the model doesn’t reliably synthesize, and the temptation when a generation fails is to add more words. More words make the next generation worse, because v6 has a limited budget of attention and every clause you add competes with the ones that matter. The converter rules call this instruction competition, and I’ve watched it happen in real time: a prompt that nailed the groove at 600 characters lost it at 950 once I added mix detail nobody asked for.

The sequence I use when something fails repeatedly is symptom, then probable cause, then a simplified test, then a targeted correction, then an honest call on whether this is a model limit. If a behavior works in a stripped-down arrangement but fails in the full one, competition is the likely cause and the fix is to cut secondary instructions. If it fails even in isolation, you’re probably looking at a limitation, and the move is to regenerate the section, replace it, or fix it in post rather than add a fourth synonym.

Here are the failures I hit most, what tends to cause them, and what I do about each.

Loudness creeps up and the second half sounds squashed, with transients gone and everything louder than the first verse. This is progressive gain drift, and in my experience it is mostly a model behavior rather than a prompt error. Requesting stable perceived loudness, preserved transient headroom, and arrangement-based rather than loudness-based escalation reduces it. Deleting cumulative instructions like “bigger every section” or “maximum power throughout” reduces it more. It never fully goes away on long tracks, and when it persists I regenerate the back half rather than keep rewriting.

The singer starts as one person and ends as another, or the vocal stays high after the first chorus and never comes down. That’s vocal identity drift and register drift, and both respond to the register journey described earlier: define the range globally, move it locally, and restate the lower register with “same tone and placement” after every climb. Max Mode helps here on release candidates. If the identity still wanders on a track longer than four minutes, I accept that and stitch sections.

The groove simplifies when the vocal gets quiet, or the tempo seems to sag when the harmony gets darker. That’s parameter bleed, the model letting one adjective affect dimensions it shouldn’t. Counter it by positively restating what must stay fixed in the same header, and only where bleed is actually happening. Don’t restate every global parameter in every section or you’re back to instruction competition.

An instrument you defined carefully vanishes in the bridge or changes job in the second chorus. That’s instrument-role instability. Reinforce the role at the transition where it drops, using function language, “low cellos continue driving the ostinato,” rather than listing the instrument again. If it still drops after scoped reinforcement, it’s a limitation, and I let the DAW fix it.

The chorus starts two bars early or the bridge bleeds into the final chorus. Section boundaries in v6 are approximate. When a transition has to be obvious, give it an audible structural event: drums cut completely, bass drops out, one-beat silence, full band returns. Labels alone don’t draw hard lines, and neither do bar counts, which v6 treats as soft targets no matter how precisely you write them.

A one-off effect, a filtered phrase or a radio voice, never goes away. Keep temporary effects in Lyrics, never in Style, and write the exit in the same header as the entry. If it persists anyway, regenerate just that region.

The removal instruction gets treated as a volume dip. “No drums” or “silence” sometimes comes back as quieter drums. Reinforce true removal through the surrounding arrangement: “drums and percussion stop completely; exposed vocal and piano only.” If it still refuses after that, don’t add contradictory wording. Note it, move on, and cut the drums yourself later.

Across all of these, the one thing I never do anymore is quietly swap the song’s identity for something easier. If v6 struggles with a soft vocal over dense accompaniment, the answer is to make the accompaniment yield in the mix, not to replace the dense accompaniment with a strummed guitar. Model limits don’t invalidate the musical idea. They just tell you which part of the idea you’ll be finishing by hand.

Repairs, Remaster, and Not Propagating Rot

Once the prompt is stable and the generations are mostly right, the remaining problems are usually local, and the biggest workflow mistake I see is treating a mostly good song as a failed one. A generation with a perfect first two minutes and a degraded last minute contains a perfect first two minutes. Preserve it. Use it as the reference for the next extension or edit, and never let the damaged region be the material the next pass builds on, because that teaches the model that the collapse was part of the song.

Before you regenerate anything, separate structural problems from presentation problems. A structural problem is the wrong composition, the wrong section behavior, the wrong singer, a broken arrangement, or a transition that didn’t happen. A presentation problem is a good performance rendered with a muddy mix, slightly smeared instruments, or dull top end. These need different tools, and using the presentation tool on a structural problem wastes credits and a download.

For presentation problems, Remaster is worth testing. According to the Suno Help Center’s Remaster article, the feature creates subtle variations of a clip when you’re happy with the structure, lyrics and performance but want to refine how it sounds, and since v5 it has a Variation strength control where Subtle stays very close to the original and changes only small acoustic and production details. That is exactly the layer you want for a keeper with a slightly wrong balance or unclear pronunciation. The same article is clear that Remaster isn’t intended for changing lyrics or drastically altering the style, so don’t expect it to fix a wrong arrangement or a wrong vocalist. I run one Subtle pass, compare on headphones I trust, and stop. Stacking remasters tends to move the song further from the version I liked.

For structural problems, regenerate the section and nothing else, using the clean material as your anchor. And for the stubborn cases, the ones where v6 can’t be made to hold a particular drum pattern or a particular vocal register across four minutes no matter what you write, the honest answer is sometimes that the AI version is a demo. Rebuilding the track in a DAW, or having real players re-record it from the AI arrangement, is one legitimate way to get the version you actually hear in your head, and it has the side benefit of giving you a recording whose ownership is a lot less complicated than a generated file. I don’t say that as a pitch. I say it because I’ve spent more credits than I’d like trying to prompt my way past a limitation that a session drummer solved in twenty minutes.

The Checklist I Run Before I Spend Credits

The two part converter rulebook ends with long final checks for Style and Lyrics, and I’ve trimmed them down to the questions that actually catch my mistakes. For Style: is there one clearly dominant identity and no more than three genres, each with a job? Is the order right, identity through exclude? Is it at or under 1,000 characters including the exclusions? Does the pulse have BPM, meter, and feel? Is the singer described mechanically with a stated range? Does every important instrument have a function? Is there one arc that says what changes? Is there a clear mix hierarchy? Is the emotion a progression? Are all negatives in Exclude rather than written as “no male vocals” in the positive text? And the one that catches the most: if I deleted this clause, would the music change?

For Lyrics: can I read only the headers and hear the song? Does every section inherit from Style except the parameters it names? Does any vocal instruction accidentally rewrite the arrangement, or any emotional word accidentally slow the drums? Does the pre-chorus name what builds? Does the chorus name its exact form of escalation? Does the bridge remove things rather than just soften them? Does the final chorus escalate through specific dimensions with loudness held? Do effects have exits? Are counts and key changes reinforced with musical behavior? Is the original lyric text untouched?

For settings: is Variety at 0 for this pass? Did I change only one variable since the last generation? Am I using Max Mode on a candidate, not on a diagnosis? And am I about to rewrite the prompt for a problem that is really a model limit?

What to Do This Week

Pick three old v4.5 prompts: one that always worked, one in a genre v4.5 struggled with, and one with a strict structure or BPM requirement. That spread is the same migration test AI Reiter suggests in their v6 review and migration guide, and it’s a good one because each prompt fails differently. Convert each one using the eight slot order, cutting everything that doesn’t change a musical decision, and moving every “when” into scoped Lyrics headers.

Then run a control pass on each: v6, Variety at 0, Style Influence around 85, Max Mode off. Compare the style text in the song details against what you wrote to confirm it ran verbatim. Listen for the specific things your prompt asked for, in order of priority: identity, pulse, voice, instrument roles, arc, mix. Note what held and what didn’t. Fix one thing per regeneration. When you’ve got a version where the first five priorities hold, save that version, turn on Max Mode, and run the final pass.

Keep a running file of what survived conversion and what didn’t. Generative model behavior changes, sometimes between weeks, and the techniques that convert Suno v4.5 prompts to v6 cleanly today will need revalidating when the next point release lands. The principle underneath them won’t change, though. Style is what the track is. Lyrics is what happens when. Write it that way and most of the fight goes away.

Sources

• Suno, Introducing v6: https://suno.com/blog/introducing-v6
• Suno Help Center, v6 FAQ: https://help.suno.com/en/articles/13924481
• Suno Help Center, Remaster: https://help.suno.com/en/articles/8105281
• r/SunoAI, How to convert style prompts from v4.5 to v6: https://www.reddit.com/r/SunoAI/comments/1wgb1yl/how_to_convert_style_prompts_from_v45_to_v6/
• r/SunoAI, Suno V6 Prompt Converter Rules, Part 2: Model Limits, Diagnostics and Final Checks: https://www.reddit.com/r/SunoAI/comments/1wj4b7w/suno_v6_prompt_converter_rules_part_2_model/
• sunoapi.org, Generate Music: https://docs.sunoapi.org/suno-api/generate-music
• 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/
• GitHub, bitwize-music-studio, Update the plugin for Suno v6: Variety, Max Mode, download caps, retired models: https://github.com/bitwize-music-studio/claude-ai-music-skills/issues/562
• Moe Lueker, Suno V6 Guide: What’s New, Pricing and How to Prompt It: https://moelueker.com/blog/suno-v6-guide
• suno.hk, Suno V6 Is Live: What the New Model Actually Changes: https://suno.hk/blog/suno-v6-now-available/
• Boing Boing, Mixed reviews for AI music generator Suno’s industry approved new model: https://boingboing.net/2026/09/16/mixed-reviews-for-ai-music-generator-sunos-industry-approved-new-model.html/amp
• Undetectr, Suno Pricing 2026: Free vs Pro vs Premier, Which to Buy: https://undetectr.com/blog/suno-free-vs-pro-vs-premier
• Lumi Music, Suno Pricing in 2026: Credits, Downloads, and Commercial Rights: https://lumimusic.ai/blog/suno-pricing
• SiliconSense, Suno v6 controls: Max Mode, Variety, Personalize explained: https://siliconsense.club/guides/suno-v6-controls
• AI Reiter, Suno v6 Review: Upgrade or Forced Migration?: https://aireiter.com/blog/suno-v6-review-tested-migration-guide