Suno AI Meta Tags & Song Structure Command Guide
Originally published in 2024, rebuilt in June 2025 for Suno v4.5, revised in Oct 2025 for Suno V5 behavior. Verified for Jan 12, 2026 against Suno Help Center Studio workflow references (editing, tempo, export, stems).
Suno AI Meta Tags & Song Structure Command Guide
What This Page Is (and Isn’t)
This page is a command-style reference for using [bracket] tags as section markers and “producer cues” inside Suno’s Custom Lyrics workflow. It focuses on:
- How to write sectioned lyrics Suno can follow (structure commands that reduce drift and repetition)
- How to place tags for maximum influence (top-loading vs section-local cues)
- How to finish in Studio (tempo locking, clip settings, fades, stems, exports)
Suno’s Help Center documents the Studio workflow (editing, tempo lock, stem export, multitrack export). This page maps your lyric/tag structure to those Studio actions. Studio references: editing tools and clip settings, fades, and undo are described in Suno’s “Editing in Studio” article; tempo drift and manual BPM are covered in “Fixing Tempo Drift”; export options (full song, selected range, multitrack, MIDI) are covered in “Exporting from Studio.”
Meta Tags: Practical Definition
For creators, “meta tags” usually means bracketed cues placed in or around lyrics to signal: sections, energy changes, 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 your intent | Put core structure + 1 mood + 1–2 instruments before the first lyric line. | Early tokens are weighted more; this reduces “random first 10 seconds.” |
| Localize the hard turns | Place [Energy: High] directly before the chorus, not globally at top. | Keeps verses from coming in too hot; makes the chorus feel like a lift. |
| One job per tag | Avoid stacks like [Mood: sad, happy, angry]. | Conflicts cause averaging and “vague emotion.” |
| Use fewer, clearer instruments | Pick 2–3 key timbres (e.g., Rhodes, live drums, bass) instead of a shopping list. | Cleaner arrangements; less clutter and fewer unexpected swaps. |
| Write for performance | Keep lines tighter for clarity (shorter 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, add a “soft” cue and reduce instruments in the intro. |
| [Verse] | Story lane; lower density than chorus. | If verse repeats, add a second verse with a clear angle shift. |
| [Chorus] | Hook lane; strongest energy cue. | If chorus doesn’t lift, place [Energy: High] immediately before it. |
| [Bridge] | Contrast lane; change harmony, rhythm, or space. | If bridge feels like Verse 3, reduce drums and add one new timbre. |
| [Outro] | Resolve lane; plan the landing. | If it cuts hard, finish in Studio with fades (see Studio section below). |
Optional “energy mechanics” tags
Use these only when you need a clear dynamic move. Don’t apply them everywhere.
- [Build] or [Build-Up]: gradual lift into a chorus/drop
- [Drop]: beat-forward impact moment (EDM/club/viral hook lane)
- [Breakdown]: strip-back for contrast (space + tension)
Command Templates You Can Reuse
Template A: Pop / Rap / Worship (structure-first)
[Intro] [Mood: Focused] [Instrument: Keys, Drums] [Verse] (keep lines tight; set the story) [Pre-Chorus] [Build-Up] (raise anticipation; shorter phrasing) [Chorus] [Energy: High] (repeatable hook; simplest words; biggest lift) [Verse] (new angle; same pocket) [Chorus] (keep hook consistent) [Bridge] [Breakdown] (space + contrast) [Final Chorus] [Energy: High] (biggest version; keep hook the same) [Outro] (close it; plan a fade in Studio)
Template B: Loop-first content (export a “Selected Time Range” loop)
If your goal is Shorts/Reels/TikTok: build a clean 20–35 second “center loop,” then export it from Studio as a selected range. Suno’s Studio export menu includes “Selected Time Range,” which is built specifically for this workflow.
[Hook Loop] [Mood: Confident] [Instrument: Bass, Drums, Simple Lead] (loop-friendly; minimal variation; clean downbeat) (repeat hook lyric; keep cadence identical)
Studio Workflow: Turning Tags Into Finished Audio
- You can edit Regions (copy, duplicate, crop, heal), add fades, and adjust clip settings like tempo behavior, transpose, speed, and volume.
- You can lock tempo via Manual BPM when a performance drifts (common in older/live-feel styles), then export stems cleanly for a DAW.
- You can export a Full Song, a Selected Time Range (loop), or Multitrack (stems), depending on the goal.
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 fade out on the Region (Studio fades are adjustable on clip edges). |
| Tempo drift breaks stem import | Don’t over-tag; keep the arrangement simple. | Set project tempo to Manual BPM to lock tempo; then export multitrack and set the same tempo in your DAW. |
| Need a clean loop for social | Write a dedicated hook loop section. | Export “Selected Time Range” for the loop segment. |
| Need a remix-ready session | Write cleaner section boundaries. | Extract stems and export Multitrack; optionally export MIDI from stems for deeper edits. |
Advanced Notes That Keep This Page Distinct
1) “Section boundaries” are your real control surface
In practice, the best “meta tag control” comes from clear section boundaries: a chorus that is obviously a chorus (shorter, repeatable, hook language), and a bridge that is obviously a bridge (contrast and space). Tags support that. They don’t replace it.
2) Replace/Extend planning starts in the lyric map
Even before you touch Studio edits, your lyric map should anticipate: what might need replacement (usually chorus clarity, bridge contrast, outro landing). If you write your chorus with compact lines and a repeatable hook, you reduce the need for corrective Replace passes.
3) If you’re exporting stems, design for stems
If the plan is to export Multitrack stems, keep the instrument list focused. In Studio, you can extract stems and export Multitrack; you can also export MIDI from stems when available. That workflow is documented in Suno’s Studio export guidance.
Clean Example Prompt (Command-First)
[Intro] [Mood: Calm] [Instrument: Keys, Soft Drums] [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
Change Log
- June 2025: rebuilt for v4.5 tag behavior and structured lyric workflows.
- Oct 2025: revised for V5 Studio workflow emphasis (editing Regions, clip settings, fades, tempo lock, exports).
- Jan 12, 2026: verified for continued relevance; no conflicting Studio workflow changes found in Suno Help Center articles last edited Sep–Oct 2025.
Updated: Jan 12, 2026 • This page is intentionally command-focused and avoids duplicating the broader “evolution narrative” on the master meta page.