Key takeaways
- Google has added a way to revise one song section instead of remaking the full track.
- Creators can keep parts they like while changing a weak intro, verse, or ending.
- The feature sits in Google’s experimental Music AI Sandbox for artists.
- It could make AI music tools feel less like a one-shot guessing game.
Google’s Lyria 3.5 editing update lets creators change one part of an AI-made song. Lyria 3.5 editing is a way to revise a selected music section without starting the whole track again. That means a good chorus can stay put while an unwanted opening gets replaced. It gives users more control over generated music.
How does Lyria 3.5 editing work?
Making music with AI often works like asking for a picture. You type a prompt, then the system creates an answer. But a song has many connected parts, so changing one bad moment could mean losing every good moment too. Google’s new approach aims to solve that frustrating problem.
With Lyria 3.5 editing, a creator picks the part that needs work and asks for a change. They might want a softer drum beat, a different mood, or a new ending. The tool then reworks that selection while leaving the rest intact. Google is offering the feature through its Music AI Sandbox, a testing space for music-making tools.
Think of a 90-second track with four parts: an intro, verse, chorus, and outro. If only the 15-second intro feels wrong, the creator can focus on that piece. They do not need to roll the dice on the other 75 seconds. That is a small change in workflow, but it can save a lot of time.
Edit 1 section, keep 3 sectionsIntroVerseChorusOutroSelected section: revise this part
Why does Lyria 3.5 editing matter for creators?
AI music can produce a fast first draft, but first drafts are rarely perfect. A singer may need a calmer backing track. A video maker may need an ending that lands at exactly the right moment. Lyria 3.5 editing gives them a more practical way to make those fixes.
The change also moves AI music closer to normal creative work. Musicians usually build songs in layers and revise them bit by bit. They do not throw away a full recording because one drum fill misses the mark. Google’s tool tries to bring that same basic choice to prompt-made audio.
There are still limits. A revised section must sound natural beside the parts around it. If the beat, key, or sound changes too sharply, listeners may spot the join straight away. Google has not said that every edit will match perfectly, so creators should listen closely before using a track.
What can users change without remaking a song?
Google’s update is built around changing a chosen section, rather than recreating a complete result. That can help with an intro that takes too long, a verse with the wrong energy, or an outro that ends too suddenly. A prompt is a written instruction for the AI. Clear prompts should give the model a better chance of making the requested change.
| Song problem | Older workflow | New workflow |
|---|---|---|
| Weak 15-second intro | Generate the full track again | Edit the intro section |
| Chorus has the wrong mood | Risk losing the best verse | Keep the verse and revise the chorus |
| Ending is too abrupt | Try a new full prompt | Rework the outro only |
The table shows the core promise of Lyria 3.5 editing: fewer wasted attempts. One targeted request can replace a full restart. For a person making music for a short film, game, or school project, that may matter more than adding yet another sound option.
How does this fit Google’s larger AI music plan?
Google has been building Lyria as a family of AI music models through Google DeepMind. A model is software trained to spot patterns and create new material from them. You can read Google DeepMind’s own overview of Lyria for its broader work on music generation and artist tools.
This update also arrives as music companies debate how AI systems should treat songs and artists. Many creators want useful tools, but they also want credit, choice, and fair payment. Google has said its music work involves partnerships with artists, yet the wider arguments over training data and rights are far from settled.
For now, Lyria 3.5 editing is most useful as a faster revision tool. It does not turn a rough idea into a finished hit by itself. A human still decides what sounds good, what fits the story, and what should be cut. That human judgment remains the part no button can fully replace.
What should creators watch before using it?
Check the rights rules for any platform where you plan to post the music. Also save different versions of your work, because an edit you dislike may be hard to recreate later. If a project involves a client, explain clearly where AI helped make the audio.
Creators should also avoid copying a living artist’s voice or a famous song’s sound too closely. A tool may create audio quickly, but that does not erase legal or ethical questions. The safest use is to develop an original idea and then shape it with careful edits.
FAQs
What is Lyria 3.5 editing?
Lyria 3.5 editing lets a user revise one selected part of an AI-generated track. The rest of the song can remain unchanged.
How is this different from making a new song?
A new generation can change every part of a track. This feature targets one section, so good parts are less likely to disappear.
Who can use Google’s music tool?
Google is providing it in the experimental Music AI Sandbox. Access and available features can vary as Google tests the service.



