Convert many Audacity projects at once
Drop a folder of projects, or select several at once: each one is opened, mixed and encoded on this machine, one after another, and you get one ZIP — with a report of what happened to every project.
Several projects? Drop or choose them together: export them all to one ZIP at once (Pro), or open them one by one free.
How can I convert a lot of Audacity projects to MP3 at once?
Drop them on this page together — a folder, or several .aup3 and .aup4 files selected at once — pick MP3 or WAV, and choose Export all. Each project is opened, mixed and encoded in your browser one after another, with nothing uploaded, and the files arrive as one ZIP with a report naming every project and what was exported from it. A damaged project is skipped and named rather than stopping the batch.
Drop the folder that holds the projects, or select several .aup3 and .aup4 files at once.
Pick MP3 (and its bitrate) or WAV; optionally split each project at its labels and add each one's labels as text.
Export all as one ZIP, with batch report.txt listing what became of each project.
Exporting the whole batch is Pro. Any project in the list can still be opened on its own, free.
Convert many Audacity projects at once
A term of class recordings, a season of a podcast, a box of digitised tapes: the audio is in dozens of Audacity projects, and getting it out in Audacity means opening and exporting each one in turn. Here the whole set goes in at once. Projects are read and exported one at a time, so a batch never needs more memory than its largest project, and a project's -wal dropped beside it is applied first, as Audacity would on opening it.
On a Mac? Audacity's own recovery utility only gained a macOS build in January 2026, and it is still a terminal program that asks for about four times the project's size in free space. Everything on this page runs in the browser instead, on any operating system.
What happens to each project in a batch
The projects are handled in the order listed, by the same worker that opens a single project: the file is read — whole when it fits in memory, otherwise a page at a time — its -wal applied when one came with it, and the document decoded. A project that does not decode is set aside and named in the report; the rest are mixed and encoded a window at a time into the chosen format, then closed before the next one is opened.
With splitting on, a project that has labels is cut at its first label track that holds any, with Audacity's rules, into a folder named after the project; files keep their label numbers and titles. Plain mixes sit at the top of the ZIP under the project's own name, with (2) added when two projects share a name. The report lists each project with the number of files it gave, any unreadable blocks, and any realtime effects that were left out.
Nothing is uploaded at any step: the ZIP is assembled in the page from the exported files and saved straight from the browser.
- Input
- Several .aup3/.aup4 files, or a folder holding them
- Order
- One project at a time, in list order
- Formats
- MP3 128–320 kbps · WAV 16-bit · WAV 32-bit float
- Options
- Split each at its labels · labels as text
- Output
- One ZIP plus batch report.txt
- Damaged projects
- Skipped and named; open alone on the recovery page
- Free
- Each project opened alone, mix up to 256 MB
New to the format? What an .aup4 file is, table by table — and how it differs from .aup3.
Converting this file
Q. Is converting a batch free?
Exporting the whole batch in one go is part of Pro. Every project in the list can still be opened on its own with its Open button, played, and exported as a stereo mix for free when it is up to 256 MB — the same as dropping it alone.
Q. What if one of the projects is damaged?
It is skipped, the batch carries on, and batch report.txt says why. A project whose document cannot be decoded is left for the recovery page, where it can be opened on its own for a full report and, with Pro, rebuilt. A project with unreadable audio blocks is exported with those parts silent, and the report counts them.
Q. Can each project be split at its labels?
Yes: tick Split each project at its labels and every project with a label track becomes a folder of one file per label, cut the way Audacity's Export Multiple cuts. A project without labels is exported as one mix. Add each project's labels as a text file to also get Audacity's own label file for every project that has labels.
Q. How large can a batch be?
There is no fixed limit. Only one project is open at a time, and a project too large to hold in memory is read from the file a piece at a time, as on every other page. The finished files are held by the browser until the ZIP is saved, so a batch of long WAV exports needs that much free disk space; MP3 batches are a fraction of the size.
Q. Does a batch keep each project's -wal?
Yes, when it comes along: drop the folder, or select each project's <name>.aup4-wal or .aup3-wal with it, and that project's committed edits are applied before it is exported — the edits Audacity would apply when it next opened the project. Neither file is changed. A log that does not belong to its project is set aside and the project is exported as last saved.
Free to open, play and export the stereo mix for projects up to 256 MB; larger projects still open and play free, and downgrading to .aup3 is free up to the same size. Recovery, per-track stems, and exports or downgrades above that size are a one-time $19 license — no subscription, no recurring fees.
Every job an Audacity project needs
Same local-first engine, one page per task.