Sound Forge and Vegas Pro Workflow for Video Editors

Vegas Pro and Sound Forge have had a round-trip audio editing workflow since the Sony era — a feature that lets you open any audio event from the Vegas Pro timeline directly in Sound Forge, edit it, save, and have the result appear back in Vegas automatically. Since Boris FX brought both applications into the same product family in March 2026, the existing round-trip workflow has become even more relevant for editors who want dedicated audio repair and mastering alongside Vegas Pro.

This guide covers the practical mechanics of that workflow and where it fits into a real video post-production session: when to stay in Vegas Pro, when to send audio to Sound Forge, and what Sound Forge adds that Vegas Pro's built-in audio tools don't.

Quick answer: In Vegas Pro, right-click any audio event on the timeline and choose Open in Audio Editor or Open Copy in Audio Editor. Sound Forge opens with that audio. Edit, clean, or master it in Sound Forge. Save. The result updates back in the Vegas Pro timeline. The difference between the two options determines whether the edit is destructive or creates a new take.

Recommended default: Use Open Copy in Audio Editor unless you intentionally want to overwrite the original source file. Open Copy preserves the original, creates a reviewable take, and lets you toggle back if the processing doesn't work out.

1. Set Sound Forge as the preferred audio editor in Vegas Pro: Options → Preferences → Audio.
2. Right-click any audio event on the Vegas Pro timeline.
3. Choose Open Copy in Audio Editor.
4. Edit or clean the audio in Sound Forge.
5. Save with Ctrl+S — do not use Save As or rename the file.
6. Return to Vegas Pro. A new take is created. Toggle between original and edited with the T key.

Setting Sound Forge as Vegas Pro's Audio Editor

The official Vegas Pro documentation on opening events in an audio editor confirms that when you first install Vegas Pro, it searches for Sound Forge software and automatically assigns it as the sound editor if detected. If it wasn't found on installation, or you want to verify the setting: Options → Preferences → Audio, Preferred audio editor field, browse to the Sound Forge executable.

The official menu path is Tools → Audio → Open in [editor name]. Right-clicking an audio event and choosing Open in Audio Editor or Open Copy in Audio Editor from the context menu does the same thing and is often faster during an edit session.

I configure this once per machine — about 30 seconds — and then the round-trip is available for every project without further setup. The setting persists across sessions.

Open in Audio Editor vs Open Copy in Audio Editor

I default to Open Copy for almost every round-trip. The original file stays intact, I can toggle back to it with T if the Sound Forge processing turns out too aggressive, and the workflow feels safer for client work where "undo" needs to be available weeks later.

Right-clicking an audio event in Vegas Pro gives two Sound Forge options. Understanding the difference between them matters before you start editing.

Open in Audio Editor opens the entire source audio file in Sound Forge. Any edits you save in Sound Forge overwrite the original file permanently. The change propagates immediately to every instance of that file anywhere in the Vegas Pro project — including other events on the timeline that use the same source file. This is the correct option when the file itself has a problem (noise, clipping, a hum that affects all uses of that clip) and you want the fix applied globally.

Open Copy in Audio Editor creates a copy of the audio file, opens the copy in Sound Forge, and on save creates a new take in Vegas Pro that sits on top of the original event. The original file is untouched. Toggle between the original and the edited version using the T key in Vegas Pro. This is the correct option when you want to try an edit without committing — processing a specific clip differently from other instances of the same source, or comparing a cleaned version against the original before deciding.

The Vegas Pro forum thread on this workflow documents a known behavior: if you choose Open Copy and then save with a different filename in Sound Forge rather than overwriting the copy, Vegas Pro may not automatically pick up the new file. The official documentation confirms: if you change the media file's name or location using Save As, you must import the edited file manually. Save using Ctrl+S to overwrite the copy filename Vegas created, which triggers the automatic take update.

What to Edit in Vegas Pro vs What to Send to Sound Forge

Most audio work in a video project should stay in Vegas Pro. Vegas Pro has volume automation, clip gain, real-time plugin chains per track, EQ, bus routing, and all the tools needed for standard mix operations. Sending every audio event to Sound Forge for processing adds round-trips that slow the session down without adding value.

