Sound Forge Markers and Regions: Navigate & Export

Quick answer: press M to place a marker at one exact time. Make a time selection and press R to save its start and end as a region. Use markers for navigation, notes, and future boundaries; use regions when Sound Forge must recall, process, loop, or export a complete span of audio.

The distinction is small in the Regions List and decisive in real work. A marker answers “where?” A region answers “from where to where?” Once that is clear, chaptering interviews, splitting concerts, preparing samples, comparing passages, and extracting dozens of files all become the same manageable workflow.

Marker vs Region: The Difference That Matters

Neither object cuts, copies, or changes the waveform by itself. They are metadata attached to the file or working document. That makes them safer than destructive edits for planning, but only if you save in a format and workflow that retain the metadata you need.

Place, Name, and Refine Markers

1. Put the cursor at the required time or play the file.
2. Press M to add a marker.
3. Enter a short, unique name when prompted.
4. Open the Regions List to review names and positions.
5. Zoom in and move rough live-dropped markers to the real boundary.

The current Sound Forge marker documentation confirms that a marker can be inserted at the cursor or during playback. A marker dropped while listening is normally a first-pass note: reaction time makes it late. Use the waveform and another listening pass to refine it.

Name markers for the decision they represent: Verse 2, Chapter 04, Remove cough, Track 07 start. Names such as Marker 12 stop helping once the list becomes long. If the markers will become file boundaries, use the final ordering convention before conversion so mistakes are visible early.

Navigation Markers vs Export Markers

Not every marker should become a region boundary. Navigation markers can identify a quote, noise, edit note, or musical section. Export markers define the start or end of a deliverable span. Mixing both jobs in one undifferentiated list is how accidental five-second files and missing sections appear. Prefix notes consistently—NOTE – chair squeak—or keep only actual boundaries before running Markers to Regions.

Create a Region from a Selection

1. Drag across the exact audio you want to preserve.
2. Play from before the selection start through the start.
3. Play from before the selection end through the end.
4. Press R and give the region a meaningful name.
5. Clear the selection, then recall the region to prove both boundaries were stored.

The official region reference describes a region as a named time range. Its value is recall: you can return to the same start and end after the temporary selection has disappeared.

Adjust One Edge or Move the Whole Region

Drag a region boundary when the start or end is wrong. When the duration is correct but the entire span belongs earlier or later, move the region tag while using the modifier documented by the current interface rather than dragging one edge and trying to recreate the original length. After any movement, recall and play both edges again.

For sample extraction, speech chapters, and track splitting, move boundaries with audio context visible on both sides. A region can be mathematically correct and still sound wrong because the first breath lies just outside it or the last reverb tail extends beyond it.

Convert Track Markers into Regions

For one long recording, placing a region manually around every track is unnecessary. Drop markers at each track start, add one final marker at the end of the last track, then choose Edit → Regions List → Markers to Regions. Sound Forge creates a region between each consecutive pair.

The current Markers to Regions help gives the important arithmetic: three markers create two regions. Therefore five tracks need six explicit boundaries when the first start and last end are both marked. If the final marker is missing, the last track cannot receive a closing region boundary.

Before conversion, remove or clearly separate note markers that are not track starts. After conversion, rename the resulting regions and compare the count with the cue sheet. The complete long-recording splitting workflow covers applause, room tone, filenames, and gapless delivery.

Extract Regions as Separate Files

1. Open Tools → Extract Regions.
2. Select the intended regions.
3. Choose a dedicated output folder.
4. Use ordered, descriptive region names.
5. Set a prefix only when it adds project context.
6. Extract, then reopen the resulting files for QA.

The official Extract Regions documentation explains long and legacy short filename behavior. Use long filenames unless an old destination explicitly requires truncated 8.3 names. Leading zeroes keep 01 through 12 in the intended order.

Extraction is not approval. The export can complete successfully while a region starts late, ends early, or has the wrong name. Treat it as a render step followed by a separate listening and file-integrity step.

Boundary QA Before Processing or Export

• Start: preserve the inhale, consonant, pick noise, count-in, or room tone that makes the entrance natural.
• End: keep decays, applause, ambience, and release consonants unless the edit intentionally removes them.
• Click risk: inspect non-zero sample discontinuities and use a nearby zero crossing or minimal fade when appropriate.
• Count: compare marker and region counts with the expected programme structure.
• Sequence: listen to adjacent exported files back to back when continuity matters.

Do not judge boundaries only by the waveform. Low-level ambience can be visually tiny and audibly essential; a loud transient can begin before its largest peak. Listen several seconds before and after each edge. If a region is only a processing target, also listen to the transition between processed and untouched audio.

Markers and Regions for Repeatable Editing

