How do you turn your poem into a song with AI without wrecking the poem?

Here is a twelve-line poem. Call it yours for the length of this page:

The kitchen light stays on past two.
My father's cup is on the sill,
a ring of tea, dry and brown,
the spoon still standing in it.

He fixed the clock above the door
with wire from an old radio.
It runs four minutes fast. We never
set it back. We let it go.

I wash the cup and leave the ring.
Some stains are how a room remembers.
The clock says it is later than it is.
It always was. It always will be.

There are two common ways to turn this into a song with AI, and both damage it. The first is to paste it raw into a music generator and press create. The model gets three stanzas of equal weight, no section that comes back, and an enjambment ("We never / set it back") that splits a thought across a phrase boundary. The second is to ask a chatbot to "make this into a song". That one is worse, because the chatbot will hand you something that looks finished: tidy rhymes, a big chorus, and a sentence about grief the poem was careful never to say.

There is a third way, and it is the subject of this page. You keep every word. You change only the order of repetition, the line breaks and the labels. Then you describe the sound in a separate field and let a music tool sing it.

Which page you actually need

If you do not have a poem yet and want a machine to write one, read which AI poem generator writes verse worth keeping instead. That page compares poem tools. This one is for the person who already has the poem, wrote it themselves, and wants to hear it sung without it turning into somebody else's text.

If what you have is already a song lyric (it has a chorus, it repeats, you wrote it to be sung), skip ahead to turning lyrics into a song, which covers the handoff into Suno's fields in detail. A poem needs one extra stage before that handoff, and that stage is where most of the damage happens.

What a poem is missing, from a singer's point of view

A poem is read at the reader's speed. The eye can slow down on a hard line, go back, skip ahead to see how a stanza ends. A song moves at the band's speed and nobody can go back. That single difference produces almost every adjustment below.

Repetition. A listener needs something to hold on to, and in a song that thing is a section that returns. Most poems never repeat a line, because on the page repetition reads as padding. In a song the absence of repetition reads as a lecture.

Line as breath. In a music generator, a line break is roughly where a melodic phrase ends. A line that carries its sentence over into the next ("We never / set it back") forces the singer to break the thought in the middle, or to rush through the break. On the page that enjambment is an effect. Sung, it often just sounds like a mistake.

Labels. A generator needs to know which lines are a verse and which are a chorus. In Suno's Lyrics field that is done with square-bracket tags such as [Verse] and [Chorus], and the rule is strict: everything outside square brackets gets sung. A stanza number, a title at the top or a note to yourself in parentheses will come out of the speaker as words.

A sound. A poem has no instrumentation. A song needs one, and it goes in a separate field from the words. Leave it empty and the tool picks its own default, which is rarely what the poem wants.

None of these needs a single word of the poem to change. That is the important part.

The contract: rearrange and repeat, never reword

Before touching the poem, decide what you are allowed to do to it. Writing the rule down sounds fussy. It is the thing that stops you from "just fixing one word" eleven times.

Everything in the left column changes how the poem is performed. Everything in the right column changes what the poem says. If a section only works after a right-column edit, that is real information: the poem may need a sung part you have not written yet, and the honest move is to write it yourself, deliberately, rather than let it slip in.

Step 1: mark the sections

Read the poem and ask of each stanza: is this telling the story forward, or is this the thing the poem keeps circling back to? The first kind becomes a verse. The second kind is your chorus candidate.

In the kitchen poem, stanzas one and three move the story: the cup on the sill, then washing the cup. The second half of stanza two is different. "It runs four minutes fast. We never set it back. We let it go." That is the thought the whole poem is built around, the family that chose not to correct something because correcting it would erase the person who broke it. It is the chorus. You did not write it as one, but it already is one.

The last line of the poem is the other candidate: "It always was. It always will be." It sounds like an ending, so it becomes the outro. The line before it ("The clock says it is later than it is") is a turn, a single image that reframes everything, and a lone line like that sits well as a short bridge.

Step 2: find the chorus inside the poem

The chorus is where most people give up and start rewriting. Three places to look first:

