REAPER project to WAV

Drop an .rpp to bounce it to WAV, or select a file — it opens in the studio, ready to export.

RPP · ZIP

How to get a WAV out of a REAPER project

An .rpp is not a recording. It is a description of one: tracks, items, tempo, and pointers to media that lives wherever REAPER was running. When you need a WAV — to open in another DAW, to hand to a mixer, to carry on from — something has to turn that description into sound first. That step is the whole job.

  1. Add your .rpp: The .rpp itself; zipped is fine, it is unzipped and read the same way. Either way what is read is the notes, and any audio travelling beside the project is not. If that audio is what you want in the bounce, it comes in by a different door — File → Import session, inside the studio.
  2. Read in your browser: Every item and its position, the tempo, the notes in each MIDI item, and the list of media the project expects to find are read where the file sits. None of it is uploaded, and no account is needed to get this far.
  3. Choose instruments, then bounce: Give each track one of thirty-six modelled players — that render needs a free account. Export audio, under File, then writes the result as WAV at 16-bit, 24-bit or 32-bit float, 44.1 or 48 kHz.

More ways to work with your music

Try our online tools to separate, transcribe and convert — Doseedo does it all.

Questions about the REAPER project to WAV converter?

We have answers.

Can I convert an .rpp straight to WAV?

No. Nothing can transcode a project file into audio, because the audio was never inside it — an .rpp names its plugins, samples and media rather than storing what they sound like, so what gets bounced here is a performance of the notes it does hold. Your own mix has to come from REAPER, on the machine that still has the media.

Do I need an account?

Yes, a free one — but only for the half that makes sound. Reading the project happens in your browser, signed out and with nothing uploaded; both routes that end in audio, the modelled render and Import session, need the account.

What if a clip's audio will not load?

On the master mix it is skipped and the track it was on is named at the end — everything that did decode is in the file, which is the difference between a bounce with a hole in it and no bounce at all. Stems do not work that way: one file per track means a clip that will not decode stops the export outright, and you get the reason in place of the zip. If the folder might be short a file, bounce the master first and read what it says it skipped.

Can I get every track as its own file?

Yes. The master mix, the selected track, or a zip with one WAV per track — though the zip follows what you can actually hear, so a track a solo is keeping quiet is not in it.

Try our free REAPER project to WAV converter

  • Bring the folder, not only the project

    Not every .rpp arrives alone. When the audio travels with it — a zipped project folder, a shared drive, a hand-off from whoever recorded the parts — the studio's Import session takes the folder instead of the file: it goes up to the import service to be read, and what comes back is an editable session in which every clip plays from the local copy your browser is already holding, at the position REAPER gave it. Files the project asks for that were not in what you handed over are counted rather than passed over in silence, so a half-collected folder says so out loud. That route needs a free account, and it renders no instruments and no plugins — only the audio the project actually carries. The same bounce then writes it as WAV.

  • When the project has notes and no audio

    A project that arrived on its own still carries its MIDI items, and that is a different job from replaying a recording: there is no recording, so one gets made. Modelled players perform those parts on a GPU, which is the step that needs a free account. Nothing in the result reconstructs how the project sounded on the machine that made it: it performs the notes the file holds, and the plugins it names have no part in that. What you get back is audio that has never existed before, with room underneath for a mix or an overdub. No original exists anywhere for it to be faithful to, which retires the usual fidelity question and leaves the answerable one — the render is kept compressed, and the export reads that copy. A first writing is what a source is.

  • What lossless costs, and the cheaper lossless

    A WAV's size is arithmetic rather than a setting: sample rate, times bytes per sample, times channels. At 48 kHz, three bytes for 24-bit, two channels, that is 288 kilobytes every second — about 17 MB a minute, near 70 MB for four minutes, and the same again per track if you take the stems. Nothing about the music moves that number; a silent track costs exactly what a loud one does. There is a third format in the same menu for when it hurts: FLAC, lossless as well, which packs the identical samples smaller and fixes its own depth at 24 rather than taking the one you picked. The export opens on 16-bit WAV, so 24-bit is a deliberate move either way.

Try these Doseedo tools