Models - Jul 30, 2026

Lyria 3.5 Google Flow Music Access Guide

Quick Answer

Google launched Lyria 3.5 in Google Flow Music on July 29, 2026.

To check access:

  1. open the current Google Flow Music product;
  2. sign in when prompted;
  3. confirm the product is available for the account and country;
  4. inspect the current daily-credit or plan treatment;
  5. verify Lyria 3.5 or the current music-generation feature is visible;
  6. test a low-risk track before committing a project;
  7. review export, publishing, sharing, input-rights, and commercial terms.

The public homepage said “Free to start,” “No credit card required,” and “Daily credits” when checked July 30, 2026. Treat these as dated product-surface observations, not a promise of unlimited generations or permanent pricing.

Use the Lyria 3.5 model guide for the source-backed entity record.

Important boundary: Google Flow Music, Google’s video-focused Flow product, and Flowith are different surfaces. The Lyria launch does not establish a public API or Flowith availability.

What Google Verified

Google’s launch names six areas:

  • richer musicality;
  • more complex and natural melodic structures;
  • better lyrics;
  • improved prompt adherence and structural awareness;
  • more expressive vocals and pronunciation;
  • easier tempo and duration control.

Google says Lyria 3.5 is rolling out in Flow Music. The product homepage also presents:

  • chat with a Producer;
  • full-length song creation;
  • music-video creation;
  • audio effects;
  • stem splitting;
  • playlists, publishing, sharing, and discovery;
  • daily credits.

These product features can change independently of the model. Verify the current signed-in interface rather than assuming every homepage feature uses Lyria 3.5 in every step.

Access Checklist

Account and Eligibility

Check:

  • signed-in Google account;
  • supported country;
  • age eligibility;
  • organization or managed-account restrictions;
  • waitlist or rollout status;
  • current terms acceptance.

A public landing page is not proof that every account can enter the creation workspace.

Credits and Cost

The checked-date homepage says daily credits and free to start.

Before a project, record:

  • initial credits;
  • daily reset behavior;
  • credits per generation or edit;
  • retry and failed-generation treatment;
  • paid upgrade path if one exists;
  • export or publish costs;
  • current currency, tax, and refund rules.

Do not convert “free to start” into “free Lyria 3.5” or “unlimited music generation.”

Model and Feature Label

Google’s launch says Lyria 3.5 is rolling out in Flow Music, but product UIs can expose capabilities without displaying a model ID.

Record:

  • visible model or feature label;
  • product version or experiment status;
  • date;
  • account;
  • output controls;
  • any fallback or unavailable message.

If the UI does not show a model identity, describe the feature as Flow Music rather than asserting every output came from a specific checkpoint.

A Practical First Session

1. Define the Brief

Write:

  • intended genre and subgenre;
  • mood and emotional arc;
  • instrumentation;
  • tempo target;
  • duration target;
  • vocal type;
  • lyrical topic;
  • section structure;
  • prohibited references or content.

Avoid asking for a living artist’s identity or a real person’s voice. Describe musical attributes that you have the right to request.

2. Generate a Small Set

Create a bounded set of candidates instead of spending all daily credits at once.

Keep the brief stable so you can compare:

  • melody;
  • harmony;
  • form;
  • groove;
  • vocal realism;
  • pronunciation;
  • lyrical adherence;
  • artifacts;
  • ending quality.

3. Test Creative Controls

Change one variable at a time:

  • tempo;
  • duration;
  • vocal emotion;
  • section order;
  • lyrical density;
  • instrumentation.

Measure the result. A prompt asking for 120 BPM or three minutes does not prove the exported track meets those values.

4. Refine and Review

Use the product’s current editing, effects, or stem tools where available.

Review:

  • clipped or distorted audio;
  • unwanted similarities;
  • voice or likeness risk;
  • mispronounced names;
  • factual or harmful lyrics;
  • copyrighted text;
  • unwanted samples;
  • metadata and credits.

