SunoBatch

Reference guide

Suno Metatags: The Complete List and How to Use Them

Metatags are the square-bracket instructions inside a Suno lyric that tell the model what to do instead of what to sing: where the chorus starts, when the vocal drops to a whisper, when the drums cut out entirely. Used well, they are the difference between a song that wanders and a song that is arranged. This is the working reference — the tags by category, where each one goes, and the mistakes that waste generations.

The one rule: style field vs lyrics field

Suno reads two different inputs, and metatags belong in only one of them. The style field holds genre, mood, instruments and vocal type ("lo-fi hip hop, warm piano, soft female vocals"). The lyrics field holds the words — plus metatags in square brackets that control structure and delivery. Putting style words in brackets inside the lyric does not break anything, but it wastes the space where arrangement instructions belong, and putting section tags in the style field does nothing at all.

Bracketed tags are instructions, not lyrics: Suno reads them as directions and does not sing them. Parentheses, by contrast, are sung as backing vocals or ad-libs. Mixing the two up is how a "[Chorus]" ends up being belted as a word instead of opening the chorus.

Structure tags: the skeleton of the song

These are the tags you will use in every song. They mark sections, and Suno arranges the music around them:

TagWhat it doesWhere it goes
[Intro]Instrumental or soft opening before the first verseVery start of the lyric
[Verse][Verse 1], [Verse 2] for distinct versesBefore each verse's lines
[Pre-Chorus]Build-up section before the chorusBetween verse and chorus
[Chorus]The repeated hook sectionBefore the hook lines
[Bridge]Contrasting middle sectionAfter the second chorus
[Break]Minimal arrangement — a drop or breatherWhere the track should thin out
[Interlude]Short transition passageBetween sections
[Instrumental]No vocals for this stretchSolos, breaks, intros
[Outro]Closing sectionEnd of the lyric
[Fade Out]Gradual ending instead of a hard stopFinal lines

Vocal delivery tags: how it is sung, not just what is sung

Delivery tags sit on the line they affect. They are the cheapest way to make a generated vocal sound intentional:

TagEffectUse it when
[Whispered]Quiet, close-mic deliveryIntimate verses, secrets, late-night songs
[Belted]Full-power vocalChorus peaks, anthems
[Falsetto]High, light vocal registerEmotional lifts, R&B and pop choruses
[Spoken Word]Talked rather than sungStorytelling passages, intros
[Harmonized]Layered backing vocalsChoruses that need width
[Male Vocals] / [Female Vocals]Vocal gender for a sectionSwitching voices mid-song

Arrangement and sound tags: instruments, effects, atmosphere

These tags describe what the band does during a section. Keep them to two or three per section — a tag list longer than the lyric it decorates is the fastest way to a muddy generation:

Tag familyExamplesNotes
Instruments[Acoustic Guitar], [Synth Pads], [808 Bass], [Strings]Name the lead instrument first
Drum cues[Beat Drops], [Drums Enter], [No Drums]Useful for drops and breakdowns
Solos[Guitar Solo], [Saxophone Solo], [Piano Interlude]Pair with [Instrumental] for clean solos
Effects[Echoing Vocals], [Reverb-Drenched]Atmosphere, not arrangement
Crowd and scene[Applause], [Audience Laughing], [Rain Sounds]Scene-setting; easy to overuse

A worked example: one tagged skeleton, start to finish

Here is a complete skeleton using only the tags above. The words are placeholders for your own lyric — the structure is the point:

  • [Intro: Soft piano and rain sounds]
  • [Verse 1: Whispered vocals]
  • Two lines of scene-setting, quiet and specific.
  • [Pre-Chorus: Building intensity]
  • Two lines that lean forward into the hook.
  • [Chorus: Belted vocals, full band]
  • The hook, twice, no extra words.
  • [Verse 2]
  • Two lines that deepen the story, not repeat it.
  • [Chorus: Belted vocals, full band]
  • The hook again, unchanged — repetition is what makes it a chorus.
  • [Bridge: No drums, strings only]
  • One turn: a new image or a confession.
  • [Outro: Fade out]
  • The hook once more, quieter, then gone.

The mistakes that waste generations

Most metatag failures are not mysterious. They are one of these:

  • Too many tags: a section with six arrangement tags fights itself. Two or three, chosen for contrast with the previous section, beat a shopping list.
  • Conflicting tags: [Whispered] and [Belted] on the same lines, or [No Drums] next to [Beat Drops]. Suno picks one; you will not know which until you hear it.
  • Tags in the style field: section markers there are ignored. Style belongs in the style field; structure belongs in brackets in the lyric.
  • Parentheses for instructions: (whispered) is sung as a backing line. Square brackets are the instruction syntax.
  • Tagging every line: tags mark sections and turns. A lyric where every line wears a tag reads as noise to the model — tag the section once, then let the words do the work.
  • Regenerating instead of re-tagging: when a song comes out wrong in one place, fix the tag on that section and regenerate. Throwing away the whole lyric because the bridge misfired wastes the verses that worked.

Using metatags at batch scale

Tags pay off twice when you work in batches. A tagged skeleton is reusable: write it once, swap in a new lyric per song, and every generation in the batch shares the same arrangement logic — which is how you get a consistent sound across a whole set instead of ten unrelated songs.

The no-tool route is just Suno itself: paste tagged lyrics into Custom Mode, generate, and download from your library. At scale, SunoBatch's bulk-create flow turns up to 50 of your tagged lyric sheets into songs in one run, and downloads run up to 20 tracks per batch in MP3, M4A or WAV, without spending your Suno download allowance and without asking for your Suno password. First 5 downloads are free, lifetime.

Suno metatags FAQ

Metatags are square-bracket instructions inside a Suno lyric — like [Chorus], [Whispered] or [Guitar Solo] — that tell the model how to structure and deliver the song. They are read as directions, not sung as words.

The lyrics field. The style field holds genre, mood, instruments and vocal type in plain words. Section and delivery tags only work as bracketed instructions inside the lyric; in the style field they are ignored.

Square brackets are instructions the model follows but does not sing. Parentheses are sung as backing vocals or ad-libs. Use brackets when you want an arrangement change, parentheses when you want a voice in the background.

Tag the sections and the turns — typically one structure tag per section plus one or two delivery or arrangement tags where a section needs to stand out. More than two or three tags on a single section usually fights itself and muddies the result.

Almost always because it was in parentheses instead of square brackets, or because it was written as plain text without brackets at all. Check the characters: [Chorus] is an instruction, (chorus) is a backing line, and Chorus with no brackets is just a lyric.

Yes, and you should. A tagged skeleton — intro, verses, chorus, bridge, outro — is arrangement logic, not content. Swap in a new lyric per song and the batch keeps a consistent sound; bulk-create flows accept up to 50 tagged lyric sheets in one run.

Structure is a skill. Batches make it a habit.

Write one tagged skeleton, run it across 50 lyric sheets, download 20 tracks per batch. First 5 downloads free.