> ## Content Index
> Fetch the complete content index at: https://soundforgepro.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Record Audio in Sound Forge Pro 2026
- URL: https://soundforgepro.com/how-to-record-audio-in-sound-forge-pro/
- Published: 2026-04-03T21:07:43.000Z
- Updated: 2026-09-04T11:55:44.000Z
- Description: Record audio in Sound Forge Pro with Windows permissions, ASIO setup, input routing, levels, and the right recording mode.
- Author: Erick Finn
- Tags: Core Editing

**To record audio in Sound Forge Pro 2026, verify Windows microphone access, select the correct driver, route the hardware input, create a file with the required format, open View → Record Options, arm the input and check the meters before pressing Record.** If the recorded file is silent, check permissions, the selected device and input routing before replacing the microphone.

Sound Forge is strongest for recording into one mono, stereo or multichannel audio file. It isn’t a multitrack DAW: several inputs can become channels in one data window, but you don’t get independent timeline tracks for arranging a band or podcast cast.

**Use a ten-second test:** stop, play it back from Sound Forge and save it before committing a performance or an entire record side. That small loop catches the wrong input, one-sided stereo, clipping and sample-rate mistakes while they are cheap.

![Microphone access granted in Windows, then the driver and record routing set in Sound Forge](https://storage.ghost.io/c/af/4b/af4b05d4-2e0b-4edc-8378-1e2a62fecc70/content/images/2026/08/record-audio-ui-route-arm-v3.webp)

Recording in Sound Forge: allow desktop microphone access, apply the driver, map file channels to device inputs, then arm and record.

## 1\. Allow microphone access in Windows 11

Open **Start → Settings → Privacy & security → Microphone**. Confirm Microphone access and **Let desktop apps access your microphone** are enabled. Sound Forge is a desktop application, so it may not appear as an individual Microsoft Store-style toggle.

[Microsoft’s current privacy guidance](https://support.microsoft.com/en-US/Windows/privacy/windows-camera-microphone-and-privacy) documents that Windows 11 path and the separate desktop-app control. If the permission is already on, don’t keep toggling it as a ritual; move to driver and routing checks.

## 2\. Select the driver in Audio Preferences

Go to **Options → Preferences → Audio**. The current Sound Forge help lists three Audio Device Type choices:

- **ASIO:** choose the manufacturer’s driver for a supported audio interface and low-latency routing.
- **Windows Classic Wave Driver:** choose a specific Windows audio device through the classic driver path.
- **Microsoft Sound Mapper:** let Windows choose the default playback and recording devices.

For a dedicated interface, start with its current manufacturer ASIO driver when one exists. For a simple USB microphone or built-in input, Classic Wave or Sound Mapper may be sufficient. “ASIO” is not a quality preset: a wrong or unstable driver is worse than a working Windows path.

Click **Apply** after changing the device type, then **Advanced**. With ASIO selected, **Configure** opens the interface maker’s control panel. The [Audio Preferences help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/audio%5Fpreferences.htm) and [Advanced Audio Configuration help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/advanced%5Faudio%5Fpreferences.htm) document those current controls.

There’s no universal 64- or 128-sample buffer worth copying. Lower settings can reduce monitoring delay but raise glitch risk; higher settings improve stability. If gaps appear in the recording, raise the interface or Sound Forge record buffer and test again. The safe value depends on driver, sample rate, channel count and the computer.

## 3\. Route the input to the data-window channels

Still in **Options → Preferences → Audio**, open the **Record** tab. In the **Channel** and **Device** table, assign each data-window channel to the intended hardware input. You can also change a channel’s input by clicking its channel number in the Record Options window.

The data window limits what is recorded. A stereo window records two routed inputs; a six-channel window is required to record six enabled inputs. The current [multichannel recording help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Fmultichannel%5Faudio.htm) explains this mapping and explicitly says Sound Forge is not a multitrack editor.

For one microphone, create a mono file unless the device intentionally delivers stereo. A mono mic copied to left and right isn’t a stereo recording; it’s just the same signal twice.

## 4\. Create the recording file

Choose **File → New** and set sample rate, bit depth, channel count and channel layout for the job. Follow the delivery or preservation specification instead of choosing the largest number in each list. When the interface and workflow support it, [24-bit capture provides more digital resolution and dynamic range than 16-bit](https://www.izotope.com/community/blog/digital-audio-basics-sample-rate-and-bit-depth), so conservative recording levels remain practical. It does not add analogue input headroom or prevent the microphone, preamp or converter from clipping. Set hardware gain below overload and keep the interface and Sound Forge sample rates aligned.

If **Mode → Create new windows** is selected in Record Options, Arm and Record remain available even when no data window is open, and each restart or resume creates a new data window. In Normal or Create regions mode, create or open a data window first. File → New is still the safer choice when sample rate, bit depth, or channel layout matters.

## 5\. Open Record Options and choose the current method

Choose **View → Record Options**. Legacy tutorials can blur the distinction between Method and Mode or show labels that are absent from the 2026 help. In the current release, Method controls how recording starts; Mode controls what Sound Forge does after you stop or pause and restart.

**Method** controls how recording starts:

- **Manual:** general recording, voice-over and recording into a selection.
- **Automatic: Threshold:** starts when the input crosses a set level and stops after it remains below the stop condition.
- **Automatic: MIDI Timecode:** follows specified incoming MIDI timecode.
- **Automatic: Time:** starts at a chosen date/time and runs for the specified duration.

**Mode** controls what happens when you stop or pause and restart:

- **Normal:** continue the ordinary recording workflow.
- **Create regions:** create a new region each time recording restarts or resumes.
- **Create new windows:** create a new data window for each restart or resume.

The current [Record Options documentation](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Foptions.htm) defines those methods and modes. For the first test, stick with Manual + Normal; threshold logic can wait until the basic input works.

## 6\. Arm, meter and monitor

Click **Arm** to open the recording device and load the buffers, then generate the loudest expected signal. Check that:

- the correct channel meters move;
- peaks remain below clipping;
- left/right routing is intentional;
- headphone monitoring has no feedback or obvious delay;
- the interface and Sound Forge agree on sample rate.

Set analogue gain on the microphone preamp or interface. Raising the waveform after a clipped converter won’t fix anything. Sound Forge’s [Recording Setup help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/recording%5Fsetup%5F.htm) recommends a strong signal with no clipping and defers hardware gain details to the device maker.

Record Options can monitor the input through the Plug-In Chain when **Monitor** is set to **On** or **Auto**, but the current help is explicit: the chain is for monitoring only and is not applied to recorded data. That is useful for hearing comfort EQ or dynamics without printing them into the raw take. Save a dry capture and process a copy later.

## 7\. Record, stop and verify the file

Press **Record** or **Ctrl+R**. Stop with Record or Stop; Pause suspends capture while keeping the device armed. When recording into a selected time range, Sound Forge stops automatically at the end of that selection.

Immediately play back the test from Sound Forge. Don’t rely on direct monitoring: direct monitoring proves the microphone reached the interface, not that the correct file was captured. Listen for dropouts, distortion, one missing channel, [DC offset](https://soundforgepro.com/remove-dc-offset-sound-forge/) and the wrong source.

Save the raw take losslessly before editing. For voice work, edit mistakes before noise reduction, EQ, dynamics and loudness. For a vinyl side, preserve the untouched high-resolution transfer before restoration. The [voice-over workflow](https://soundforgepro.com/sound-forge-pro-for-voice-over-recording/) and [vinyl restoration workflow](https://soundforgepro.com/sound-forge-pro-for-vinyl-restoration/) cover those different next steps.

## Prerecord buffer, pre-roll and punch-in

With Method set to Manual, click **Settings** in Record Options. The [current Creating a New Recording help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/record%5Fnew.htm) explains that a prerecord buffer writes audio continuously after you arm. When recording starts, the buffered data is committed to disk but may remain hidden beyond the recorded event edge; use the Event Tool to slip or trim the left edge and expose it.

Choose a buffer long enough to cover the opening you might miss, then verify that you can reveal the hidden lead-in with the Event Tool. The useful duration depends on the source and take, so the article doesn’t prescribe a universal five- or fifteen-second default.

For punch-in recording, select the part of an existing file to replace, use Manual recording with Normal or Create regions mode, and configure pre-roll/post-roll if you need context. The current [Recording into an Existing Sound File help](https://cdn.borisfx.com/borisfx/Documentation/soundforge/2026/en/content/record%5Fpunch-in.htm) confirms that recording occurs underneath that roll and that the Event Tool can reveal material beyond the visible edge. It is a cursor- or selection-based workflow, not a separate current “Punch-In” Mode.

## No input signal: check in this order

1. **Windows:** microphone access and desktop-app access are enabled.
2. **Hardware:** the mic/source reaches the correct interface input, phantom power is used only when required, and the hardware meter moves.
3. **Driver:** the intended ASIO, Classic Wave or Sound Mapper path is selected.
4. **Routing:** the input is enabled and assigned on Preferences → Audio → Record.
5. **File:** the data window has the required channel count.
6. **Format:** interface and application sample rates agree.
7. **Arm:** the Record Options meters move before Record is pressed.

For computer or system audio, Sound Forge can record only an input exposed by the selected driver. Don’t assume every PC has “Stereo Mix.” Use a loopback input only when the installed interface or driver provides one, select that actual input in Sound Forge and follow the driver maker’s routing instructions. If the meters still stay flat after this checklist, use the dedicated [Sound Forge no-input and ASIO troubleshooting sequence](https://soundforgepro.com/sound-forge-pro-not-recording-audio/) instead of changing several settings at once.

## Frequently Asked Questions

### How do I start recording in Sound Forge Pro 2026?

Create a file with File → New, route the input under Options → Preferences → Audio → Record, open View → Record Options, choose Manual + Normal, click Arm, verify the meters, then press Record or Ctrl+R.

### Which audio driver should I use in Sound Forge Pro?

Use the manufacturer’s ASIO driver for a supported audio interface when you need low-latency routing. Windows Classic Wave or Microsoft Sound Mapper can work for simpler devices. Choose the stable path that exposes the correct input and passes a clean test recording.

### Why does Sound Forge show no microphone signal?

Check Windows microphone and desktop-app permissions, hardware input and gain, Audio Device Type, Preferences → Audio → Record routing, the data window’s channel count, sample-rate agreement and the armed Record Options meters.

### What are the current recording modes in Sound Forge Pro 2026?

The Mode choices are Normal, Create regions and Create new windows. Method is separate: Manual, Automatic: Threshold, Automatic: MIDI Timecode and Automatic: Time. “Automatic retake” and “Multiple takes” are not the current Mode labels.

### Does monitoring through the Plug-In Chain record the effects?

No. Current Sound Forge help states that Monitor input through Plug-In Chain affects monitoring only; the chain is not applied to the recorded data. This lets you hear a comfort chain while preserving a dry take.

### Can Sound Forge Pro record several inputs at once?

Yes, when the audio device exposes multiple inputs and they are enabled and mapped to a data window with enough channels. The result is a multichannel audio file, not a multitrack timeline session.

### What does the prerecord buffer do?

After Arm, it continuously buffers the specified duration. When recording begins, that audio is committed to disk; use the Event Tool to slip or trim the recorded event’s left edge and reveal buffered material that is not initially visible.

After the take passes playback, continue with the appropriate workflow: [cut and trim the recording](https://soundforgepro.com/how-to-cut-and-trim-audio-in-sound-forge-pro/), choose [peak, RMS, or loudness normalization](https://soundforgepro.com/how-to-normalize-audio-in-sound-forge-pro/) only when delivery requires it, then [export and verify the final MP3](https://soundforgepro.com/how-to-export-mp3-from-sound-forge-pro/) while keeping the lossless master.

*Last fact-checked: September 4, 2026.*