Guide

Suno meta tags for cleaner lyric blocks

Suno meta tags are square-bracket labels in the Lyrics field that hint at sections, vocal delivery, builds, drops, and endings. They work best when your lyric block is boringly clean: one tag per line, no stray title before the first tag, short sections, and repeated choruses pasted the same way every time.

By SoundUser teamUpdated October 29, 20269 min read

Illustration: small cream paper tags tied with orange string to segments of a teal resin sound wave.

Quick answer

Put Suno meta tags like [Verse 1], [Chorus], [Build], and [Outro] alone on their own lines in the Lyrics field. Keep most sections under about 12 lyric lines. Tags are hints, not commands, so misspelled, inline, or invented tags can be ignored or sung aloud.

Use structure tags to map the song before it sings

Notebook and MIDI keyboard set up for planning song sections

Structure tags tell the generator where each part of the song starts, so it can separate setup, payoff, contrast, and ending. If the form is still fuzzy, map the sections first with a song structure guide, then paste the tags into the lyric body.

Tag	What it points to	Lines under it	Practical use
`[Intro]`	Opening groove	0 or 1	Put first when you want a clear start.
`[Verse]`	Story section	4, sometimes 8	Use once, or number verses for safety.
`[Verse 1]`, `[Verse 2]`	Separate story sections	4, sometimes 8	Helps stop verse parts merging.
`[Pre-Chorus]`	Lift into chorus	2	Short, tense, rising.
`[Chorus]`	Main payoff	4	Put the title phrase here.
`[Post-Chorus]`	Tag after chorus	1-2	Good for a chant or repeat.
`[Hook]`	Short repeated idea	2-4	Useful in pop, rap, and lo-fi.
`[Refrain]`	Repeated verse tail	1	Folk-style repeat.
`[Bridge]`	New angle	2-4	Change image, harmony, or energy.
`[Build]`, `[Build-Up]`	Rise before drop	0-2	Use little lyric.
`[Drop]`	EDM payoff	0-1	Usually leave it empty.
`[Breakdown]`	Stripped section	2	Pull energy down.
`[Interlude]`	Short gap	0-1	Breath between parts.
`[Instrumental]`	No vocal section	0	Keep lyric lines out.
`[Solo]`, `[Guitar Solo]`, `[Piano Solo]`, `[Synth Solo]`, `[Sax Solo]`	Lead instrument break	0	Name one lead sound.
`[Break]`	Rhythmic pause	0	A stop, not a new section.
`[Outro]`	Closing section	1-2	Repeat title or last image.
`[End]`, `[Fade Out]`	Stop or fade	0	Put last with nothing after.

Delivery tags affect the next lines, not the whole track

Delivery tags change how the next lyric lines are performed, so they should sit directly above the words they affect. They are best when used sparingly. Stacking [Whisper], [Chant], and [Ad-Libs] on the same moment often gives the model mixed orders. Pick the one job you actually need.

Tag	Expected effect	Best placement	Common problem
`[Spoken]`, `[Spoken Word]`	Talked delivery	Intro, bridge, breakdown	Long blocks go flat.
`[Rap Verse]`, `[Rap]`	Rapped rhythm	Short-bar verse	Wordy lines blur.
`[Whisper]`	Quiet close vocal	1-2 intimate lines	Weakens a big hook setup.
`[Shout]`, `[Chant]`, `[Crowd]`, `[Gang Vocals]`	Raised group vocal	Hook, post-chorus	Too many words turn muddy.
`[Ad-Libs]`, `[Vocal Run]`	Decorative vocal	Parentheses and echoes	Full sentences feel clumsy.
`[Acapella]`	Vocal focus	Breakdown or intro	May still imply arrangement.
`[Half-Time]`, `[Double-Time]`	Groove feel shift	Rap or dance section	Needs short lines.
`[Key Change]`	Modulation hint	Before final chorus	Needs a chorus after it.
`[Big Finish]`, `[Silence]`	Ending gesture	Final moments	Does not replace `[Outro]`.

At 140 BPM, [Half-Time] can feel like a 70 BPM pulse. That is great for trap-style weight, bad for a chorus that needs forward motion.

Put bracket tags in Lyrics and sound notes in Style

Bracket tags belong in the Lyrics field, while genre, BPM, key, instruments, mood, mix words, and vocal tone belong in the Style field. Think of Lyrics as the chart, and Style as the production brief.

Lyrics field:

[Intro]

[Verse 1]
Streetlights blink on the wet glass
I count the turns back home

[Chorus]
We run all night to find the morning
We run all night and call it hope

