Suno structure tag reference
Click a label to copy it into the Lyrics box. This page is a lookup reference: tags make your intended sections readable, but they do not guarantee a fixed arrangement or performance. Use the song-structure guide when you still need to plan the order, contrast, or ending.
Song sections
Mark verses, hooks, and arcs
Dynamics & breaks
Control energy and space between vocal lines
Ending control
Reduce abrupt cuts
Vocal instructions
Specific vocal moments
Use the tags in a lyrics workflow
Copy, clean, estimate, compare
- Choose only the sections your arrangement needs; read the Structure playbook if the order is not settled.
- Paste the draft into the Tag Formatter to tidy spacing and flag unfamiliar brackets.
- Convert non-English section labels with the Tag Normalizer when needed.
- Check section length with the Lyrics Duration Estimator, then compare the final revision in Lyrics Diff.
See Troubleshooting if tags seem ignored, and Field limits for box length.
What each tag asks for
Evidence scope: These definitions describe creator intent, not deterministic model behavior. Suno’s current Lyrics editor supports section labels such as Verse and Outro, but the audible response can vary by model and generation. Compare one tag with a stable baseline and judge the rendered section.
Section tags
Core song structure
[Intro]- Labels the intended opening. Use Lyrics and Style to say whether it should be instrumental, vocal, sparse, or immediate; the label alone does not set a fixed length or instrumentation.
[Verse]- Labels a verse section, usually where the narrative or detail develops. Write the intended lyric density and use Style to request any lower energy or reduced arrangement.
[Chorus]- Labels a recurring chorus or hook section. Repetition, shorter lyric lines, melodic shape, and a compatible Style direction do more to express the intended lift than the label by itself.
[Pre-Chorus]- Requests a linking section before the chorus. If you want a build, make that rise visible in line length, harmony, instrumentation, or ordinary Style wording and verify the transition.
[Bridge]- Labels a contrasting section, often before the final return. State what should contrast—harmony, perspective, register, density, or rhythm—rather than assuming the label defines it.
[Outro]- Requests an ending section. Compare [Outro], [Fade Out], and no ending tag when abrupt cuts are a problem; none is a guarantee.
[Fade Out]- Requests a gradual fade. Place it at the end when that transition suits the arrangement, then listen to confirm the ending fades.
[Ending]- Requests a definite ending rather than a fade. Compare it with [Outro], [Fade Out], and a revised final lyric section; no ending label guarantees a clean cadence.
Instrumental tags
Non-vocal sections
[Instrumental Break]- Requests a broader non-vocal passage between lyric sections. Name any lead instrument or texture in Style and check whether vocals actually pause in the render.
[Solo]- Requests a featured lead-instrument passage. Specify the instrument and role in Style; the tag does not guarantee the instrument, duration, or melodic behavior.
[Interlude]- Requests a linking passage between major sections. Describe its intended texture or function because the label does not define a fixed length or mood.
[Drop]- Requests a release or peak after a build, especially in electronic styles. Reinforce the intended energy and instrumentation in Style, then score the actual contrast.
[Build]- Requests increasing tension before a release. The change may come from density, rhythm, harmony, or dynamics; specify what should rise instead of assuming a tempo change.
[Breakdown]- Requests a stripped-back contrast section. Name the element that should remain and the layers that should recede, then verify the rendered density.
Vocal direction tags
Per-section vocal control
[Spoken]/[Spoken Word]- Requests speech-like delivery for a local section. It may still sound pitched or rhythmic, so compare the actual delivery with the global vocal direction.
[Whispered]- Requests a quieter, breathier delivery. It does not reliably override a conflicting global Style direction; test it on one short section.
[Belted]- Requests a stronger full-voice delivery. Keep register, lyric density, and global vocal wording compatible with the request.
[Harmonized]- Requests vocal harmony in that section. The number, interval, placement, and audibility of harmony can vary; describe the ensemble in Style when it matters.
[Ad-libs]- Requests background vocal improvisation around the lead. Leave lyrical space for it and verify that it does not crowd the main line.
Transition and effect tags
Controlling flow between sections
[Fade In]- Requests a gradual entrance in level or density. Listen for the actual transition; the tag does not guarantee a literal gain fade.
[Key Change]- Signals a modulation to a different key. Results are inconsistent across model versions. For more reliable key changes, generate in two parts and use Extend.
[Tempo Change]- Requests a tempo shift, but results are inconsistent. Test it separately from changes in rhythm, density, and section length so the audible difference is easier to identify.
[Ritardando]- Requests a gradual slowdown. Reinforce the intent in ordinary wording and verify timing in the result; partial or absent response is possible.
Best practices for tag usage
Rules of thumb
- Test an ending tag when needed: compare [Outro] and [Fade Out] with the baseline; keep the one that improves the actual ending.
- Start with common labels: [Verse], [Chorus], and [Bridge] make the intended form readable; custom labels need separate testing.
- Keep tags purposeful: use tags at meaningful boundaries and remove ones whose effect you cannot distinguish; there is no universal ideal count.
- One tag per line: Place each tag on its own line, followed by the lyrics for that section. Do not stack multiple tags on one line.
- Number for editorial clarity: [Verse 1], [Verse 2], [Chorus 1], and [Chorus 2] make drafts easier to compare, but numbering does not guarantee a different arrangement for each repeat.
Quick FAQ
Do structure tags go in Style or lyrics?
Metatags like
[Chorus] belong in the lyrics box; Style carries sound.Why use brackets like [Chorus]?
They signal sections so the model can follow your arrangement intent.
Can I copy tags from this page?
Yes; use the copy buttons; pair with Lyrics vs Style for alignment.
What if my song ignores a tag?
Reinforce with lyrics structure and matching Style energy; see Troubleshooting.
Where is song-structure workflow explained?
See Structure for how sections and Style interact.
What is the most important structure tag to use?
No tag is universally most important. If an ending is abrupt, compare [Outro], [Fade Out], and a revised final section while keeping the rest stable.
Can I create my own custom structure tags?
You can test custom labels, but their effect is undocumented and may vary. Use common section labels for the baseline and express unusual direction in ordinary lyrics or Style wording.
What is the difference between [Solo] and [Instrumental Break]?
[Solo] requests a featured lead-instrument passage. [Instrumental Break] requests a broader non-vocal section. The rendered instrument, duration, and arrangement can vary, so describe the intended role in Style and verify the result.Do vocal direction tags override the Style field?
Not reliably. Labels such as
[Whispered] and [Belted] request local delivery, but they can be weakened or ignored when the global Style, lyrics, or generated performance conflicts. Compare one local label with a stable baseline.Should I number my verses and choruses?
Numbering repeated sections can make your draft and revisions easier to read, but it does not guarantee that Suno will create a different arrangement for each number. Use numbering for clarity and state the intended contrast in lyrics or Style.