monody
Menu
Download

DAWproject, MIDI files and stems: which one to hand off

What a DAWproject file carries that MIDI and stems don't, which DAWs document it, where plug-in state and automation get lost, and a checklist for a handoff.

The short answer. Use a DAWproject file when both DAWs document it and you want tracks, clips, notes and some mixer state to arrive as a project. Use MIDI files for notes, and stems for sound, when either side doesn't, or when you can't be sure the plug-ins match. Whatever you send, include a short note with the tempo, sample rate and plug-in list, and open the result next to the original to check it.

Moving a project between DAWs can mean stems and a lot of rebuilding. DAWproject offers another route, but support is uneven and the details matter. This guide explains the choices and how to check a transfer. The format and Cubase DAWproject documents were reviewed on 9 October 2026; the other source checks remain dated below. We did not test a DAWproject file between DAWs.

What each option carries

Stems (WAV) MIDI file (.mid) DAWproject Native import
Notes and velocities No Yes Yes, with note expression Depends on the importer
Sound as rendered Yes No Audio embedded or referenced; instrument state is not rendered sound Depends
Tempo and time signature Only if written in Yes Yes, with automation Depends on the importer
Track structure and groups No Track names only Yes Depends on the importer
Automation Baked in Controller data Volume, pan, mute, sends, plug-in parameters Varies by DAW
Plug-in state Baked in No Embedded, for plug-ins both sides have Varies
Needs the receiving DAW to Read the audio format Read Standard MIDI Files Support DAWproject Have an importer for that project

The DAWproject column describes the format's capacity, not a guarantee from every exporter and importer. Its specification and comparison table also cover clip launcher data and generic EQ, compressor, gate and limiter devices. "Native import" means one DAW opening another's project file directly, such as Bitwig's import of Ableton Live and FL Studio projects.

Who documents DAWproject

  • The format. The DAWproject repository calls version 1.0 stable and lists support in Bitwig Studio 5.0.9, Studio One 6.5, Cubase 14, Cubasis 3.7.1, VST Live 2.2 and n-Track Studio 10.2.2. It also points to converters for other formats, including one for REAPER.
  • Bitwig. Export is File, Export DAWproject. Bitwig's user guide says this saves "all of your generic project data into a file, which can be opened by any other music software that supports the format". Bitwig's FAQ lists its supporters as of 6 November 2024, so treat it as dated, not as a 2026 list.
  • Cubase Pro 15. Steinberg's DAWproject support page lists audio, instrument, group, effect, marker and folder tracks, routing and specified automation. Insert plug-ins are limited to VST3. Its export instructions use File → Export → DAWproject, then a filename and destination. These are documented capabilities, not our transfer test.
  • Waveform. The current manual documents File, Export Other, Export as DAWproject file and File, Import Other, Import a DAWproject file, with a list of what does and doesn't travel.
  • Fender Studio Pro. Bitwig's FAQ lists Studio One 6.5, with File, Convert To, DAWproject File as the export path. Studio One is now Fender Studio Pro. We haven't confirmed the current version's menu, so read its Reference Manual.
  • Logic Pro, FL Studio, Ableton Live. None is named in the repository's list or in Bitwig's FAQ. We have no source saying they support or don't support it today, so check each manual.
  • Bitwig's other routes. Its MIDI and audio export and its controller extensions are in Bitwig and AI.
  • monody. No DAWproject support. AI basslines you can edit shows the .mid route instead.

Direct import is not DAWproject

Bitwig describes importing Ableton Live and FL Studio projects directly. From Live it keeps audio, MIDI and group tracks with routings, and VST plug-ins with settings and automation, and converts stock Ableton devices to Bitwig equivalents. From FL Studio it brings patterns and audio events in as clips, but native FL devices aren't transferred and automation is lost, which Bitwig calls "a handy time-saver when transferring simpler material". Those are one-way import features of one DAW, not a shared format.

What gets lost