Style field: indie pop, 108 BPM, C major, bright, bittersweet, clean electric guitar, tight drums, warm bass, room reverb, clear female vocal

Do not put [Chorus] in Style. It does not mark the chorus location in your lyric block, and it steals room from sound words that matter. Put the genre first, then a fusion genre if needed, then tempo, key, two moods, instruments, production, vocal, and language if needed. If you want a deeper sound prompt pattern, use this Suno prompt writing guide.

Placement rules that stop tags being sung aloud

The model usually sings a tag aloud when the tag is misspelled, lower-case, inline with a lyric, or not a tag it understands. The fix is plain: use a known tag, capitalized, alone on its own line.

Broken:

Midnight Run
[Intro] soft guitar
[verse 1]
I packed the car before the rain
[Chorus] We run all night
We run all night

Fixed:

[Intro]

[Verse 1]
I packed the car before the rain
I left the porch light glowing
I heard the tires sing my name
I kept the engine going

[Chorus]
We run all night
We run all night

Nothing goes before the first tag. [Intro] goes first when you use it. [Outro], [End], or [Fade Out] goes last. Keep brackets balanced, avoid duplicate tags back to back, and keep sections near 12 lines or fewer. Parentheses are useful for backing parts: (oh-oh) on its own line feels like an echo, while We run all night (oh-oh) feels like a response. Need tighter lines first? Start with lyrics writing basics.

The first visible line is a known tag.
Every tag sits alone on its own line.
Brackets are balanced.
Verses are numbered when there is more than one.
Repeated chorus blocks match exactly.
No section has a pile of long, uneven lines.
Nothing appears after [End] or [Fade Out].

Copy this pop tagged-lyrics skeleton at 108 BPM

A tight pop form usually wants a short intro, 4-line verses, a 2-line pre-chorus, a 4-line chorus, and a bridge before the last chorus. This 108 BPM setup gives the model enough structure without overfeeding it.

Style field: pop rock, 108 BPM, G major, hopeful, restless, clean electric guitar, punchy drums, round bass, wide chorus vocals, room reverb, clear male vocal

Lyrics field:

[Intro]

[Verse 1]
I drew a map on the back of a receipt
You held the wheel while the city fell asleep
We left our names on a window full of rain
I heard the road call out the title phrase

[Pre-Chorus]
Every red light turned to gold
Every doubt let go

[Chorus]
We run all night to find the morning
We run all night through the warning
We run all night, hearts wide open
We run all night and call it hope

[Verse 2]
Your jacket smelled like smoke and gasoline
The radio cracked but it carried the dream
We chased the dawn past the county line
I saw the title phrase in your eyes

[Pre-Chorus]
Every red light turned to gold
Every doubt let go

[Chorus]
We run all night to find the morning
We run all night through the warning
We run all night, hearts wide open
We run all night and call it hope

[Bridge]
If the old life calls, let it ring
We are more than what we leave

[Chorus]
We run all night to find the morning
We run all night through the warning
We run all night, hearts wide open
We run all night and call it hope

[Outro]
We run all night and call it hope
[End]

Chord map: in G major, try verse I-V-vi-IV, which is G-D-Em-C. Pre-chorus ii-IV-V is Am-C-D. If the chorus comes back with a new melody, paste the chorus block exactly the same each time. For turning a finished lyric into audio, follow the lyrics to song workflow.

Copy this EDM skeleton with [Build] and [Drop] at 126 BPM

Laptop and headphones in a warm electronic music workspace

An EDM form works better when [Build] carries the vocal tension and [Drop] stays empty or nearly empty. A normal 4-line chorus under [Drop] often makes the vocal sing across the drop, which weakens the payoff.

Style field: melodic house, 126 BPM, F# minor, euphoric, tense, sidechain bass, four-on-the-floor kick, bright synth plucks, wide pads, club mix, airy female vocal

Lyrics field:

[Intro]

[Verse 1]
Neon on the ceiling
Your shadow by the door
I feel the bassline breathing
I cannot wait anymore

[Build]
Take me higher

[Drop]
(oh-oh)

[Verse 2]
Hands up in the strobe light
Heartbeat on the floor
Every second opens
Like we have been here before

[Build]
Take me higher

[Drop]
(oh-oh)

[Breakdown]
Quiet in the blue light
Say it once more

[Drop]

[Outro]
Take me higher
[Fade Out]

Expected result: vocal setup, riser build, instrumental drop, stripped breakdown, final drop, soft fade. One change if it misses: delete normal lyric lines under [Drop] and leave only one parenthesized chop, or nothing at all. This same split between words and sound also helps with text to song prompts.

