How to get the MIDI out of a Bitwig project
Bitwig's own .bwproject is a closed format that nothing outside Bitwig reads, and Bitwig hands MIDI out a clip at a time. What Bitwig does have is File → Export → DAWproject: an open, documented file that carries the whole arrangement. Drop that here and the arrangement comes out as one Standard MIDI file — and so does a .dawproject from Studio One or Cubase.
- Export a .dawproject: In Bitwig Studio 5, File → Export → DAWproject. Studio One 6.5+ and Cubase 14+ have the same export. Drop the .dawproject it saves — not the .bwproject, which cannot be read.
- It is read in your browser: A .dawproject is a zip holding one XML document. The tracks, the clips, their loops and every note are read on your machine; nothing is uploaded and no account is needed.
- Take the MIDI: The arrangement opens in the studio and downloads as one Standard MIDI file — a named track per track, at the project tempo.
More ways to work with your music
Try our online tools to separate, transcribe and convert — Doseedo does it all.
Questions about the Bitwig project to MIDI converter?
We have answers.
Do I need an account?
No. A .dawproject is read in your browser, so the conversion works signed out and the project is not uploaded.
Can I drop the .bwproject?
No — Bitwig's own project file is undocumented, and nothing outside Bitwig reads it. Export the project as DAWproject (File → Export → DAWproject) and drop that; it carries everything this needs.
Does a Studio One or Cubase DAWproject work?
Yes. DAWproject is one format whoever wrote it; a .dawproject from Studio One 6.5+ or Cubase 14+ reads the same way.
Do my track names survive?
Yes. Each track with notes becomes a named track in the MIDI file; tracks inside a group keep their own names.
Try our free Bitwig project to MIDI converter
A clip is a window on its notes, and loops are played out
In DAWproject a clip holds its notes in its own time, starts playing them from an offset, and may loop a range of them until the clip ends. Reading the notes alone gives you one pass of each loop stacked at the clip start; what you hear is the loop repeated across the clip's length. That is what gets written here: every pass of every loop, at the position Bitwig plays it, and a note that falls past the end of its clip is left out.
Nested clips, aliases and odd units
The format lets a clip contain clips, lets a clip point at another clip's notes rather than carry its own, and lets any lane count in seconds instead of beats. Bitwig nests every looped clip; Studio One wraps notes in an extra lane. All of it is unwrapped here, and lanes in seconds are placed through the tempo map — holds and ramps — so a clip after a tempo change lands where the DAW plays it.
What is not in a DAWproject
Audio clips are recordings and hold no notes. Bitwig's instruments and modulators, CLAP and VST plugins, The Grid — all of that is named in the file, with its state, and none of it is MIDI. A MIDI file is the performance; the sound stays in Bitwig.
Use Doseedo tools for free
- Free runs every day on every tool — nothing to install
- A free account gets 120 credits a month (a DAW conversion is 1 credit), up from three conversions with no account
- Save your sessions and come back to them
Try these Doseedo tools
- Convert audio
- Convert MIDI
- Projects to MIDI
- Projects to audio
- FL Studio project to MP3
- FL Studio project to WAV
- Ableton Live project to MP3
- Ableton Live project to WAV
- Logic Pro project to MP3
- Logic Pro project to WAV
- REAPER project to MP3
- REAPER project to WAV
- Pro Tools session to MP3
- Pro Tools session to WAV
- Cubase project to MP3
- Cubase project to WAV
- GarageBand project to MP3
- GarageBand project to WAV
- Studio One project to MP3
- Studio One project to WAV
- Bitwig project to MP3
- Bitwig project to WAV
- From Logic
- From Ableton
- From FL Studio
- From REAPER
- From Pro Tools
- Session files
- Guides