We read every Suno prompt guide so you don't have to.

What Suno actually rewards

We pulled this from Suno's official guidance and what works in production. The short version:

• →Keep Style box focused on sonic intent.
• →Put structure tags in Lyrics box.
• →Restate genre to bias more strongly.
• →Use [Instrumental Intro] (intros are unreliable as [Intro]).
• →Use sound-alikes from prompt-style lists, not literal artist names.

Common mistakes we fix automatically

• Avoid
  Don't put song-structure tags in Style box.
• Avoid
  Don't use literal artist names of major copyrighted acts (filtered).

Frequently asked questions

Which versions of Suno does this support?

We support v3.5, v4, v4.5, v5. We apply the prompt patterns Suno recommends for each, so the rewrite is tuned to the version you're using.

Is my prompt stored or used for training?

No. Prompts are sent to the rewriter, scored, returned, and discarded. We don't train on them and we don't keep them around.

Do I need to know prompt engineering to use this?

Nope. That's the point. Paste what you have, click Rewrite, get back a version that follows Suno's official guidance.

What makes this different from Suno's own "improve prompt" feature?

Built-in optimizers use the model's own preferences. Ours is built on Suno's official documentation and patterns that consistently produce better results in production. We keep rewrites inside the length window Suno responds best to.