Suno meta-tags

Last modified: 2025, July 16.

See the latest version(s) on GitHub: stayen/suno-reference.

Riffusion relation

Since April 27, 2025 Riffusion.com audio tracks generation service (very much like Suno) introduced paid levels of membership and a new model FUZZ-1.0 Pro.

After 400+ generations that were first tested in Suno and then in Riffusion (“Style of Music” at Suno going to “Sound” prompt at Riffusion; “Lyrics” going to “Lyrics”) it was discovered that Riffusion generally follows the same set of official and user-tested meta-tags known for Suno.

Known misbehaving tags/tags values

Tag	Status	Notes
`[style: none]`	❌ Invalid	“none” is not interpreted as a meaningful style. Will confuse output.
`[section: ...]`	❌ Redundant	Rejected or misread; use `[intro: ...]`, `[verse: ...]` etc.
`[theme: ...]`	❌ Invalid	unlabelled theme tag is ignored or causes parsing errors, use [theme A: …] etc.

Tips on using meta-tags

Use only known or confirmed tags.
Avoid alias or ambiguous tags like bpm, key, language.
Test in Standalone mode first — many tags that break in Extend or Cover work fine solo.
If in doubt, use “[style: experimental]” or “[control: hallucinatory]” to encourage flexible output instead of forcing

Important changes made in July 15, 2025

The following tags deleted as either highly unstable or not supported: accent, autotune, bpm, emoion, key, language, loop, master, melody, mix, filter, panning, style:none, sing-style, section, song-type, unlabeled theme, volume, intensity

Parsing Note for Suno v4.0+

Any unrecognized tag (e.g. [emotion build], [tense development]) is treated as a generic [section X: …] tag.

Use colon syntax to embed directives safely:

[tense development: Style and mood of the theme gets more tense until a climactic counterpoint is reached]

Avoid placing instruction text outside the tag, as it will be sung/spoken:
```
[tense development]
Style and mood... ← ❌ becomes lyrics
```
Avoid inserting lyrics/text to sing as [verse] colon notation: the engine will only sing that text if doesn’t find obvious rendering directives; place the verse lyrics immediately below its [verse] tag