Field specs & limits

Style field

Length and token priority

• Length: Treat Style as a long text box—models read dense prompts, but extremely long strings may truncate or weigh late tokens less. Build the important ideas first.
• Commas: Separate ideas; stacks like “genre, instruments, mood” are normal (see Prompt Builder).
• Line breaks vs one block: Both can work—consistency matters more than format. Prefixed lines (Genre: …) aid human reading.

Lyrics field

Structure and caps

• Structure: Use tags for sections; very long lyrics may be split or summarized by the model.
• Character limits: If the box stops accepting input, trim repeated choruses or move detail to Style where appropriate.

Check in the Suno app

Why verify in the live product

Exact character counts and field behavior change with app versions—always confirm in the live product and on suno.com (help or announcements) when you need authoritative limits.

Quick self-checks

• Style box: Paste a long Style string; if input stops accepting characters or text appears clipped after save, shorten from the lowest-priority phrases first.
• Lyrics box: If you cannot type or paste further, remove duplicate sections or move non-essential lines into a note outside Suno.
• Multi-line Style: After generating, confirm whether line breaks you typed are still present—some flows may normalize to a single block.

Practical tip

Budget for negatives

Reserve space for negative hints if you need them—don’t fill Style with low-value adjectives first.