New features ·

Tested on Suno v5.5 update

Suno Studio 2.0: MIDI, a Wavetable Synth, and the No-Limits Export Lane

Studio 2.0 turns Suno's browser DAW into something closer to real production software: MIDI on the timeline, a built-in synth, automation, a plugin-building chat bar, and unlimited exports for Premier.

On August 13, Suno shipped Studio 2.0, the second generation of its browser-based production suite and easily its most serious attempt at being a real DAW rather than a text box with a timeline attached. The first Studio, built on Suno’s WavTool acquisition and launched in September 2025, was reviewed politely and used skeptically; press coverage rated it middling, and most working creators treated it as a stopover on the way to their actual DAW. Version 2.0 goes straight at the gaps that caused that.

This is an announcement-tier writeup: what follows comes from Suno’s launch post and the coverage around it, not from us having rebuilt a workflow inside it yet. When we have, the practical guides will catch up. Studio 2.0 is Premier-only, which matters more than usual for reasons at the bottom.

MIDI arrives, and it works both directions

The headline feature is the most-requested one: MIDI on the timeline. You can import MIDI files, record from an external controller, or play parts in from your computer keyboard via a Musical Typing mode, then edit the results directly in Studio. A built-in wavetable synth gives the MIDI something to play: basses, leads, pads, and chords designed inside the browser, with MIDI Learn support for hardware control.

The genuinely new idea is the reverse direction: MIDI clips can be used as prompts for new audio generations. Write the melody yourself, then have Suno generate around it. For anyone whose complaint about generation has always been “I can’t give it my actual musical idea, only words about it,” this is the first official answer. How well the generation honors the MIDI is exactly the kind of claim we don’t repeat until it’s been tested, but as a direction, it’s the most interesting thing in the release: prompting is no longer only a writing exercise.

The chat bar that builds plugins

Studio 2.0 adds a beta chat assistant that can control the session: generating sounds, organizing the project, editing MIDI and audio on instruction. The audacious part is plugin design. Alongside factory devices that include sidechain compression and convolution reverb, the chat bar can build custom effects from a description. Suno says plugin creation costs no credits at launch, while noting a credit structure may come later, which is worth reading as: enjoy the free period, don’t architect a workflow that assumes it’s permanent.

Automation also arrives for the first time: curves for volume, panning, and plugin parameters drawn over time. Between MIDI and automation, the two loudest “this isn’t a real DAW” objections are now answered on paper.

Stems, and the export lane

Studio 2.0 folds in Suno’s newest stem separation, with standard and advanced options for pulling a finished recording apart into editable components inside the session. If you’ve been following the stems workflow, this is that machinery moved into the place where you’d actually use it.

And then the detail that connects this launch to the rest of Suno’s August: Premier subscribers can export 32-bit/48kHz multitracks and stems from Studio with no download limits. Read alongside the September 3 download caps, the shape is unmistakable. The metered door is the regular library download; the unlimited door is Studio, behind the top subscription. Industry coverage has read the same week of announcements the same way: casual mass export gets harder, while paying producers get a professional lane with the limits removed. Whatever you think of the strategy, the practical takeaway for anyone on Premier is simple: export-heavy work now belongs in Studio, full stop.

What this means for existing workflows

  • The DAW round trip narrows but doesn’t close. Our Suno-to-DAW guide exists because finishing has always meant leaving. MIDI, automation, and in-session stems move real finishing work into the browser; whether they move your finishing work depends on how attached you are to your plugins, your templates, and your latency. Browser DAWs still carry browser constraints.
  • Our beginner guide covers the old Studio. Studio for beginners describes the original interface and will be re-verified against 2.0; until then, expect its screenshots and step ordering to drift from what you see.
  • Pro subscribers are watching through glass. Studio remains Premier-only. With the caps arriving September 3, the tier question stopped being about credits and started being about doors: Pro gets 20 metered downloads, Premier gets Studio and the unmetered lane. That math is different for everyone, but it’s now the actual decision.

The sensible posture

Same as every launch: the features are real announcements, the behavior is unverified until tested, and the free parts are free until they aren’t. If you’re on Premier, spend an hour in it before restructuring anything; the MIDI-as-prompt feature is the one we’d test first, because if it works even reasonably well, it changes what “writing for Suno” means. That test, and this page, will get updated as the picture firms up. The bigger context, including where Studio fits in the run-up to the licensed models, lives in the next-model guide.

Sources