Audacity 3 to 4 for Podcasts: Project Compatibility and an Upgrade Checklist

What opens, what saves, and what does not go back

Audacity's transition guide identifies AUP4 as the version 4 project format and says it opens AUP3 projects. Its save guide distinguishes an editable project from an exported audio file and documents saving to your own computer. Cloud saving is another option, not a requirement for this local-copy exercise.

Do not plan a round trip by renaming the extension or treating an export as a converted Audacity 3 session. Returning to the old workflow means returning to the preserved original, with any new edits reconciled deliberately. A rendered mix cannot substitute for the original editable arrangement.

Before opening a copy, close the source project in the application that owns it and finish its normal save. Follow your established backup procedure for a closed, saved project. Do not duplicate an actively changing session and assume the copy is a consistent recovery point.

Use the exact release notes, not an old problem list

Audacity 4.0.0 was released on September 3, 2026; the 4.0.1 page, released September 30, is marked Current at this review. The latter reports fixes for project corruption after a failed save, clips affected during AUP3 conversion, and opening files or projects with non-ASCII names or folders. It also adds multiple-file export and restores missing Audacity 3 shortcuts.

Our recommendation is to run the trial on the current stable build. If you made a candidate with 4.0.0, make a fresh copy of the preserved AUP3 original and convert that copy with the newer stable build before judging the upgrade. This avoids judging the current workflow from a candidate that may carry an earlier conversion problem; retain the earlier trial and notes if you need to investigate a difference.

The release notes are not proof that every project now converts perfectly. Conversely, repeating the fixed issues as known present-day defects would mislead a reader. If a later release is available when you use this guide, review its notes before applying a conclusion about 4.0.1.

If batch automation is essential, also consult the list of features not yet available in the 4.0.0 release page and the notes for your exact build. The older page lists features not yet available at that release; it does not establish what remains absent in every later version.

This is not a complete feature or plugin compatibility matrix. The version-specific release notes and the current transition manual give different plugin-support lists, so this guide does not combine them into a universal claim. Check any indispensable tool against the exact build and its own documentation; stop the upgrade if you cannot establish a usable workflow.

Give each file one job

Create a small migration record before testing. Make the candidate by opening a copy of the closed, saved AUP3 file in Audacity 4, not by opening your only original. Use names that make the source and candidate unmistakable, and store the backup away from the working folder. These names and checks are our suggested organisation, not required Audacity settings.

Choose an episode with at least two voices, several edits, a music or ambience transition, and the processing you actually use. A newly recorded single sentence may prove that a device works while telling you almost nothing about your edited podcast archive.

• Original AUP3 and independent backup — the return point. Keep it closed and untouched during the candidate test; record where it is and who owns it.
• Reference audio from the established workflow — the listening comparison. Note its duration, channel layout, and export settings before testing the new copy.
• Candidate AUP4 — the editable trial. Give it a distinct name and location; record the source project and exact application version.
• Candidate audio export — the delivery trial. Keep it separate from the reference so a familiar filename cannot hide a replacement.
• Acceptance note — the decision. Record the reviewer, date, checks completed, differences found, and whether the original workflow remains responsible for the next episode.

Know the editing changes that can affect a spoken-word timeline

The transition manual describes direct clip selection and warns that moving a clip onto another can replace the overlapped part underneath. It also replaces the old Sync-Lock workflow with ripple-style insert and delete choices. Classic workspace and clip-theme options can make the layout more familiar, but familiarity does not establish identical editing behaviour.

Use expendable sections in the candidate copy to rehearse a cross-track delete and an insert. Watch the guest track, host track, music cue, and any later marker together. Decide whether later material should move before executing the command; then inspect the result and undo it. Avoid memorising shortcuts from a different operating system or version.

That rehearsal addresses a different risk from file conversion. A project might arrive with correct timing, then drift when an editor applies an unfamiliar operation. Your acceptance record should distinguish an import mismatch from a new editing mistake.

Podcast migration acceptance worksheet

Run this on the candidate, with the reference and untouched original available. For each row record pass, unresolved, or fail, plus a timecode or filename. We have not performed these checks on your session; an empty worksheet is not a passed test.

• Open and inventory — compare the number and names of tracks, episode duration, labels, and the opening and closing positions with the original. Stop if audio is missing or an unexplained duration change appears.
• Timing anchors — compare a clear event near the beginning, middle, and end of each voice track. Listen across overlaps and transitions; matching the start alone will not catch later drift.
• Edit boundaries — inspect several cuts, fades, clip gains, and a music transition. Listen around the boundary rather than judging a waveform thumbnail. Mark any changed sound or timing for explanation.
• Required operations — rehearse one normal correction, one cross-track timing edit, and any indispensable processing step on the copy. Undo the rehearsal where appropriate and verify that unrelated tracks did not move.
• Save and reopen — save the candidate to its own AUP4 location, close it normally, reopen it, and repeat the important anchors. A view left open in memory does not demonstrate a usable saved handoff.
• Delivery — export with the intended sample rate, channel layout, encoding and loudness workflow. Open that audio independently; check duration, beginning and end, transitions, and representative speech against the reference.
• Handoff and return point — have the responsible editor identify the accepted project and export without help. Confirm the original and backup remain available; record which version will own the next real revision.

Decide pass, pause, or return to the original workflow

Pass only when the required checks are complete and any differences are understood and accepted by the editor responsible for delivery. This is an operational decision about your episode, not a claim of sample-identical output or universal compatibility.

Pause if the evidence is incomplete: for example, a collaborator has not reopened the copy or a necessary operation has not been located. A pause is different from a demonstrated defect. Keep the next deadline on the established workflow while you answer the specific question.

Return to the untouched original workflow if audio is missing, timing changes cannot be explained, a saved candidate cannot be reopened, or the intended delivery cannot be verified. Preserve the trial and your notes for investigation; do not overwrite the source in an attempt to make the new copy work.

For a partly edited production, the lowest-risk choice may be to finish that episode with the established system and evaluate the upgrade on a later copy. If you have already made new edits in AUP4, document them before deciding how to reproduce them elsewhere. This guide offers no automatic reverse converter or corrupted-project recovery guarantee.