Regions are useful even when no files will be extracted. Save a noise-only passage before noise reduction, a representative loud section before level processing, or a difficult transient before time stretching. Recalling the same passages makes comparisons fair and prevents each setting from being judged on different material.

For batch-oriented work, use regions to approve content boundaries and the Sound Forge Batch Converter only after the lossless files are correct. For a loudness check, define representative and full-programme ranges, then use the loudness-meter workflow without confusing a short selection with programme-integrated loudness.

Markers, Regions, and File Formats

Do not assume every delivery format, player, or editor will preserve Sound Forge marker and region metadata. Keep a working master in a suitable lossless format and verify metadata after saving or transferring the file. If a downstream system needs a cue sheet, chapter list, or separate files, create and test that deliverable explicitly rather than relying on hidden metadata.

When metadata matters for archival work, save a text record of names and time positions alongside the master. A region list inside one application is convenient; an external cue sheet is easier to audit years later when software and file-format support have changed.

Auto-Generated Regions Need Review

Auto Trim/Crop can create candidate regions from audio separated by silence. It is useful for consistent sample sets and cleanly separated speech clips. It is unreliable when the noise floor changes, vinyl never becomes silent, audience ambience bridges songs, or quiet notes fall below the threshold.

After automatic creation, sort the Regions List, look for implausibly short or long ranges, and audition every edge. Automation should reduce marker placement, not remove editorial responsibility.

Four Practical Region Workflows

Interview Chapters

Drop rough markers while listening, then move them to the start of complete thoughts rather than the first visible syllable. Turn approved chapter spans into regions and name them with the chapter number and subject. Keep a short bed of matching room tone at each entrance so a player that pauses between files does not expose a hard digital cut.

Concert and LP Track Boundaries

Mark song starts, add the final end marker, and decide whether applause belongs to the preceding song or the next. Check adjacent regions in sequence. For vinyl, surface noise may hide visual gaps; follow musical phrasing and label information instead of treating the lowest waveform area as an automatic split.

Sample and Foley Libraries

Save one region per usable event with consistent category, perspective, and take names. Leave enough pre-roll to avoid clipping the attack and enough tail to preserve the acoustic space. If every region will receive identical format conversion, extract approved lossless files first and batch-convert those masters afterward.

Repair and Comparison Passes

Create regions around a representative noise-only section, a difficult transient, the loudest passage, and an exposed quiet passage. Use the same ranges for every plugin or process comparison. This keeps one setting from winning merely because it was auditioned on easier material.

Pre-Export Region Checklist

• Every region has a unique, ordered, human-readable name.
• The region count matches the cue sheet or expected deliverables.
• No note marker was accidentally converted into a tiny region.
• The first boundary preserves natural pre-roll and the final boundary preserves the tail.
• Adjacent live or narrative regions have been played in sequence.
• Sample rate, bit depth, channel count, and destination folder are documented.
• The full working master and an external list of names and times are retained.

This checklist catches structural errors before extraction multiplies them. Correcting one region in the working master is fast; discovering the same naming or boundary error after metadata, conversion, upload, and delivery is not.

Common Failures and Fixes

• Pressing M created a point, not a selected range: make the selection and press R for a region.
• The final track is absent: add a closing marker after it and recreate the final region.
• Too many regions appeared: remove note markers before converting boundaries.
• A recalled region has the wrong duration: adjust the incorrect edge, then recheck both.
• An exported file clicks: repair the sample discontinuity or place the boundary in safer material.
• Names sort incorrectly: add leading zeroes and use one naming convention before extraction.
• Metadata disappeared elsewhere: verify the destination format and export a cue sheet or files explicitly.

Markers and Regions FAQ

What is the shortcut for a marker in Sound Forge?

Press M to add a marker at the cursor or current playback position. Refine markers dropped during playback because reaction time usually places them late.

What is the shortcut for a region?

Make a time selection and press R. The region stores both selection boundaries and can be named, recalled, adjusted, and extracted.

Why is the last part missing after Markers to Regions?

Regions are created between consecutive markers. Add a final marker at the end of the wanted audio so the last interval has a closing boundary.

How do I move a region without changing its length?

Move the region as a whole using the region tag and the modifier shown by the current interface. Then recall it and verify that start, end, and duration all moved together.

Can Sound Forge export every region as a file?

Yes. Use Tools → Extract Regions, select the wanted named regions, choose a folder and naming scheme, then reopen the files to check boundaries and order.

The Practical Rule

Use markers to remember one instant and regions to preserve a complete range. Name them for their job, keep note markers separate from export boundaries, audit both edges, and never treat a successful extraction as a substitute for listening.

Last fact-checked August 5, 2026 against the current Sound Forge 2026 online help.