Send audio to Sound Forge when the problem requires work that Vegas Pro's clip editor can't cleanly handle:

Noise floor problems in a specific clip. A location recording with HVAC bleed, camera mic hiss, or room noise that doesn't match the rest of the cut. Vegas Pro can apply a noise reduction plugin to the clip, but Sound Forge's noise print workflow — capture a noise profile from a silent section of the specific file, reduce the noise floor across that file — is more targeted and produces cleaner results. The full noise reduction workflow is in the noise reduction guide.

Clipped or distorted audio in a specific event. A clip that overloaded on input — flat-topped waveform peaks visible in the event. Vegas Pro has no tool for reconstructing clipped audio at the sample level. Sound Forge includes restoration and editing tools that can handle clipping repair depending on the edition and installed components.

Broadband noise or click artifacts from archival footage. Interview clips digitized from tape, stock footage with audible hiss, dialogue recorded over a steady electrical hum. These are restoration tasks Sound Forge's dedicated toolset handles more directly than a plugin chain on a Vegas Pro track.

A voice-over file that needs mastering before placement. A narrator delivered as a dry 24-bit WAV that needs noise reduction, de-essing, EQ shaping, compression, and loudness normalization to a delivery spec. Doing that chain in Sound Forge on the standalone file is faster than building an equivalent chain on a track in Vegas Pro, particularly when the same narration file needs to be delivered separately from the video project.

The decision of whether to send a clip to Sound Forge or handle it in Vegas Pro usually takes about five seconds: can a plugin chain on this track solve it cleanly? If yes, stay in Vegas. If no, right-click and open in Sound Forge.

Sample-level waveform repair. A single corrupted sample — a click, a pop from a phone notification, an edit artifact — that needs to be fixed at the waveform level. Sound Forge provides sample-level editing tools for this kind of work; Vegas Pro has no equivalent. The Sound Forge product page positions it as a specialist single-file audio tool that integrates with video editing software.

Dialogue Cleanup Workflow

Dialogue is the most common audio problem in video post-production and the task where the Sound Forge round-trip adds the most value. A typical dialogue cleanup pass in Sound Forge covers three things: noise floor reduction, de-clipping if needed, and de-essing for harsh sibilance.

The sequence for each dialogue clip sent to Sound Forge: first check the waveform for clipped peaks — flat tops at 0 dBFS — and run a clipping repair pass before anything else. Then capture a noise print from a moment of silence within the clip (breath pause, room tone before speech begins) and run noise reduction. Then check for sibilance and apply de-essing if the S and SH sounds are harsh on headphones.

Round-trip one clip, review it on the Vegas Pro timeline in context with the adjacent clips and the underlying music or room tone, and adjust the noise reduction settings if needed before processing the rest. Noise reduction that sounds fine on an isolated clip can occasionally sound slightly processed when it plays back in context — the Vegas timeline is the right place to make that judgment, not Sound Forge in isolation.

In a typical documentary cut with material across multiple locations, some clips will be clean enough for Vegas Pro clip gain and a plugin; others will have consistent noise floor problems that benefit from Sound Forge's dedicated noise reduction. Sending every clip to Sound Forge adds unnecessary time; sending none leaves audible problems on the clips that need restoration. The split decision — handle simple problems in Vegas Pro, send complex ones to Sound Forge — keeps the session moving at the right pace.

Voice-Over Post-Production Workflow

Voice-over for video follows a cleaner path than multi-location dialogue because the recording conditions are more consistent. The typical workflow: the VO artist delivers a 24-bit WAV from their home studio, the file has some room tone character and possibly a low-level noise floor, and it needs to match the quality level of professional narration on delivery.

In Sound Forge: noise reduction pass (capture the noise print from the pre-roll before speech, reduce by 8–12 dB), EQ correction (high-pass around 100 Hz to remove proximity effect, gentle presence boost at 2–4 kHz if the voice needs forward placement), compression, loudness normalization. Export the finished WAV. Import into Vegas Pro and place on the narration track.

In a typical narration delivery with some room noise, the Sound Forge pass — noise print from pre-speech room tone, noise reduction, EQ high-pass, light compression — handles the cleanup before the file goes back to the Vegas Pro timeline. The narration track sits cleanly without further attention.