1. The line that survives being said three times. Read each candidate out loud three times in a row. Most lines go flat by the second repeat. The one that gets heavier is the chorus.
2. The last two lines. Poems often end on their thesis. If your closing couplet still makes sense out of context, it can return.
3. The phrase you would use as the title. If you had to name the poem with one of its own lines, that line wants to come back in the song.

If none of the three works, the poem may honestly not have a chorus in it. You have two clean options. Leave it through-composed: tag every stanza as a verse and accept a song without a refrain, which is a legitimate form, closer to a ballad or an art song than to pop. Or write a chorus yourself, as a new part, in your own voice, and keep it visibly separate from the poem in your own notes.

A third option exists and it is worth describing accurately. The lyric generator on this site, at /generators, takes a form brief (a theme of up to 800 characters, a point of view, an emotion, a structure, a hook type) and writes a complete new lyric with a title and section tags. It never sees your poem. It sees only the theme you summarise into that field. So it cannot "find the chorus in your poem". What it can do is draft a full lyric on the same subject, and you may find a chorus idea there worth adapting by hand. One SM1 generation costs 20 credits, which is $0.20; SM2 and SM3 add an editing pass that flags and rewrites weak lines and cost 80 credits. New accounts start at zero credits and there is no free trial, so check the plans first. Either way, that is a source of ideas, not a way to preserve the poem, and if preserving the poem is the point, the first two options are better.

Step 3: fix line length with breaks, not with words

Count syllables. A line around ten syllables or fewer is comfortable to sing as one phrase. Past twelve or so, a generator tends to cram the words into the bar or split the line wherever it likes, and either way you lose control of where the singer breathes.

The fix is almost always a line break, not a cut. "It runs four minutes fast. We never set it back." is twelve syllables across a sentence boundary. Broken at the full stops, it becomes two six-syllable lines, each a complete thought, each a natural breath. No word changed.

Two more things to check while you are counting:

• Enjambment. If a sentence runs over a line break, either re-break so the line ends where the sentence does, or accept that the singer will pause mid-thought. Pick one on purpose.
• Punctuation. A generator does not read commas the way an actor does. Full stops at the end of lines are harmless but useless; most people drop them so the sheet reads cleanly. Keep commas inside a line if they help you read it aloud; they cost nothing.

The kitchen poem, as a lyric

Here is the same poem after steps one to three. Not one word was added, removed or swapped. Capitals, punctuation and line breaks changed, the chorus returns once, and the words of the poem first appear in exactly the order they had on the page.

[Verse 1]
The kitchen light stays on past two
My father's cup is on the sill
A ring of tea, dry and brown
The spoon still standing in it

[Verse 2]
He fixed the clock above the door
With wire from an old radio

[Chorus]
It runs four minutes fast
We never set it back
We let it go

[Verse 3]
I wash the cup and leave the ring
Some stains are how a room remembers

[Bridge]
The clock says it is later than it is

[Chorus]
It runs four minutes fast
We never set it back
We let it go

[Outro]
It always was
It always will be

Three things to notice. The verses are uneven: four lines, then two, then two. That is fine. A short verse arriving at the chorus quickly is a known shape, and padding verse two to four lines would mean writing lines the poem does not have. The longest line, the bridge, is ten syllables. And the chorus lines are short, six, six and four syllables, which suits a chorus: it is supposed to be easy to catch on the first pass.

If you want a stronger refrain, you are allowed to repeat inside it. Singing "We let it go" twice at the end of each chorus is still your words. That is a performance choice, not a rewrite.

What happens when you let the AI do the whole job

Here is the kind of chorus a "make this poem into a song" request tends to produce. We wrote this one to show the pattern; it is not output copied from any particular tool:

[Chorus]
Oh the clock keeps ticking on and on
Four minutes fast and you are gone
We never turned the hands around
Your memory's the only sound

Each line is defensible on its own, and together they undo the poem. The original never says the father is dead. It shows a cup, a ring, a clock nobody corrects, and lets the reader work it out, which is why it lands. "And you are gone" says it out loud. "Your memory's the only sound" is a phrase that could close a thousand songs. The rhymes are tidier than anything in the original, and that tidiness is the problem: the model optimised for what songs usually sound like, and your poem was valuable because it did not sound like that.

