Audacity 4 documentation · Primary-source explanation; examples are illustrative. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Check the editor requirement before conversion
Audacity 4 release notes specify its new .aup4 project format. They explain that .aup3 projects open and convert without changing the original, while converted projects cannot be saved back to .aup3. This matters when a collaborator or a second computer must continue editing in Audacity 3. A playable audio export is useful for listening but does not substitute for an editable project in the required application version.
Make the handover an explicit comparison
For an original preparation plan, retain the original .aup3 file and create the converted working project under a distinct name. Record which application version is expected on the receiving computer. Open a copy there and inspect track structure, clip positions, effects and a recognisable passage before treating the conversion as a completed handover. Keep the original available until the future editing route is settled; a renamed extension does not reverse a project format conversion.
Review the workflow as well as the file
The same release notes identify interface changes and several Audacity 3 capabilities absent at the 4.0 launch, including Macro Manager and the scripting pipe. Check the particular installed release if the project depends on automation or a specific plugin workflow, rather than assuming an opening project proves every production step is available. These are documented migration limits, not a claim that a project was converted here or that every third party effect behaves identically across versions.