SoundForgePro.com is a separate editorial site about Sound Forge, iZotope and Boris FX software and related editing workflows. It is not an official Boris FX, iZotope, MAGIX, Sony Creative Software, or Sonic Foundry publication, and references to their products do not imply vendor endorsement.
Correction, September 16, 2026: an earlier version made broad claims about sponsorship, affiliate revenue, outside approval, universal sourcing, hands-on authorship and update practices that we could not substantiate across the site's history. It also used a speculative product-integration example that no longer provided reliable current context. Those statements have been removed or limited below. This policy describes the standard for current editorial corrections and future work; it does not certify every older page.
Evidence and sourcing
Claims should be matched to the most direct source available. Product features, supported systems, prices, bundle contents, release details and menu paths should be checked against current vendor documentation or another source responsible for the fact. A source should be linked near the claim when it helps the reader verify it. Older ownership or feature history should be labeled with the relevant period instead of being presented as current.
Documentation establishes what a vendor publishes. Claims about processing speed, CPU load, latency or repair quality come from published measurements: lab-style reviews, video comparisons that show their figures and forum reports that give the build and hardware. A test section combines several of these sources and reports the median or mean, the range and the source count; a figure that rests on one source is attributed to that source. A community post without numbers can raise a question but doesn't settle it. A calculation or browser check is reported with the inputs and settings it covered. The Review Methodology explains these distinctions in detail.
Reviews and recommendations
A recommendation should name the evidence that decides it: a composite test result, a documented capability or the license terms. Every data point behind a composite is logged with its source, date, version, hardware and settings, and key sources are linked where their numbers appear. We don't describe a test session, equipment or listening comparison that didn't take place.
Ratings are editorial judgments unless a page explicitly defines another method. They must not be described as user aggregates, laboratory scores or measured category averages without corresponding evidence. The current Sound Forge review explains how its rating should be read.
Commercial relationships and disclosures
If a sponsorship, affiliate arrangement, free access, gift or other material relationship affects a page, it is disclosed clearly near the relevant recommendation or link so readers can weigh it. Paid or affiliate links, if used, also carry the appropriate rel attribute (sponsored or nofollow).
A September 16, 2026 review of the current public HTML found no outbound links marked rel="sponsored" and no recognizable affiliate redirect pattern. Where a material relationship applies, readers should be able to rely on a clear page-level disclosure instead of guessing from URL formatting. The site's Disclaimer explains the separate-site and trademark context.
Authorship and automation
Erick Finn is the editorial byline used on this site. The byline shows who is responsible for published work; on its own it doesn't prove credentials, location, equipment ownership or hands-on product use. The About page describes the site's current purpose and identity boundaries.
AI-assisted tools and scripts may help with research, drafting, claim comparison and technical validation. Their output isn't a source, and it doesn't show that anyone operated Sound Forge, listened to audio or verified a product claim. Material statements are checked against the cited source before publication.
Updates and corrections
Current corrections should keep the page URL where practical, update visible text and dependent structured data together, and add a dated note when an earlier material claim could mislead a reader. A modified date should reflect a substantive change; it isn't a cosmetic freshness signal.
To report an outdated instruction, unsupported experience claim or other factual error, follow the Corrections Policy and include the page URL, the disputed wording and a primary source or reproducible steps when possible.
Publication boundaries
- No fabricated named users, quotations, testimonials, test sessions or measurements.
- No cracks, keygens, serial numbers or unofficial download mirrors.
- No synthetic or altered interface presented as a genuine product screenshot.
- No speculation presented as a confirmed feature, acquisition plan or release commitment.