This is the predictable result of asking a text model to convert a poem. It fills gaps with the most common choice, and the most common choice in a song lyric is a stated emotion with an end rhyme. If you do use a chatbot for this stage, give it the contract from the table above and ask only for a proposed section map ("which lines are verse, which is the chorus"), never for new text. Then check its answer against the original word by word.

Step 4: describe the sound in its own field

The poem says what is sung. It does not say how. In Suno's Custom mode that goes in the Styles field: a short line of English descriptors covering genre, tempo feel, instruments, vocal and production. For the kitchen poem, something like:

sparse acoustic folk, fingerpicked guitar, soft male vocal, close mic, warm, slow

Anything you do not want goes in the Exclude field (under Advanced Options in Custom mode) rather than as a "no" in Styles, because a negative written inside Styles is often read as a topic. The guide to fixing negative prompts explains why.

This is where this site is most useful for a poem, and it is worth being exact about it. The prompt generator at /generators builds that Styles line across every axis (genre, mood, tempo feel, vocal, instruments, structure), phrases everything positively and moves each "don't" into Exclude. It is deterministic, not an AI, and it never touches your words. The style catalogue has nearly 2 000 styles with recipes, and the artist recipes describe more than 4 000 artists' sounds without naming the artist, so Suno's block on artist names does not trip. Browsing the catalogue with full recipes for the ten most popular styles, all prompt guides and the first three preset categories of the prompt generator are free without a card; the full versions need a plan.

Step 5: where the singing happens

sunomarket.com is an independent site. It is not Suno, it is not affiliated with Suno or with any other company named here, and nothing on it produces audio. The singing happens in a tool you pick.

In Suno, the route is the one in their help article on using your own lyrics: open Create, switch to Custom, paste the tagged lyric into the Lyrics field, the sound description into Styles, give it a title. Everything on this site is built for Suno's format. A tagged lyric is plain text, so any tool with a lyrics box will accept it, but whether that tool treats [Bridge] as a structural instruction or sings it is something to test, not assume.

Expect to generate more than once. Two runs of the same input usually come back different. When one take gets the chorus right and fumbles a verse, keep the sheet as it is and run it again before you start editing words.

Rights, briefly

This is not legal advice, and the details depend on your country and on the terms of the tool you use. Suno's help centre states that you keep ownership of original lyrics you enter. The recording is a separate matter: Suno ties commercial use of a generated song to the plan you were on when you made it, and songs made on the free plan are for personal, non-commercial use under their terms at the time of writing. Read their current pages before releasing anything. For what this site does and does not grant on its own output, see the disclaimer, and for the wider picture, who owns AI-generated music.

When the first take is wrong

A tag or a note got sung. Something sat outside square brackets. Check for a title line, a stanza number, a parenthesis. The lyrics format guide lists every way a sheet leaks.

A line came out rushed or chopped. It is too long for one phrase. Re-break it at a natural pause. Count again.

The chorus does not feel like a chorus. It is probably not repeated enough, or it is longer than the verses. Repeat its last line, or cut it back to the two strongest lines and move the third into a verse.

The genre is wrong. That is the Styles field, not the poem. Change the description and leave the words alone. The guide to why Suno ignores a prompt covers the usual causes.

A word is stressed in the wrong place. A generator can stress a word differently from the way you read it. Try a re-break that puts the word at the end of a line, where it usually gets a longer note, before you consider swapping it.

You find yourself rewriting. Stop and look at the contract table. If the fix is in the right-hand column, decide consciously whether you are now writing a new song. That is allowed. It is just a different project from singing your poem.

Before you paste, do this

Copy the poem into a plain text file. Mark each stanza as verse, chorus candidate or ending. Read the chorus candidate out loud three times. Break every line over twelve syllables at its natural pause, and remove anything that is not a sung word or a bracketed tag. Then write one Styles line describing the sound, by hand or with the prompt generator, and run the song at least twice before you change a single word of the poem.