Google Flow Music is what Riffusion became: Producer.ai first, then Google's after it bought the company in February 2026. Since July it runs on Lyria 3.5, which Google says follows lyrics and song structure better than Lyria 3 did. You can chat with it, but its prompt box will also take one complete prompt for a whole song, and Google has published more about how to write that prompt than most music companies publish about anything.
This guide pulls Google's advice together (the Gemini API's Lyria prompt guide and music-generation page, Google Cloud's Lyria 3 Pro prompting guide and the Flow Music help pages) and shows a full-song prompt built that way.
One prompt, in Google's order
Flow Music has no separate lyrics or style fields when you start a song: you describe it in one prompt box, and add audio or images if you like. Google's framework for that prompt runs:
Genre and style → mood → instruments → tempo and rhythm → vocal style and language → lyrics.
- Genre first, with an era or regional twist if you want one: "early-2010s bedroom pop", not just "pop".
- Name the instruments you care about. Otherwise Lyria picks the genre's defaults.
- Tempo and key as words: "112 BPM", "around 72 BPM", "in G major", "in D minor".
- The voice: gender, range and timbre ("warm female alto, close-miked"). Google's guides cover duets and backing singers in the prompt's description, not with tags.
- Length in the prompt: Lyria 3.5 takes a request like "a 2-minute song". There's no length setting to set.
- Instrumental: say so. Google's own wording is "Instrumental only, no vocals."
Both short and long prompts work, Google says. A detailed one gives you more control.
The structure outline
Lyria 3.5 accepts the song's shape as an arrow outline:
Structure: [Intro] -> [Verse 1] -> [Chorus] -> [Bridge] -> [Chorus] -> [Outro]
List every part in order, the instrumental ones too: the intro, a drop, a break. Google also describes timing in plain words ("at 22 seconds", "every 4 bars"), and its pages show timestamped lines, though in two different formats. The arrow outline is the one Google documents specifically for Lyria 3.5, so it's the one to use.
The Lyrics block
Put your lyrics under a Lyrics: heading, after the musical direction, so the model can tell words to sing from instructions:
- Tag sections with
[Verse],[Verse 1],[Pre-chorus],[Chorus],[Bridge],[Intro],[Outro]. - Put backing vocals, echoes and ad-libs in parentheses:
I'm halfway home (halfway home). - Write the prompt in the language you want sung. Lyria sings in the prompt's language, and covers English, German, Spanish, French, Hindi, Japanese, Korean and Portuguese.
Without a Lyrics block, Lyria 3.5 writes its own words from your description.
A full-song prompt
Put together, the prompt for a three-minute indie-pop song looks like this:
Indie pop, 112 BPM, bright and hopeful. Early-2010s bedroom-pop warmth.
Warm female lead, close-miked and conversational. Brushed live kit, round
electric bass, chiming clean guitars and a glockenspiel line. Verse 1 close,
conversational; Chorus full band, belted; Bridge half-time, whispered.
Vocal up front, guitars wide. Ends on a held chord ringing out.
In G major. Make it about 3 minutes long.
Structure: [Verse 1] -> [Chorus] -> [Bridge] -> [Chorus] -> [Outro]
Lyrics:
[Verse 1]
You left the porch light on for me
I counted every car that passed
[Chorus]
Leave the light on, leave the light on
I'm halfway home (halfway home)
[Bridge]
If the road goes dark
I'll follow the glow
[Chorus]
Leave the light on, leave the light on
I'm finally home
Paste it into a new session in Flow Music. If a part comes out wrong, Flow Music's chat and its Compose view let you change the lyrics, the sound or one section, and Replace, Extend and Cover work on a selected stretch of the song.
What Lyria won't take
- Exclusions. Google documents no negative prompting for Lyria 3 or 3.5, and its Vertex documentation says outright that Lyria 3 Pro doesn't support it. The only exclusion Google documents is "instrumental". Leave a list of unwanted sounds out rather than writing "no …" sentences into the prompt.
- Artist names and copyrighted lyrics. Google's safety filters block prompts that ask for a specific artist's voice or existing lyrics. Describe the sound instead.
- A full song in the Gemini app. Lyria 3 in Gemini makes 30-second clips. For a whole song, use Flow Music or the Gemini API's
lyria-3.5model.
Bringing a Suno prompt to Flow Music
A Suno prompt holds everything Lyria needs (genre and tempo, the voice, the band, the section plan, the ending), so it converts well. It just needs rearranging:
- Styles becomes the opening description, as it is. Add the key and the length if Styles doesn't say them.
- Cued headers lose their cue.
[Chorus | full band, belted]becomes[Chorus]. Google's guides never mention Suno's pipe cue, and the words after it could be sung. The delivery stays in the description, if your Styles already says how each section goes. - Inline cues and voice tags come out.
[beat stops]and[Male vocal]have no meaning to Lyria. Describe a duet or an answering voice in the description. - Sections with nothing sung (an intro, a drop) go in the Structure outline only.
- Exclude stays behind, for the reason above.
[End | …]becomes[Outro].
The free Suno prompt converter builds the whole Flow Music prompt from your Suno Styles, Exclude and lyrics, and lists what it changed. The example above is its output.
What we haven't tested yet
We haven't run a blind listening test of converted prompts on Flow Music against the same prompts on Suno, so we can't tell you yet how closely Lyria 3.5 follows a section's delivery. The format follows Google's own guides; judge the takes by ear.
For how the two products compare on price, rights and editing, see Suno vs Google Flow Music. The free lyric checker works on any lyric sheet before you paste it anywhere.