The Suno Style String: An 11-Field Anatomy of a Complete One

There are two ways to write a style prompt, and they suit different workflows. The short ordered prompt — genre, instrumentation, vocal, vibe, under 20 words — is the right tool when you're iterating by hand and want to change one variable per render; the style-prompt anatomy guide covers that strategy. The complete style string is the right tool when you know exactly what the song should be and want to specify it once: every field stated, nothing left to the engine's defaults. Our forge uses the complete strategy, because by the time the style string is written the writing room has already made every one of these decisions.

The checklist our forge writes against, with an example phrase for each:

1. Genre + subgenre + era. "Indie folk-rock with alternative undertones." The era does real work: "2007 indie blog era" and "1973 Laurel Canyon" are different productions of the same genre word.
2. Vocal gender. Stated explicitly — "female vocal," "male vocal." Leaving it out is a coin flip.
3. Vocal texture + character. "A warm alto that cracks on the high notes."
4. Vocal delivery dynamics. "Building from hushed confessional verses to soaring belt-it-out choruses." This field is where performance intent lives — verse half-spoken, chorus belted, the bridge held back — described as prose rather than scattered through the lyric as tags.
5. Full instrumentation. Named instruments, not categories: "fingerpicked acoustic guitar, upright bass, brushed drum kit, understated piano fills."
6. Production aesthetic. "Lo-fi analog production with tape warmth."
7. Spatial/reverb character. "Natural room reverb, close-mic'd vocals where you can hear every breath, wide stereo field."
8. Tempo/BPM. "82 BPM." A number beats an adjective; "slow" spans 40 beats per minute of ambiguity.
9. Key. "In the key of D minor." The cheapest mood lever in the whole string.
10. Atmosphere/emotional color. "Melancholic yet hopeful, like the first light after a sleepless night."
11. Dynamic arc. "Stripped solo acoustic opening building to a full arrangement by the final chorus, then pulling back to a single voice for the last line." The one field almost everyone omits, and the difference between a song with a shape and three minutes at one volume.

The complete string is written as flowing prose, not a comma pile of genre tags. A style string that reads as a sentence gives the engine relationships between the fields — this vocal over this instrumentation in this room — where "folk, acoustic, sad, slow" gives it four disconnected words. Density also has a budget: our spec is 700-900 characters because shorter strings under-specify and longer ones start repeating themselves. Every phrase should add a dimension no other phrase covers.

Internal contradiction. "Upbeat melancholy" cancels itself out; so does a gentle-acoustic string paired with a lyric whose chorus demands detonation. The style string and the lyric's section directives must agree about who owns the dynamic arc.

Real artist names. "Sounds like [artist]" risks refusal on every major engine — our pipeline scrubs names from style strings before they reach any provider. Field 1's era + production description is the safe encoding of the same intent, and it transfers between platforms (what transfers and what breaks).

The fastest way to apply the checklist: take the style prompt you were about to use and count which of the 11 fields it answers. Most hand-written prompts cover three or four. You don't always need all 11 — but every field you leave blank is a decision you've delegated to the engine's defaults, and the engine's defaults are the average of everyone else's songs. Specify what matters, and make it the things only you would choose.