
An Audacity AUP3 file is an editable Audacity project, not an interchangeable sound file. To place narration in a video editor, export audio in a format the receiving editor supports. Keep the project separately when you need to revise the underlying tracks, labels, or level decisions.
Key Takeaways
- Save Project preserves Audacity work.
- Export Audio produces a playable delivery file.
- A renamed extension does not convert project data into sound.
Agree on the artifact the editor needs
Ask whether the recipient needs finished narration, separate recordings, or the editable Audacity project. These are different handoffs. A video editor requesting a sound file may be unable to use the project even if Audacity opens it correctly.
The Audacity project manual distinguishes its project format from WAV or MP3 export and explains that projects retain tracks, labels, envelopes, gain, and pan data. It also notes that saved projects do not retain the session's Undo history. Plan explicit revision checkpoints rather than relying on a future Undo command.
Export the intended content
- Save the editable project with a clear revision name.
- Confirm which tracks and passage belong in the delivery.
- Use Export Audio and choose the format, channels, and sample rate agreed with the receiving editor.
- Give the exported file a name tied to its content and revision.
- Import that file into the receiving editing workflow and inspect its content and placement.
Retain the AUP3 file as an editing asset. Do not replace it with an exported mix unless the loss of independent track editing is deliberate and the source is protected elsewhere.
Verify a narration example
Suppose a film editor expects a narration mix for an anniversary montage. Sending only the saved AUP3 file leaves them without the expected playable artifact. Sending only a mixed WAV may solve playback while preventing an Audacity collaborator from changing an individual take.
A useful handoff can include both, clearly named for their purposes. Verify that the audio export contains the approved wording and no muted draft passage. Then check its start and final audible tail. This is a proposed delivery check, not a report that the files have passed it.
Preserve timing and quality decisions
If the editor needs several aligned tracks, specify a common start separately from the choice of audio format. Use the stem reconstruction checklist to define that acceptance task.
When further processing is expected, keep the editable source rather than repeatedly editing a compressed delivery file. The repeated-export quality guide explains the broader risk of passing a finished encode through successive applications; the Audacity project remains a distinct revision artifact.
Related tasks
- Why Do Delivered Dialogue, Music, and Effects Stems No Longer Line Up?
- Why Does My AI Clip Get Softer Every Time I Pass It Through Another App?
Sources and scope
- Audacity Manual: Managing Audacity Projects: AUP3 is Audacity-only project data; Export Audio creates WAV/MP3; saved project elements; Undo history is not retained on reopen.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance, not a claim of hands-on testing or independent review. Report a correction.
Cover: Pignatta / Pixabay, Content License. The city photograph is an illustrative source asset; it does not show this application or a test result.