5. Export, Publish, or Share

The homepage presents publishing and sharing features, but those buttons are not a blanket rights clearance.

Before distribution:

  • read current Flow Music terms;
  • confirm the rights to prompts, lyrics, uploads, samples, and reference material;
  • review voice and likeness consent;
  • check commercial-use and monetization conditions;
  • review the destination platform’s AI-music rules;
  • retain project records and human approval.

Model Controls to Evaluate

Musicality

Google says Lyria 3.5 produces richer and more complex melodic structures.

Listen for:

  • coherent motifs;
  • transitions that serve the form;
  • balanced repetition and variation;
  • harmonic consistency;
  • natural phrase lengths;
  • purposeful endings.

Lyrics

Google names improved prompt adherence and structural awareness.

Check:

  • requested theme;
  • verse, chorus, and bridge structure;
  • point of view;
  • rhyme and meter;
  • repetition;
  • factual or sensitive claims;
  • prohibited words;
  • language consistency.

Generated lyrics still require editorial and rights review.

Vocals and Pronunciation

Google names greater realism, emotional nuance, and pronunciation.

Test:

  • the target language;
  • code-switching;
  • names and uncommon terms;
  • consonant clarity;
  • long sustained notes;
  • emotional direction;
  • artifacts at section boundaries.

Do not present generated vocals as a real performer or imply endorsement.

Tempo and Duration

Google says these controls are easier.

After generation, measure:

  • actual BPM;
  • total duration;
  • intro and outro length;
  • section durations;
  • tempo drift;
  • abrupt cuts or padding.

Use audio tooling for exact delivery requirements.

API Access Is Not Established

Google’s July 29 post launches Lyria 3.5 in Flow Music. It does not publish:

  • a general API endpoint;
  • a developer model ID;
  • API request schema;
  • API pricing;
  • quotas;
  • regions;
  • service-level terms;
  • a deprecation policy.

Do not use lyria-3.5 as an invented API identifier. Check current Google AI and Cloud developer documentation if programmatic access becomes a requirement.

Flow Music, Google Flow, and Flowith

Google Flow Music

The verified product surface for the launch. It focuses on music creation, production, publishing, sharing, and discovery.

Google Flow

A separate Google creative product commonly associated with visual and filmmaking workflows. Do not transfer its plans, credits, model catalog, or rights terms to Flow Music.

Flowith

A separate product from a separate company. Google’s Lyria rollout does not prove a Flowith model mapping, price, plan, credit cost, context, output limit, or data policy.

Check the live Flowith workspace independently.

Troubleshooting

Lyria 3.5 Is Not Visible

Check:

  • signed-in account;
  • supported country;
  • age;
  • rollout status;
  • product URL;
  • managed-account restrictions;
  • available credits;
  • browser and product status.

Credits Are Exhausted

Record the reset message and current upgrade options. Avoid creating another account to bypass product limits.

Tempo or Duration Is Wrong

Use a simpler brief, change one control at a time, generate a small candidate set, and measure the output. Use an audio editor if exact delivery is required and the terms permit editing.

Vocals Sound Like a Real Person

Do not publish until voice, likeness, impersonation, disclosure, and destination-platform risks are reviewed. Regenerate with non-identifying vocal attributes.

Frequently Asked Questions

Do I need a credit card?

The public homepage said no credit card required when checked July 30, 2026. Confirm the signed-in product and current region because entry terms can change.

Does Flow Music give unlimited daily songs?

No such claim is established. The homepage mentions daily credits; verify how many credits are granted and how actions consume them.

Can I upload an existing song?

The public product presents remixing and music workflows, but upload types, rights, size, storage, and reuse rules must be checked in the current interface and terms.

Can I distribute a Lyria 3.5 track?

Do not rely on the launch post alone. Review current product terms, rights to all inputs, voice and likeness, samples, disclosures, and the distributor’s policies.

Official Sources