The makers say it plainly:

  • Media can live outside the container. The format permits external audio references. Our handoff recommendation is to check that the copied package opens on the receiving machine without access to the original media folder.
  • Plug-ins must exist on both sides. Waveform warns that a plug-in only loads if that exact plug-in is installed on the receiving machine, and is silently dropped otherwise. Bitwig's FAQ noted that Studio One AU data isn't read by Bitwig and Bitwig's CLAP data isn't read by Studio One, for the versions it listed.
  • Automation and routing vary. Waveform's list of what doesn't come across includes automation curves, sends and bus routing, step and Edit clips, pitch and time-stretch settings, and groove and quantize settings. Another DAW may differ, so read each side.
  • Built-in devices are generic. The format covers a generic EQ, compressor, gate and limiter. Everything else is the plug-in's own state or nothing.
  • Clip launcher data may not map. Bitwig's FAQ noted that Studio One didn't read Bitwig's clips and scenes.
  • A missing instrument plays nothing. Waveform says a plug-in that isn't installed on the receiving machine is dropped from the track, so check that the notes still have an instrument.

A handoff checklist

  1. Say what the other person needs. Edit the arrangement, remix, mix, or just hear it. That decides the format.
  2. Check both manuals for DAWproject at your versions, or for a direct import.
  3. Save a copy and export from the copy. Some exports, such as FL Studio's project-wide MIDI macro, change the project.
  4. Package the media and a reference. Include any externally referenced audio, a full-mix reference, common-start stems and MIDI for the key parts as needed. Move MIDI and stems between DAWs has the fallback steps for FL Studio and Logic Pro.
  5. Write the note. Tempo, time signature, sample rate, key, and a list of every plug-in with its format (VST3, AU, CLAP) and version.
  6. Import as a new project for the first check. In Cubase Pro 15, File → Import → DAWproject offers a destination choice if a project is open: Yes creates a new project; No imports into the active one.
  7. Check the transfer. Compare track count, tempo, note counts and plug-in presence. Then bounce both versions and listen to them against each other at the same loudness.

When it goes wrong

What you see Likely cause Try
Media missing on the receiving machine Audio may be referenced outside the container Include the referenced files using the exporter's documented packaging options, then check the transferred copy
Instrument tracks silent The receiving side may lack a compatible plug-in Check plug-in format and version, or use a rendered stem
Everything lands 1 bar or 1 beat off Different start or tempo Set the tempo first, import at bar 1
Automation missing The importer or exporter doesn't carry it Bake it into stems or redraw it
Notes right, sound wrong MIDI carries no sound Use the stem as a reference

Sources

DAWproject repository and Cubase Pro DAWproject help read directly on 9 October 2026. Other Bitwig, Waveform and monody claims retain their 4 October review. The current Fender Studio Pro menu remains unconfirmed here. No application-to-application transfer or listening test was performed.

Questions

What is DAWproject?
An open format for transferring session data between DAWs. Its ZIP container holds XML and plug-in state; audio can be embedded or referenced outside the file. What arrives depends on both applications, so check media and playback after importing.
Which DAWs support DAWproject?
The format's repository lists Bitwig Studio 5.0.9, PreSonus Studio One 6.5, Steinberg Cubase 14, Cubasis 3.7.1, VST Live 2.2 and n-Track Studio 10.2.2. Steinberg also documents Cubase Pro 15 import and export. Waveform's manual documents both. A support list does not promise that every feature transfers.
Does DAWproject work with Logic Pro, FL Studio or Ableton Live?
We found none of them named in the format's own support list or in Bitwig's. Check each maker's current manual. Bitwig imports Ableton Live and FL Studio projects directly, which is a different feature.
Does monody support DAWproject?
No. monody opens Ableton Live 12 sets and exports a Live project folder with stems. It exports a MIDI clip or track as a .mid, and the mix or stems as WAV, FLAC or AAC. It does not read or write DAWproject, .flp or .logicx files.
When should I send MIDI and stems instead of a DAWproject file?
When the receiving DAW doesn't document DAWproject, when you only need the notes or the sound, or when you can't be sure both sides have the same plug-ins. MIDI and WAV are the most widely supported formats, but the receiving DAW still has to read them.