Suno meta-tags

Last modified: 2025, August 26.

Suno service news (updated: July 18, 2025)

On 18-th of July Suno has released for paid subscriptions, access to a new model, “v4.5+”

The initial tests showed that v4.5+ generated more variable, richer tracks with better polyphony and overall quality. Typical restrictions are the same as for v4.5. It’s not yet known if there are changes in how v4.5+ interprets meta-tags.

Also, the “Inspo” tool has been added to tracks generation UI. That, according to the UI hint, uses songs from specified playlist as “source for inspiration” In practice, Suno blends the “inspiring” tracks, making kind of pot pourri in the output. No formal definitions for “Inspo” was officially done yet.

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 (consider obsolete)

Tag	Status	Notes
`[autotune: ...]`	❌ Unsupported
`[filter: ...]`	❌ Inefficient
`[loop: ...]`	❌ Unsupported
`[mix, mixing: ...]`	❌ Inefficient
`[master: ...]`	❌ Inefficient
`[pan, panning: ...]`	❌ Inefficient
`[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.
`[volume: ...]`	❌ Inefficient

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

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
```