Where to Put Suno Prompts in V6: Styles vs Lyrics, Simple vs Custom
Gary WhittakerInside Suno V6 · Part 5
Prompting Explained: Simple vs Custom, Styles vs Lyrics
Prompting in Suno V6 is not a contest to write the longest description. The useful skill is knowing how much control you need, putting each instruction in the right place, and changing one meaningful variable when the result misses.
Verified against official Suno documentation · November 13, 2026
START HERE · FIELD PLACEMENT
Where should your prompt go?
Simple mode: Describe the whole song in one prompt. Use it for a fast concept or a detailed direction without managing multiple fields.
Custom mode: Separate your instructions by job—global sound in Styles, performed words and short local cues in Lyrics, and exclusions or influence choices in their own available controls.
Reggae-rock with deep bass, distorted guitar, raspy male lead and gospel choir accents.
[Verse]
Original lyrics go here.
[Final Chorus – full band, choir responses]
Original chorus goes here.
This is guidance, not deterministic code. Suno v6 can also follow richer Simple-mode prompts and supported references.
Get the Free Prompt Foundation GuideBest for
Turning musical intent into usable direction.
Main job
Tell Suno what matters without making every field compete.
Watch for
Prompt problems that are actually model, structure or slider problems.
Next step
Edit the keeper instead of restarting everything.
Start with the right mode
Simple and Custom are two different jobs
Suno still gives you a fast description-first path and a more deliberate field-by-field path. In V6, Simple mode can accept surprisingly detailed direction, including richer instructions and multiple references. Custom mode is still the clearer choice when you want to separate lyrics, Styles, advanced settings and title into distinct controls.
Use Simple when the idea matters more than the setup
Describe what you want to hear and let Suno interpret the request. This is useful for quick concepts, mood-first creation and testing an idea before you need to manage every field.
Example: “A smoky late-night reggae soul song with deep male vocals, restrained drums and a chorus that opens into gospel harmonies.”
Use Custom when you need separation and diagnosis
Custom gives you dedicated space for your own lyrics, Styles and Advanced options. That separation matters once you need to know whether the problem is the writing, the global sound, a local section cue or a separate control.
Operator rule: if you need to diagnose the miss, Custom usually gives you cleaner evidence.
V6 changes the ceiling, not the principle. Suno says V6 understands more musician-language across vocals, instrumentation, structure, mood, references and feel. That means you can communicate more complex intent—but clarity still matters if you want repeatable testing.
CURRENT SUNO · VERIFIED NOVEMBER 13, 2026
What v6 changes about prompting
Choose the workflow first
Simple can use detailed instructions and supported combinations of songs, playlists, audio, images or video. Custom gives you separate Lyrics, Styles and advanced settings for deliberate control and easier diagnosis.
Official v6 FAQ →Lock your test conditions
v6-mini is available on all plans; v6 and v6-wild require Pro or Premier. Record the selected model. Keep Variety at 0 when holding style tags fixed; Max Mode costs more credits, so do not change it during a prompt comparison.
Model selection →Source file first, sound prompt second
Suno's November 4 MIDI upload workflow uses Simple mode on desktop web for Pro and Premier. The MIDI sets the notes and timing; the prompt describes instruments, genre, mood and energy. Do not assume Custom-mode fields appear in this workflow.
MIDI Create help →Control availability can differ by model, plan and workflow. Check the Create interface before relying on a setting, and change one variable at a time.
The 20-second field map
What goes in Styles vs Lyrics?
Genre / overall sound
Styles
Militant reggae rock, heavy bass, distorted guitar
Vocal character
Styles
Deep raspy male lead, urgent delivery
Mood / instrumentation
Styles
Defiant, cinematic, live drums, low strings
Words actually performed
Lyrics
Your verse, chorus, bridge and ad-libs
Song sections
Lyrics
[Verse], [Chorus], [Bridge]
One-section direction
Lyrics / local cue
[Final Chorus – choir responses, full intensity]
Something you do not want
Exclude / dedicated control
trap hi-hats, country twang
Length / influence / vocal-gender controls
Dedicated control when available
Duration, influence settings, Vocal Gender
The goal is not a bigger prompt. It is a clearer job for every field. If Suno already gives the job its own setting, use that control instead of hiding the same instruction inside a paragraph.
Muffled vocals, generic output, prompt misses, identity drift, artifacts or wasted credits? Use the free 5-minute JR Rescue Path to diagnose the problem first, then choose the right next move.
Open the Free Suno v6 Rescue Path →Think in layers
Sound, structure and moments
1 · Sound
What should the whole song feel like? Genre foundation, production character, key instruments, broad vocal identity and emotional tone belong here.
2 · Structure
Where are the verse, chorus, bridge, drop or instrumental moments? Give the song an understandable architecture before adding micro-direction.
3 · Moments
What should change only here? A choir entering in the final chorus is a local instruction, not necessarily part of the entire song identity.
These directions are not deterministic code. They guide a generative model. The value of clean placement is that when the model misses, you have a better idea what to change.
Before and after
Fix placement before rewriting everything
Genre confusion
Weak:
reggae gospel trap cinematic rock emotional aggressive piano guitar choir 808
Stronger Styles:
Reggae-rock foundation, gospel choir accents, deep bass, distorted guitar, defiant cinematic energy
Choose a foundation. Make the rest accents or priorities.
Instructions get sung
If prose directions in Lyrics look performable, the model can treat them like material to sing. Move global musical direction to Styles and keep local cues concise.
[Bridge – instruments drop, close vocal] I hear the room breathe back my name
The chorus will not lift
If the global identity is already right, fix the moment instead of rewriting the whole Styles field.
[Chorus – full band, stacked responses, increased intensity]
Every retry changes too much
Lock what already works. Keep the same model and core brief, change one variable, listen, record the result, then decide the next move.
A better testing workflow
Stop treating every generation like a new experiment
Define one musical mission
Name the song’s job before you touch the fields: hook test, full-song candidate, mood study, instrumental bed or something else.
Choose Simple or Custom by the control you need
Use Simple for speed and whole-idea direction. Use Custom when you need field separation, your own lyrics or cleaner diagnosis.
Choose the model by the job
Keep V6, V6-Wild and V6-Mini as a separate decision from prompt wording. If you are testing a prompt, hold the model steady first.
Place each instruction where it belongs
Global sound in Styles, performed text and section cues in Lyrics, dedicated jobs in dedicated controls.
Generate a small comparable set
Do not rewrite the entire brief after one miss. Listen for which part of the instruction survived and which part drifted.
Change one meaningful variable
Prompt wording, model choice, structure cue and slider setting are different variables. If you change them all together, you learn almost nothing.
Diagnose before you regenerate
Prompt problem, model problem, slider problem—or song problem?
Polished result, wrong musical direction
Check first: Prompt mission and Styles hierarchy
Avoid: Switch every setting at once
Direction is right but too safe
Check first: Model choice; compare V6-Wild
Avoid: Stuff more adjectives into Styles
Direction changes wildly between tries
Check first: Model choice, prompt conflicts, Variety
Avoid: Assume longer prompts equal more control
One section is weak
Check first: Local structure/edit workflow
Avoid: Throw away the keeper
Reference is not followed closely enough
Check first: Relevant influence/reference control
Avoid: Repeat the same reference request in multiple fields
Hook, cadence or lyric is generic
Check first: The writing itself
Avoid: Blame the generator for a weak song idea
Keep the useful existing training
Where to go when placement is no longer the problem
Your prompt is placed correctly but still misses
Move into a deliberate construction and repair process instead of cycling through random rewrites.
Build and repair the prompt →The song works but one section does not
Learn structure control before rebuilding a working song.
Learn Suno song structure tags free →You still need a clean starting framework
Build one prompt clearly before spending more credits or adding more controls.
Get the free AI Prompt Foundation Kit →You need examples by genre
Use the genre library as references, then adapt the prompt to your own musical mission instead of copying blindly.
Open the Suno prompt examples →Choose the bigger next step
Prompt placement is one skill. Build the system around it.
If this solved where your instructions belong, the next question is whether you need broader orientation or a repeatable AI-music operating system.
Need broader direction first?
The free Creator Starter Kit helps you place this lesson inside the larger creator journey: what you are making, how to think about rights and positioning, and what to do next.
Open the Creator Starter KitReady to build a repeatable music process?
Find Your Sound — AI Music Operator Manual V6 + Song Decision Guide connects prompting, structure, revision, production decisions and keeper selection into one reusable system.
Open Find Your Sound — Operator ManualPrefer to keep learning free? Continue with Find Your Sound — Free Core Path →
FAQ
Common prompting questions
Where do Suno prompts go?
Use Simple mode when one description can carry the idea. In Custom mode, put global musical identity in Styles, performed words and concise local section cues in Lyrics, and use dedicated controls for jobs Suno already separates.
Can Simple mode handle detailed V6 instructions?
Yes. Suno’s current V6 guidance says Simple mode can accept complex and diverse directions and can work with multiple kinds of references. Use Custom when you want clearer field separation and easier diagnosis.
Should instruments go in Lyrics?
Put overall instrumentation in Styles. A short Lyrics cue can make sense when an instrument matters only to one specific section, such as [Bridge – isolated cello].
Why does Suno sing my instructions?
Directions placed in Lyrics can resemble performable text. Move global production instructions into Styles and keep local cues concise and clearly separated from the lyric lines.
Should BPM and key go in Styles?
They can be part of the global direction when useful, but treat exact compliance as guidance rather than guaranteed deterministic control.
What if the prompt seems right but the result still fails?
Hold the model and core brief steady, isolate one variable and test it. The problem may be model selection, a structure cue, a slider, the source/reference, or the songwriting itself—not prompt wording.
Current platform references
What Suno currently confirms
Suno’s current V6 documentation says the model family understands more musician-language across vocals, instrumentation, structure, mood, references and overall feel. Its current Simple Mode documentation still centers on describing what you want to hear, while Custom Mode exposes separate lyrics, Styles and Advanced options. Interface details can change during rollout, so feature-specific controls should always be checked against Suno’s current documentation.
Series navigation
You have the direction. Next, protect the keeper.
Prompting gets you closer to the target. The next production skill is knowing when not to regenerate the whole song. Part 6 will focus on editing: local fixes, what to preserve, and when V6’s edit workflow is a better move than another full generation.
Creator Labs / Next learning decision
Your prompt is in the right place. What should you do next?
You now know how to separate musical direction from performed words. Choose the next action based on what your song needs rather than adding more instructions or purchasing tools by default.
Continue the complete free workflow
Move from prompt placement into selecting your keeper, fixing weak sections, finishing audio, checking rights and preparing a release.
Learn to control the next variable
Need genre, vocal, lyric or structure examples? Explore the organized Prompt Vault Hub and check the access requirements before using member resources.
Choose the level of training
Use Creator Library for DIY reference material, Creator Pro for ongoing learning, or Complete Access when consultations and project guidance matter.
Continue the free Suno V6 workflowExplore Find Your Sound
How to Use JR: The placement lesson above is complete without a purchase. Advanced vaults, reusable systems and consultation are optional paths for creators who want more structure.
2件のコメント
Awesome thanks
It ist really amazing
Thanks