If the VO file needs to be delivered separately as well as placed in the video — common for broadcast or training video where the client wants the isolated audio files — Sound Forge produces both in the same session. Export the mastered WAV as the standalone delivery file, then use Open Copy in Vegas Pro to bring it into the project without disturbing the standalone file.

The full voice-over processing workflow including ACX delivery requirements is in the voice-over guide.

Final Audio Mastering for Video Delivery

After picture lock and audio mix, the final audio deliverable — a stereo mix of the full video's audio, or separate stems — often needs a mastering pass before delivery. This is where Sound Forge handles the finishing step entirely outside Vegas Pro.

Export the finished audio mix from Vegas Pro as a 24-bit WAV. Open in Sound Forge. Run Statistics to see the pre-mastering state. Apply EQ correction if the mix has frequency problems that the Vegas monitoring chain didn't reveal. Apply dynamics processing. Adjust final loudness and true peak toward the delivery target — broadcast specs vary by territory and distributor (commonly EBU R128 around -23 LUFS in Europe, ATSC A/85 around -24 LKFS in the US). For web and streaming, -14 LUFS is a common practical reference point, but verify the actual delivery requirements for each platform. Export the finished master.

On a recent corporate documentary — 22-minute finished cut for broadcast delivery — the final audio master required EBU R128 compliance. The Vegas Pro mix was sitting at -18 LUFS integrated on export. The Sound Forge pass (EQ correction on the low-mid buildup from the mix room, gentle limiting, final Statistics verification) brought it to -23 LUFS with LRA within spec in about eight minutes.

For broadcast delivery specifically, Sound Forge's loudness metering lets you verify the integrated LUFS, true peak, and LRA (loudness range) against the EBU R128 or ATSC A/85 specification before delivery. Vegas Pro has loudness metering on its master bus, but running the final verification on the exported file in Sound Forge gives a clean read of the actual delivery file rather than the mix bus output — which can differ slightly depending on export settings.

The full mastering workflow including loudness targets by delivery format is in the mastering guide.

SoundApp and When It's Enough

As of June 2026, Vegas Pro Ultimate includes SoundApp, a standalone CrumplePop-powered application for AI-based audio separation and cleanup, as confirmed on the Vegas Pro plans and pricing page. For many video editors, SoundApp handles audio problems quickly enough that Sound Forge isn't needed on every project.

SoundApp's strength is speed on straightforward problems: isolate dialogue from a mixed soundtrack, remove wind noise from a clip, clean up background noise in location audio that doesn't have a consistent noise print. It works on mixed-down files — you don't need the original isolated tracks. For editors who don't want to configure a round-trip workflow or learn Sound Forge's toolset, SoundApp covers the most common audio cleanup tasks without leaving the Vegas Pro ecosystem.

On straightforward interview packages — consistent room, quality talent, clean recording chain — SoundApp handles the audio cleanup without needing Sound Forge at all. Many video editors complete deliverables entirely in Vegas Pro with SoundApp for the simpler projects.

Sound Forge adds value over SoundApp when the problem is complex enough that AI cleanup introduces artifacts, when the audio needs sample-level repair that no AI tool addresses, or when the file needs a proper mastering chain rather than cleanup alone. The two tools aren't competing — SoundApp is fast and good enough for most location audio problems; Sound Forge is the tool when fast and good enough isn't sufficient. The Sound Forge vs Vegas Pro comparison covers the full differences between the two.

Common Round-Trip Mistakes

These are the problems that come up repeatedly in the Vegas Pro forums and support threads on the Sound Forge / Vegas Pro workflow.

Using Open in Audio Editor when you meant Open Copy. Open in Audio Editor overwrites the original source file permanently. If the same file is used elsewhere in the project, every instance changes. Open Copy is the safer default for most round-trip work.

Using Save As in Sound Forge and breaking the automatic update. The official documentation is explicit: if you change the filename or path, Vegas Pro will not detect the update automatically and you need to reimport the file manually. Always save with Ctrl+S to overwrite the copy Vegas created.

Sending every clip to Sound Forge. Most audio problems in a Vegas Pro project are solvable with a plugin chain on the clip or track. Sound Forge is for the cases where a plugin chain isn't enough — noise floor, clipping, sample-level damage. Routing clean clips through Sound Forge adds round-trip time without adding quality.

