Google Flow Music now exports the tools you describe as VST3 and AU plugins

On 6 Oct 2026 Google announced that producers can export custom Spaces from Google Flow Music as VST3 or AU plugins and run them inside their DAW. Spaces is the part of Flow Music where you describe an instrument or effect in plain language and the system builds it, with no coding required. Until now those tools lived only in the browser.

The launch example comes from Khris Riddick-Tynes, one of the credited writers on SZA's "Snooze", which won Best R&B Song at the 2024 Grammys. Google says his plugin, No Chaser, keeps instrumentals and vocals sharp and studio-quality wherever they were recorded.

How does the export actually work?

The Google help page is more revealing than the announcement. You don't get a standalone plugin per idea. You install two Google plugins once, Flow Instrument and Flow Effect, which appear in your DAW under the manufacturer "Google Flow Music". Each tool you build in Spaces downloads as an .fmx file, and you drag that file onto Flow Instrument or Flow Effect to load it. If the "Use in DAW" option doesn't show up, Google suggests asking the producer to make the Space a VST plugin.

The current limits are stated plainly on the same page:

• macOS only. Ableton Live, Logic Pro and FL Studio are given as example hosts. AIMusicpreneur notes Google hasn't given a date for Windows.
• Synthesis and effects only. Instrument plugins can only use standard synthetic audio for now; sample-based instruments and anything that uses generative AI audio can't be exported yet.
• Staged access. The Plugins filter may be missing if plugins aren't available for your account yet.

On price, a Google Flow Music staffer told Zinstrel that export works on free accounts. Google's own pages don't say either way, beyond the Spaces page noting that Flow Music is free to start with a Google Account.

Where this comes from

Flow Music began as Riffusion, relaunched as ProducerAI in 2025 and joined Google Labs in February 2026, according to Music Business Worldwide. MBW also reports that Flow Music runs on Google DeepMind's Lyria models, that independent musicians sued Google in March 2026 alleging Lyria 3 was trained on YouTube recordings without permission or payment, and that Google says it trained on material it has a right to use. That dispute sits in the background of everything Flow Music ships, plugin export included.

What it means for artists

The interesting shift is from AI that makes songs to AI that makes instruments. Riddick-Tynes told Zinstrel the feature is for nerds, or people who want to be nerds but can't code, and that the appeal is speed: a new idea doesn't have to wait for a new version to come out. That's a producer describing a tool that serves his taste, not one that replaces it. The record is still made by a person in a DAW, with every creative decision traceable to them.

The demand for this is real and it comes from users, not just from Google's launch copy. On X, one hobbyist described building a web MIDI drone synth and guitar amp that started life in Flow Music, with a VST as the goal. Another creator asked Suno for exactly this: VSTi support, or Suno running as a plugin inside their DAW. The common thread is that producers want AI where they already work, not a separate app that asks them to move their sessions out.

Then there are the questions artists should ask before building a signature sound on this:

• Who owns the tool? Flow Music's terms link redirects to Google's general Terms of Service (effective 30 Jul 2026). Those say your content remains yours and that Google won't claim ownership of original content its services generate, but they also give Google a worldwide, royalty-free licence to use your content to operate and improve its services, and to use publicly shared content to promote them. We found no terms written specifically for exported plugins or .fmx files, so whether you can sell or redistribute a plugin you described is not verified.
• Does it keep working? Your .fmx file runs inside Google's Flow Instrument and Flow Effect. The help page doesn't say whether those need an account or a connection to load a saved tool, or what happens to old sessions if Google changes or retires them.
• Is it AI audio at all? Not yet. What exports today is synthesis and effects processing, which is closer to a very fast plugin designer than to generative music in your DAW.

What we think

The launch is framed as "vibe coding" your own plugins. The more accurate description is that Google has built one host plugin that can run many patches, and Spaces is how you write the patches. That's a clever design: one install, unlimited tools, and no code-signing or plugin-validation headache per idea. It also means every tool a producer builds this way depends on Google software keeping working in their DAW. A session that opens fine today relies on Flow Effect still loading in five years. Producers who've lost projects to a discontinued plugin will recognise the risk.

Second-order effects: small developers selling simple utility effects (a channel strip, a drum enhancer, the kind of chain No Chaser describes) face a free competitor that's built to order. The developers making deep, sample-based or carefully modelled instruments are safe for now, because those can't be exported. Producers gain the most, provided they treat these tools as sketches they can rebuild elsewhere, keep printing audio, and don't let a session's identity hang on an .fmx file.

The bigger point is direction. AI that works inside the producer's own workflow, building tools and parts under their control, respects authorship in a way that whole-song generators don't. That's the direction we'd like the field to take. Browser DAWs are heading the same way: Veena puts an AI co-producer inside the session to generate audio and MIDI, and runs VST and AU plugins through Veena Bridge, so the AI's output lands where the producer is already working. The test for all of these tools is the same one we'd apply to Google: does the artist keep the session, the stems and the say?

What Google should publish next is simple: plain terms for exported plugins, a commitment on how long Flow Instrument and Flow Effect will keep loading old files, and a Windows date. Until then, it's a promising instrument-building toy with an unclear lease.