Suno AI Meta Tags & Song Structure Command Guide
Verified for Suno Studio workflows: Jan 12, 2026 • Updated: Jan 16, 2026
Suno AI Meta Tags & Song Structure Command Guide
If you’re here to fix output now: jump straight to the copy templates below.

Jump to what you need
What This Page Is (and Isn’t)
This is a command-style reference for writing [bracket] structure labels and section-local “producer cues” inside Suno’s Custom Lyrics workflow—then finishing cleanly in Studio.
- Commands that reduce drift and repetition
- Placement rules that actually change outcomes
- Studio finishing for fades, tempo lock, loops, stems, and exports
This page stays narrow on purpose: commands + workflow. If you want the bigger “tag library” and advanced placement strategy across Style vs Lyrics, use the VIP references below.
Quick Start (copy/paste first)
[Mood: Focused] [Energy: Medium] [Instrument: Keys, Drums] [Intro] (keep it short; establish palette) [Verse] (tight lines; story lane) [Pre-Chorus] [Build-Up] (shorter phrasing; raise anticipation) [Chorus] [Energy: High] (simple hook; biggest lift) [Bridge] [Breakdown] (space + contrast) [Final Chorus] [Energy: High] (same hook; biggest version) [Outro] (leave room for a Studio fade)
Meta Tags: Practical Definition
In creator use, “meta tags” usually means bracketed cues placed in or around lyrics to signal: sections, energy turns, and performance direction.
- Section tags (best ROI): [Intro] [Verse] [Chorus] [Bridge] [Outro]
- Descriptor tags (use sparingly): [Mood: …] [Energy: …] [Vocal Style: …] [Instrument: …]
Placement Rules That Actually Change Outcomes
| Rule | What to do | Why it helps |
|---|---|---|
| Top-load the palette | Before your first lyric line, include: 1 mood + 1 energy direction + 1–2 key instruments. | Reduces “random first 10 seconds” and keeps early arrangement choices consistent. |
| Localize the hard turn | Place [Energy: High] immediately before the chorus (not only at the top). | Prevents verses from coming in too hot; makes the chorus feel like a lift. |
| One job per tag | Avoid conflicts like [Mood: sad, happy, angry]. | Conflicts get averaged and you lose emotional clarity. |
| Fewer instruments = cleaner stems | Pick 2–3 anchor timbres instead of a long shopping list. | Cleaner arrangement choices, less clutter, easier multitrack export workflows. |
| Write for performance | Keep lines tighter (short lines are easier to articulate consistently). | Improves intelligibility and reduces rushed phrasing. |
Core Structure Commands
Primary section tags
| Tag | Best use | Common fix when it fails |
|---|---|---|
| [Intro] | Establish palette; keep it short and clear. | If it starts too loud, reduce instrument cues and add a calm mood cue before the intro. |
| [Verse] | Story lane; lower density than chorus. | If verse repeats, write a clear Verse 2 with an angle shift (new images, new details). |
| [Chorus] | Hook lane; strongest energy cue. | If chorus doesn’t lift, place [Energy: High] immediately before it and shorten the hook lines. |
| [Bridge] | Contrast lane; change harmony, rhythm, or space. | If bridge feels like Verse 3, strip drums or switch to half-time feel, then return to full chorus energy. |
| [Outro] | Resolve lane; plan the landing. | If it cuts hard, keep the last lyric line short and plan a Studio fade. |
Optional “energy mechanics” tags
Use these only when you need a clear dynamic move (don’t apply everywhere).
- [Build] / [Build-Up]: gradual lift into a chorus/drop
- [Drop]: impact lane (beat-forward hook moment)
- [Breakdown]: strip-back contrast (space + tension)
Command Templates You Can Reuse
Template A: Structure-first song
[Mood: Focused] [Energy: Medium] [Instrument: Keys, Drums] [Intro] (quiet movement; establish palette) [Verse] (story lane; tight lines) [Pre-Chorus] [Build-Up] (raise anticipation; shorter phrasing) [Chorus] [Energy: High] (repeatable hook; simplest words; biggest lift) [Verse 2] (new angle; same pocket) [Chorus] (keep hook consistent) [Bridge] [Breakdown] (space + contrast) [Final Chorus] [Energy: High] (biggest version; keep hook the same) [Outro] (leave room for a Studio fade)
Template B: Loop-first (Shorts/Reels/TikTok)
Build a clean 20–35 second hook segment, then export a Selected Time Range loop in Studio.
[Hook Loop] [Mood: Confident] [Energy: Medium→High] [Instrument: Bass, Drums, Simple Lead] (loop-friendly; minimal variation; clean downbeat) (repeat hook lyric; keep cadence identical)
This page stays command-focused. The VIP guide covers the broader system.
Studio Workflow: Turning Tags Into Finished Audio
- Region editing: copy, duplicate, delete, crop, and heal edits on Regions.
- Clip Settings: tempo behavior (on beat vs original), transpose (semitones), speed, and volume.
- Fades: adjustable fade in/out on clip edges.
- Export options: Full Song, Selected Time Range, Multitrack (stems).
Studio actions that pair with tag-based structure
| Your problem | What you do in lyrics/tags | What you finish in Studio |
|---|---|---|
| Outro ends too abruptly | Add [Outro] and keep the last line short. | Add a fade out on the Region (clip edge fade). |
| Tempo drift breaks DAW import | Don’t over-tag; keep the arrangement focused. | Set Manual BPM (consistent tempo), then export Multitrack and match tempo in your DAW. |
| Need a clean loop for social | Write a dedicated hook loop section. | Export Selected Time Range for that loop segment. |
| Need a remix-ready session | Write clean section boundaries and avoid instrument sprawl. | Export Multitrack; optionally extract stems and generate MIDI from stems if needed. |
Export and MIDI notes (quick, practical)
- Export scopes: Full Song / Selected Time Range / Multitrack (stems).
- Export a single element: you can download an individual clip (WAV) from the timeline context menu.
- MIDI-from-stems: Studio can generate MIDI from a stem (“Get MIDI”) and this is a paid action (credit cost applies).
Advanced Notes (keeps this page distinct)
1) Section boundaries are your real control surface
Tags work best when the writing supports them: a chorus that reads like a chorus (short, repeatable hook), and a bridge that reads like a bridge (contrast + space). Tags reinforce the intent—they don’t replace it.
2) Plan Replace/Extend outcomes in your lyric map
Most “fix passes” happen because the chorus is too wordy, the bridge doesn’t contrast, or the ending lands wrong. If you design compact chorus lines and clear transitions, you need fewer corrective edits later.
3) If you’re exporting stems, design for stems
Keep the palette focused. Cleaner boundaries and fewer instrument cues usually export into cleaner sessions.
Clean Example Prompt (Command-First)
[Mood: Calm] [Energy: Medium] [Instrument: Keys, Soft Drums] [Intro] (quiet movement; space) [Verse] I kept my head down, stayed on the line Small wins stacking up over time [Pre-Chorus] [Build-Up] Now the air feels different when I breathe [Chorus] [Energy: High] We don’t fold, we don’t fade We step forward, unafraid [Bridge] [Breakdown] Let it breathe, let it break, let it rise again [Final Chorus] [Energy: High] We don’t fold, we don’t fade We step forward, unafraid [Outro] Hold the last word; leave room for a Studio fade
Related references (go deeper)
Change Log
- June 2025: rebuilt for v4.5 tag behavior and structured lyric workflows.
- Oct 2025: revised for V5 Studio workflow emphasis (region editing, clip settings, fades, tempo lock, exports).
- Jan 12, 2026: verified for continued relevance against Suno Studio workflow docs.
- Jan 16, 2026: reduced duplication, clarified exports/MIDI/tempo-lock notes, added VIP reference links.
This page is intentionally command-focused and avoids duplicating the broader “tag library” and “Style vs Lyrics” deep-dive pages.