Everything you need to write Suno V5 prompts that produce sharp results. Limits, tags, metatags, structure, tested examples — straight from the docs.
Suno is now the reference platform for generating music with AI. But between a beginner prompt that produces generic mush and a precise prompt that sounds like a real production, there is a documented grammar. This guide covers the current syntax (Suno V5 / V5.5, April 2026), the metatags that are actually recognized, and the common traps.
Update, November 8, 2026: Suno moved to V6 on September 9. The syntax below still applies; for the new models and which one to pick, read our Suno V6 prompt guide.
Two numbers change everything in a Suno prompt:
A Suno prompt has two distinct fields, and they do not play the same role:
[Verse], [Chorus], etc.) on their own line.Order in the Style field has weight: the first tags pull more. Follow the formula that shows up in nearly every pro guide:
neo-soul, alt-r&bsensual, laid-backmale falsetto, vocal runswarm rhodes, analog bass, vintage tape78 BPMSuno recognizes a stable set of tags placed on their own line in the Lyrics field. Here are the structurally meaningful ones, used by the community and confirmed in current docs:
| Metatag | Use |
|---|---|
[Intro] | Track opening |
[Verse] / [Verse 1] | Verse section |
[Pre-Chorus] | Lift before chorus |
[Chorus] | Hook / refrain |
[Bridge] | Mid-song break |
[Build] / [Drop] | EDM / electronic energy |
[Break] | Pause / dropout |
[Instrumental] | No vocals on this section |
[Outro] | Closing |
Two things to keep in mind. First: place each metatag on its own line, with no leading or trailing space. Inline tags inside a verse line are usually ignored. Second: Suno treats them as signal weights, not hard switches. They bias the section identity, energy and arrangement density — they do not force a specific outcome.
To shape the vocal performance, place a voice tag on a line just before the lyric line that should follow:
[Verse]
[Whispered]
I keep your photo in my coat
[Chorus]
[Belted]
But you don't know me anymoreThe most reliable voice tags: [Whispered], [Belted], [Falsetto], [Spoken], [Choir], [Auto-Tuned], [Harmonized], [Ad-lib]. Avoid trying to direct emotion through long descriptions — Suno reads the music in the lyric itself better than a long emotional brief.
Beyond ~20, Suno averages instead of choosing. The result is generic. Cut to the 8-12 tags that actually matter for the track.
"in the style of [famous artist]" is filtered (rights protection). Decompose the artist's signature into technical tags instead — that is exactly what the ToneDraft music board does with Sounds Like.
[Verse], [Chorus], [Drop] belong in the Lyrics field, never in Style. In Style they are at best ignored, at worst they confuse the model.
Without an explicit BPM, Suno guesses based on genre. Lock it: 120 BPM, 140 BPM, etc. The platform respects BPM when stated.
Style is keyword-driven, not narrative. "A melancholic song reminding me of a rainy night in Tokyo with neon lights and someone I miss" makes for a bad prompt. melancholic, neo-soul, rainy night vibe, neon ambient pads, tokyo lo-fi, 75 BPM works far better.
Style:
alt-r&b, neo-soul, sensual, moody, male falsetto, vocal runs, rhodes, warm analog bass, vintage tape, intimate bedroom production, 78 BPMLyrics (excerpt):
[Intro]
[Soft]
mmm... yeah...
[Verse 1]
Late night calls, you don't pick up the phone
Streetlight glow on the bedroom wall
[Chorus]
[Belted]
But I'd still come over if you asked me to
And you know it's true
[Bridge]
[Falsetto]
Maybe we were never meant for daylightFor consistent results across multiple tracks, build your prompts in 4 steps:
That iteration loop is exactly what the ToneDraft music board automates. You pick from a curated tag library across 18 dimensions, lock the ones that work, spin the rest. The output is a Suno-ready prompt you copy and paste.
Above all, treat Suno as an instrument. The prompt is your score. The more precise the score, the closer the result lands to what you hear in your head.