Suno AI Meta Tags & Song Structure Command Guide
Free Suno V5.5 reference · Reviewed July 2026
Suno meta tags are bracketed structure labels and short creator cues placed in the Lyrics field. They help communicate the song map, but they are generative signals—not guaranteed software commands.
The working rule
Style defines the broad sound world. Lyrics carries the words and section map. Exclude removes meaningful conflicts. Personalization can support identity, but it does not replace clear direction.
Style vs Lyrics vs Exclude vs Personalization
Style
Use it for the broad sound world.
- Genre or musical lane
- Tempo and groove
- Main instruments
- Broad vocal character
- Production texture
- Overall emotional direction
Lyrics
Use it for what happens inside the song.
- Actual lyrics
- Section labels
- Hook repetition
- Local performance cues
- Contrast and pacing
Exclude
Use a short list of elements that would damage the lane.
- Unwanted instruments
- Vocal qualities
- Genre influences
- Production effects
- Arrangement habits
Personalization
Use eligible voice and preference tools to support identity.
- Voices
- Custom Models
- My Taste
- Relevant source audio
Style example
Modern roots reggae, 82 BPM, deep round bass, offbeat guitar skank, warm organ, grounded baritone, reflective verses, communal chorus
Exclude example
Trap hi-hats, EDM drop, theatrical choir, long instrumental intro
Copy-ready song maps
Paste a structure into Custom Lyrics, remove the explanatory notes and replace them with your own words. Build the map before adding descriptive cues.
Standard song template
[Intro] [Verse 1] Introduce the setting, voice or conflict [Pre-Chorus] Shorten the phrasing and build anticipation [Chorus] Deliver the central hook and strongest lift [Verse 2] Develop the idea without repeating Verse 1 [Bridge] Change perspective, harmony, rhythm or emotional pressure [Final Chorus] Return to the hook with the widest arrangement [Outro] Resolve the ending or prepare a controlled fade
Delete the guidance sentences before generating. Leaving them in can cause Suno to treat them as lyrics or performance directions.
Standard map
[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]
Core structure labels and creator cues
| Label | Job | Common mistake |
|---|---|---|
| [Intro] | Establish the palette and prepare the first section | Delaying the main idea with an oversized opening |
| [Verse] | Carry story, detail and lower-density phrasing | Writing every line at chorus intensity |
| [Pre-Chorus] | Raise anticipation before the hook | Repeating the verse without changing pressure |
| [Chorus] | Deliver the central hook and repeated idea | Writing another dense verse |
| [Bridge] | Create contrast through thought, harmony, rhythm or emotion | Giving the bridge no new purpose |
| [Outro] | Resolve the landing or prepare a fade | Expecting the label alone to force an exact ending |
| [Build-Up] | Increase tension or density | Using it without a defined destination |
| [Breakdown] | Reduce density and create contrast | Keeping every instrument at full intensity |
| [Spoken] | Suggest speech-like delivery | Combining it with a conflicting global vocal direction |
| [Call and Response] | Suggest an exchange between voices | Expecting the cue to write both sides clearly |
Three levels of reliability
Level 1 · Start here
Clear structure labels
[Intro], [Verse], [Pre-Chorus], [Chorus], [Bridge], [Outro]
These create the most readable map, but still do not guarantee an exact arrangement.
Level 2 · Use when needed
Common event cues
[Build-Up], [Drop], [Breakdown], [Instrumental], [Spoken], [Final Chorus]
Place one concise cue directly before the event it should influence.
Level 3 · Experimental
Descriptive bracket cues
[Energy: High], [Vocal: Warm], [Drums: Stronger], [Harmony: Wider]
Treat these as creator shorthand, not official switches.
Why a tag appears to be ignored
| What happened | Likely cause | First action |
|---|---|---|
| The label is sung aloud | The cue is too verbose or lyrical | Shorten the bracket |
| Sections blend together | The lyrics create too little contrast | Clarify each section’s job |
| The chorus does not lift | It reads like another verse | Reduce density and strengthen the hook |
| Genre keeps drifting | Several primary styles compete | Keep one lead genre |
| An unwanted instrument appears | The negative request is buried in Style | Move it to Exclude |
| The ending continues too long | The label cannot force exact timing | Simplify and edit the ending |
| Every retry is unrelated | Too many variables changed | Hold the prompt and lyrics steady |
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 tags control exact song length?
They can influence pacing, but they are not the strongest duration control. Use the available duration or editing tools for runtime problems.
Should I regenerate or edit?
Regenerate when the whole direction or map is wrong. Edit, replace or extend when the central song works and only one part needs attention.
Do Voices and Custom Models replace structure?
No. They influence identity or personalization. The prompt, lyrics and section map still need to define the current song.
Continue with the right layer
Use the prompt guide for sound direction and this page for structure control
Keep the roles separate: the prompt guide defines the musical brief; this reference organizes sections, field placement and troubleshooting.
Official Suno references
Jack Righteous is an independent creator resource, not Suno Support. Features and interface placement can change.