Suno AI Meta Tags & Song Structure Command Guide
A practical reference for deciding where an instruction belongs, choosing the best structure cue, judging how dependable that cue is likely to be, and knowing what to change when Suno interprets it poorly.
Style defines the broad sound world. Lyrics carries words, section labels and local cues. Exclude removes meaningful conflicts. Personalization influences identity and preference, but it does not replace clear song direction.
- Choose the field.
- Choose the smallest useful cue.
- Test one revision at a time.
Understand
Field placement comes before tag selection
Many weak results begin before the cue is written: the instruction is placed in the wrong control layer.
Broad sound world
Genre, groove, BPM, primary instruments, vocal character, production texture and overall emotional direction.
Local song events
Actual lyrics, section labels, hook repetition, contrast, call and response, spoken moments and arrangement cues tied to a specific location.
Meaningful conflicts
Unwanted instruments, vocal qualities, genre influences, production effects or arrangement habits that would damage the intended lane.
Identity layer
Voices, Custom Models, My Taste and eligible source audio may influence identity or preference. They interact with the song brief rather than replacing it.
Modern roots reggae, 82 BPM, deep round bass, offbeat guitar, warm organ, grounded baritone, reflective verses, communal chorus
Trap hi-hats, EDM drop, theatrical choir, long instrumental intro
Choose
What are you trying to make Suno do?
Start with the intended musical outcome—not a long list of possible tags.
Build
Copy-ready song maps
Start with a readable structure. Add descriptive cues only after the section map itself is doing a clear job.
Standard song
[Intro] [Verse 1] [Pre-Chorus] [Chorus] [Verse 2] [Chorus] [Bridge] [Final Chorus] [Outro]
Hook-first short form
[Chorus] [Verse] [Chorus] [Breakdown] [Final Chorus]
Instrumental build
[Intro] [Theme] [Build-Up] [Drop] [Breakdown] [Final Build] [Outro]
Reference
Command library by function
Read across one row: cue, intended job, placement, reliability class and the first revision to try.
| Cue | Primary job | Best placement | Reliability | First revision when weak |
|---|---|---|---|---|
| [Intro] | Establish palette or entry point | Top of Lyrics | Foundation | Shorten the opening or remove it |
| [Verse] | Carry story, detail and lower-density phrasing | Before each verse | Foundation | Differentiate lyric purpose from chorus |
| [Pre-Chorus] | Raise anticipation | Immediately before chorus | Foundation | Shorten lines and increase tension |
| [Chorus] | Deliver central hook | Before hook block | Foundation | Reduce density and strengthen repetition |
| [Post-Chorus] | Extend hook energy | After chorus | Common cue | Use fewer words and one repeated phrase |
| [Refrain] | Return to a short repeated line | Where recurring line belongs | Common cue | Make it shorter than a chorus |
| [Bridge] | Create contrast in thought, harmony or rhythm | Late-song contrast point | Foundation | Give it a genuinely new purpose |
| [Interlude] | Create a pause or connective passage | Between major sections | Common cue | Clarify whether it is vocal or instrumental |
| [Outro] | Resolve the landing | Final section | Foundation | Remove new lyrical ideas |
| [Build-Up] | Increase tension or density | Before a clear destination | Common cue | Name or create the destination |
| [Drop] | Release built energy | After build-up | Common cue | Simplify surrounding cues |
| [Breakdown] | Reduce density | Before a quieter contrast section | Common cue | Reduce lyric and instrument density |
| [Instrumental Break] | Create lyric-free space | Between vocal sections | Common cue | Remove words directly below the cue |
| [Solo] | Feature one lead instrument | At desired solo location | Common cue | Name the instrument in Style or cue |
| [Guitar Solo] | Feature guitar | Before solo passage | Descriptive cue | Ensure guitar belongs in Style |
| [Violin Solo] | Feature violin | Before solo passage | Descriptive cue | Support violin in Style and remove conflicts |
| [Drum Break] | Feature percussion | Transition or dance section | Descriptive cue | Shorten the section and simplify other layers |
| [A Cappella] | Remove instrumental backing | Before isolated vocal moment | Common cue | Use a short passage and clear vocal direction |
| [Spoken] | Suggest speech-like delivery | Directly before spoken text | Common cue | Shorten text and remove melodic conflicts |
| [Whispered] | Suggest quiet intimate delivery | Directly before line or section | Descriptive cue | Keep the passage brief |
| [Call and Response] | Suggest an exchange between voices | Before clearly written exchange | Common cue | Write both sides explicitly |
| [Choir] | Suggest ensemble harmony | Before group vocal passage | Descriptive cue | Support choir in Style and simplify lead direction |
| [Group Vocal] | Suggest communal delivery | Before chant or response | Descriptive cue | Use short repeatable wording |
| [Half-Time] | Suggest slower rhythmic feel | Before contrast section | High variance | Support with groove language in Style |
| [Double-Time] | Suggest faster rhythmic subdivision | Before accelerated section | High variance | Support with phrasing and drum direction |
| [Sparse Instrumentation] | Reduce arrangement density | Before quiet passage | Descriptive cue | Name what should remain |
| [Full Band] | Restore wide arrangement | Before lift or final chorus | Descriptive cue | Use after a clearly sparse section |
Test
Four reliability classes
Reliability is not a promise of exact output. It tells you how much a cue depends on surrounding context.
Clear structural labels
[Verse], [Chorus], [Bridge], [Outro]. Usually the most readable signals, but never exact software switches.
Familiar musical events
[Breakdown], [Instrumental Break], [Spoken], [Call and Response]. Useful when placed close to the event.
Creator shorthand
[Warm Harmony], [Violin Solo], [Sparse Instrumentation]. More dependent on Style, lyrics and surrounding context.
Detailed or unusual cues
[Half-Time], layered compound commands or highly specific production language. Test one variable at a time.
Apply
Worked example: reflective roots-reggae anthem
This example shows how the layers work together without asking every control to do the same job.
Creative goal
Grounded verses that grow into a communal final chorus without drifting into trap, EDM or theatrical gospel.
StyleModern roots reggae, 82 BPM, deep round bass, offbeat guitar, warm organ, restrained drums, grounded male baritone, reflective verses, communal final chorusExclude
Trap hi-hats, EDM drop, theatrical choir, long instrumental intro
[Verse 1] Personal conflict and setting [Pre-Chorus] Shorter lines, rising anticipation [Chorus] Simple central hook [Verse 2] Wider social meaning [Breakdown] One quiet reflective line [Call and Response] Lead: short question Group: short answer [Final Chorus] Repeat hook with wider communal energy [Outro] One final resolving phrase
If the chorus fails, change the chorus lyrics or local cue before rebuilding the entire Style field. Use the intensity guide when the energy curve is the real problem.
Decide
Use a cue, regenerate, edit, extend or move to a DAW?
Not every problem is a prompting problem. Choose the tool based on how much of the song is already working.
Fix a weak Suno generation without starting blindly · Use the free song-development workbook
Fix
Why a cue appears to be ignored
Start with the smallest plausible cause and isolate one change.
| What happened | Likely cause | First action | Deeper help |
|---|---|---|---|
| The label is sung aloud | The cue is too verbose or lyrical | Shorten the bracket | Beginner structure lesson |
| Sections blend together | The lyrics create too little contrast | Clarify each section’s job | Song structure guide |
| The chorus does not lift | It reads like another verse | Reduce density and strengthen repetition | Intensity guide |
| Genre keeps drifting | Several primary styles compete | Keep one lead genre | Prompt guide |
| An unwanted instrument appears | The negative is buried in Style | Move it to Exclude | Advanced workflow |
| The ending continues too long | A label cannot force exact timing | Simplify, edit or extend | Repair workflow |
| Every retry is unrelated | Too many variables changed | Hold prompt and lyrics steady | Free workbook |
Clarify
Common questions
Do Suno meta tags guarantee exact results?
No. They are prompt signals inside a generative system. Results also depend on the model, lyrics, Style, Exclude, personalization and normal variation.
Can a tag control exact song length?
It can influence pacing but is not a precise duration control. Use available duration, editing, extend or DAW tools for runtime problems.
Should every section have a descriptive cue?
No. Begin with the minimum readable map. Add a local cue only when the section needs a distinct event or delivery change.
Do Voices, Custom Models or My Taste replace structure?
No. They influence identity or preference. The current prompt, lyrics and section map still need to define the song.
What is the difference between a prompt and a meta tag?
The prompt usually describes the broad musical brief. A meta tag or bracketed cue usually marks structure or a local event inside the Lyrics field.
Continue
Continue with the layer that matches your problem
Each destination now uses the full page width, so the explanation remains readable and the action stays clear.
Connect prompting, song development and repeatable creative direction.
Enter Find Your SoundSources
Official Suno references
These links support documented feature behaviour. Common musical labels and creator shorthand remain generative conventions, not guaranteed software commands.
Jack Righteous is an independent creator resource, not Suno Support. Interface placement and feature behaviour can change. This guide separates documented features, common musical conventions and tested creator shorthand rather than presenting every bracket as an official command.