Bitwig project to MP3

Drop a .dawproject to get an MP3, or select a file — it opens in the studio, ready to export.

DAWPROJECT · ZIP

How to get an MP3 out of a Bitwig project

Bitwig exports audio as WAV, FLAC or OGG, and never as MP3; and a .bwproject opens nowhere but Bitwig, so a project somebody sent you is a closed door on a machine without it. What Bitwig does have is File → Export → DAWproject, an open file that carries the arrangement and the audio inside it. Drop that here: the recordings play as they are, the note clips play on stand-ins, and the MP3 is the two together.

  1. Export a .dawproject: In Bitwig Studio 5, File → Export → DAWproject; the file carries the tracks, the clips and the audio they play. Studio One 6.5+ and Cubase 14+ export the same file. Drop it here — the arrangement is read in your browser, and no account is needed to open it.
  2. It renders by itself: The studio opens on the arrangement and starts the MP3 straight away. Audio clips play from the file's own copy of the recordings; each note track's clips — loops played out — go to a stand-in picked from the track's name, rendered on our server from a General MIDI sound set.
  3. Download the MP3: One 256 kbps file of the whole arrangement lands in your downloads. Your first three a month need no account; a free account gives you 120.

Questions about the Bitwig project to MP3 converter?

We have answers.

Can I convert a Bitwig project to MP3 without Bitwig?

With a .dawproject, yes — drop it here. Audio clips play from the recordings inside the file; note clips play on stand-in instruments, not Bitwig's. A .bwproject cannot be read by anything outside Bitwig, so export it first.

Is it free? Do I need an account?

Your first three MP3s a month need no account, and opening the project needs none at all. A free account raises the renders to 120 a month.

Will it sound like my project?

Your recordings will; Bitwig's instruments and devices will not. Note clips are played on General MIDI stand-ins, and no CLAP or VST device is rendered. Signed in, Sources can play any part on a modelled instrument instead.

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+ renders the same way.

How long can the project be?

Up to 20 minutes and 40,000 notes for the stand-in render.

Try our free Bitwig project to MP3 converter

  • What a DAWproject carries, and what it cannot

    A .dawproject is a zip: one XML document with the tracks, the clips, the notes, the mixer and the automation, plus an audio folder holding the recordings the clips play. So the recordings come with the file and play at their positions, under their track names; nothing has to be hunted down. What the file cannot carry is sound Bitwig makes live — Polymer, Phase-4, The Grid, every CLAP and VST device — those are named in the file with their state, and no server here runs them. Note clips are played on stand-ins; audio clips that point at files outside the project (external media) have nothing to play, and the studio says how many.

  • Why it is not your Bitwig mix

    Everything that makes a Bitwig project sound finished is computed by Bitwig while it plays: the instruments, the modulators, the devices on every track, the automation. None of that is audio in the file. What you hear is your recordings at their positions and your writing on stand-ins: right for checking an arrangement or sharing a sketch from a machine that has no Bitwig. The record itself comes out of Bitwig's File → Export Audio, on the machine that has everything — and an MP3 of that still needs a second step, because Bitwig does not write one.

  • One bitrate, and what it costs

    256 kbps is the only bitrate on offer: no slider, nothing to get wrong. About 1.9 MB a minute, so a four-minute song lands near 8 MB — one attachment, playable by anything. An MP3 spends its bits on seconds rather than on detail, and what it discards is gone; send the MP3, keep a WAV if the audio will be worked on.