Running noise reduction without checking the result in timeline context. Noise reduction that sounds clean on an isolated file can sound processed when it plays back against music, room tone, or adjacent clips on the Vegas timeline. Do the Sound Forge pass, return to Vegas, and review the take in context before applying the same settings to the rest of the project.

Forgetting to verify loudness on the final exported file. The loudness reading on Vegas Pro's master bus meters reflects the mix, not necessarily the rendered file. Export the audio, open it in Sound Forge, and run Statistics to confirm integrated LUFS and true peak against the delivery spec before submitting.

Frequently Asked Questions

How do I open a Vegas Pro audio clip in Sound Forge?

Right-click any audio event on the Vegas Pro timeline. Choose Open in Audio Editor to open the source file directly in Sound Forge — changes saved in Sound Forge will overwrite the original and propagate to all uses of that file in the project. Choose Open Copy in Audio Editor to work on a copy — on save, Vegas Pro creates a new take over the original event, which you can toggle with the T key. Set Sound Forge as the preferred audio editor first: Options → Preferences → Audio → Preferred audio editor.

What is the difference between "Open in Audio Editor" and "Open Copy in Audio Editor" in Vegas Pro?

Open in Audio Editor opens the original source file. Saves are permanent and affect every instance of that file in the project. Open Copy in Audio Editor creates a duplicate, opens the copy, and on save creates a new take in Vegas Pro without touching the original. Use Open in Audio Editor when the problem affects all uses of the file and you want a permanent fix. Use Open Copy when you want to process one event differently or compare the result against the original before committing.

What audio problems should I fix in Sound Forge vs Vegas Pro?

Fix in Vegas Pro: clip gain, volume automation, plugin chain per track, EQ and compression on individual tracks or buses, standard mix operations. Send to Sound Forge: consistent noise floor in a specific clip, clipped or distorted audio, broadband hiss from archival footage, voice-over files needing a full processing chain, sample-level clicks or pops that need the Pencil tool. Most audio work stays in Vegas Pro; Sound Forge handles problems the clip editor can't cleanly solve.

How do I master video audio for delivery in Sound Forge?

Export the finished audio mix from Vegas Pro as a 24-bit WAV. Open in Sound Forge and run Statistics for the pre-mastering state. Apply EQ correction and dynamics processing. Adjust final loudness toward the delivery target — broadcast specs vary by territory; for streaming, -14 LUFS is a common reference point rather than a universal standard. Verify integrated LUFS, true peak, and LRA via Statistics before export. Export the finished delivery file. The full workflow is in the Sound Forge mastering guide.

Is Sound Forge still integrated with Vegas Pro after the Boris FX acquisition?

Yes. The Vegas Pro external audio editor workflow remains part of the current Vegas Pro feature set. Boris FX acquired Vegas Pro, Sound Forge, and Acid Pro from MAGIX in March 2026. Boris FX has not announced a specific Vegas Pro-to-Sound Forge integration roadmap beyond the existing external editor workflow, but the Open in Audio Editor and Open Copy workflows are fully functional in current versions. Check the current Vegas Pro documentation for exact menu behavior.

Why does Vegas Pro not update after I save in Sound Forge?

The most common cause is using Save As in Sound Forge with a different filename or path. The official Vegas Pro documentation states that if you change the file's name or location, Vegas Pro will not automatically detect the update — you need to import the new file manually. Use Ctrl+S in Sound Forge to overwrite the copy Vegas created, which triggers the automatic take update. Also confirm you opened a copy using Open Copy in Audio Editor, not the original via Open in Audio Editor.

Should I use SoundApp or Sound Forge for audio cleanup in Vegas Pro?

Use SoundApp for fast AI cleanup: isolating dialogue, separating stems, removing consistent background noise from a clip where you don't need manual control. SoundApp is faster and doesn't require a round-trip workflow. Use Sound Forge when the problem needs manual control — noise reduction with a custom noise print, clipping repair, sample-level waveform editing, or a full mastering chain on a finished audio file. SoundApp and Sound Forge cover different points on the complexity scale; which one fits depends on the specific problem.