Troubleshoot one symptom, then change one thing

The fastest repair is to name the exact symptom and change one variable. Rewriting the whole song after every bad result hides the cause.

Symptom	Likely cause	One change
Vocal sings Chorus or Verse	Tag is lower-case, misspelled, or inline	Put a known tag alone on its own line.
First lines act like verse, no intro	Text before first tag	Move those words under `[Verse 1]`.
Chorus changes each time	Chorus text differs	Paste the exact same chorus block.
Section feels rushed	Long or uneven lines	Cut the longest lines toward the section median.
Second verse mumbles	Verse is too long or merged	Split into `[Verse 2]` and `[Verse 3]`.
No bridge appears	Bridge is too short or form is crowded	Give `[Bridge]` 2-4 lines, or remove one earlier chorus.
Wrong genre	Style prompt starts vague or conflicts	Put one genre first.
Vocal is buried	No vocal descriptor	Add `clear male vocal` or `warm female vocal`.
Ending is abrupt	No closing tags	Add `[Outro]` with one title line, then `[End]`.
Fade runs into noise	Lyrics after fade	Put `[Fade Out]` last.
Drop is sung over	Lyrics under `[Drop]`	Leave `[Drop]` empty or use one parenthesized phrase.
Tempo feels wrong	BPM missing or late	Put `126 BPM` early in Style.

A good fix is boring. One edit. New render. Listen for that symptom only.

Invented Suno tags are a gamble

You can invent tags, but known tags are safer because unknown bracket text can be sung like normal lyrics. Behavior also shifts over time, so a custom tag that behaves once may not stay dependable.

Risky invented tag	Safer known tag	Better Style-field wording
`[Massive Cathedral Choir]`	`[Gang Vocals]`	`large choir backing vocals, wide reverb`
`[Super Emotional Bit]`	`[Bridge]`	`intimate bridge, sparse piano`
`[Crazy Bass Explosion]`	`[Drop]`	`heavy sidechain bass, club mix`
`[Everyone Sings Here]`	`[Chant]`	`crowd chant hook`
`[No Singing Please]`	`[Instrumental]`	`instrumental` with lyric lines removed

The better move is usually a known tag plus plain words somewhere else. Example: use [Gang Vocals] above (everybody now), then put gang vocals in the chorus in Style. That gives the generator a section cue, a small singable response, and a sound direction. Other AI song tools may read brackets differently, but clean section labels still make your lyric block easier to understand.

Frequently asked questions

01Do Suno meta tags really work?

Yes, they can steer section order and delivery, especially common tags like [Verse 1], [Chorus], [Bridge], [Build], and [Outro]. They are still hints, not commands. Clean formatting matters more than exotic labels: one tag per line, short sections, no text before the first tag, and repeated chorus blocks copied exactly.

02Why does it sing the word Chorus out loud?

It is probably reading the tag as lyric text. Common causes are [chorus] in lower-case, a missing bracket, a made-up tag, or an inline line such as [Chorus] We run all night. Fix only that first: write [Chorus] alone on its own line, then put the chorus lyric below it.

03Should tags go in the style box or the lyrics box?

Put bracket tags in the Lyrics field. The Style field is for sound choices: genre, BPM, key, mood, instruments, production, vocal type, and language if needed. A tag like [Drop] in Style does not place the drop inside the lyric structure. It just clutters the sound brief.

04How many lines should sit under each tag?

Use 4 lines for a verse, 2 lines for a pre-chorus, 4 lines for a chorus, 2-4 lines for a bridge, and 1-2 lines for an outro. Keep most sections around 12 lines or fewer. Long blocks, especially with uneven line lengths, often get rushed or partly skipped.

05Can I invent my own tags?

You can try, but invented tags are risky. Unknown bracket text may be ignored or sung aloud. Use known tags for structure, then describe the extra idea in Style. [Chant] plus crowd chant hook is clearer than [Everybody In The Stadium Sings This Huge Part].

06Do these tags work in other AI music generators?

Some bracket habits transfer, but every AI music generator can read tags differently. The safe habits still help: keep section labels alone on their own lines, separate lyrics from sound descriptions, use short sections, and avoid directions you would hate to hear as sung words.

07How do I end a song cleanly?

Add [Outro] with 1-2 closing lines, often the title phrase or final image, then put [End] as the last line for a hard stop. For a fade, put [Fade Out] last and add nothing after it. [Big Finish] can support the last chorus, but it is not a full ending by itself.