How to Restore Old Audio Recordings at Home

Calibrate Hardware First

Most home restorers plug a turntable directly into their computer's microphone jack and wonder why the result sounds like a blanket was thrown over the speaker. The answer is not software. A turntable cartridge outputs a signal that is both extremely low voltage and deliberately equalized with a steep bass cut and treble boost — the RIAA curve. Without a phono preamp that applies the inverse RIAA equalization, the signal entering your audio interface will lack the low frequencies that define a full-bodied recording. Audacity's documentation is explicit on this point: a phono preamp is mandatory for vinyl digitization. No amount of post-hoc EQ in software can reconstruct bass that was never captured at the analog stage; you are simply amplifying noise floor where the signal should have been.

The same principle applies to tape decks, though the failure mode is different. Reel-to-reel and cassette decks require the bias level to match the tape formulation — Type I (ferric), Type II (chrome), or Type IV (metal). A deck set to the wrong bias will under- or over-magnetize the tape, causing permanent high-frequency loss during playback that no digital filter can reverse. Check the tape shell for the type marking and set the deck's bias switch accordingly before you press record. This is a one-time hardware decision; getting it wrong means the frequencies above 8kHz are gone before they reach your ADC.

One r/audioengineering thread consistently flags a second hardware trap: cheap USB audio interfaces that lack proper ground isolation. A 60Hz hum — the frequency of mains power in North America — can bleed into the signal path at a level that masks quiet passages entirely. The fix is not a software notch filter applied later, which will also remove fundamental frequencies from bass instruments and male speech. The fix is hardware: use an interface with balanced inputs (XLR or TRS) and a ground-lift switch, or insert an external ground-loop isolator between the turntable preamp and the interface.

Input gain staging is the final hardware calibration that most guides skip. Set the gain so the loudest peak hits around -6dBFS on your recording software's meter. Clipping at the analog stage produces a flat-topped waveform that no declipping tool can fully reconstruct; the information about the original waveform's shape is simply gone. iZotope RX Declip can interpolate short bursts, but it cannot invent a continuous clipped passage longer than a few milliseconds. Set the gain so the loudest peak hits around -6dBFS on your recording software's meter. 24-bit depth gives you 144dB of dynamic range — there is no penalty for conservative gain. You can always amplify a clean recording later. You cannot un-clip a distorted one.

Before you connect a single cable, clean the vinyl with a carbon-fiber brush and anti-static solution. Surface dust and static discharge create pops that restoration software treats as signal, forcing the declicker to work harder and increasing the chance of audible artifacts in the final file. This is a five-minute mechanical step that directly reduces the number of false positives your software will generate. Skip it, and you are asking a spectral editor to distinguish between a dust particle and a snare hit — a task it will fail at with predictable regularity.

Action for today: locate the phono preamp or tape deck bias switch in your setup. Do not digitize another record until the hardware chain is verified. The software can wait.

Capture at 24-Bit Depth

The single most impactful setting in your restoration chain is not a filter or a plugin — it is the bit depth and sample rate you choose before you press record. According to iZotope and Audacity documentation (as of July 2026), capturing at 24-bit depth and 96kHz sample rate preserves the dynamic headroom and ultrasonic content that makes later noise reduction effective without introducing aliasing artifacts. Most consumer software defaults to 16-bit/44.1kHz, which is a format designed for final distribution, not archival capture. That default discards roughly 48 dB of dynamic range and cuts off all frequency content above 22.05 kHz. No amount of post-hoc EQ in software can reconstruct frequencies that were never captured at the analog stage; you are simply amplifying noise floor where the signal should have been.

If your audio interface supports 96kHz, use it. If it does not, 48kHz is the minimum acceptable capture rate for restoration work. Never downsample until every processing step — declick, dehum, denoise, declip — is complete. A common failure mode reported in practitioner threads is exporting the raw capture as MP3 for quick listening, then discovering that the compression artifacts from that MP3 are now permanently embedded in the source file. The correct archival export is 16-bit/44.1kHz WAV or FLAC. Reserve MP3 for the final shareable version only after all restoration is done and you have a lossless master.

Audacity and several modern DAWs offer a 32-bit float recording mode. When available, this is strictly superior to 24-bit for restoration. A 32-bit float file cannot clip at the recording stage; it stores the signal as floating-point values that represent the voltage ratio rather than a fixed integer range. This means a transient that would have hit 0 dBFS and distorted in a 24-bit recording is instead stored as a value above 0 dBFS, recoverable in post by simply reducing the gain. A recording engineer on a production forum described recovering a vocal take that had been recorded 18 dB into the red — the 32-bit float file restored it to clean, undistorted audio with no visible waveform flattening. If your interface and software support it, enable 32-bit float and never worry about setting recording levels again.

The practical consequence of ignoring these capture settings is that you spend hours applying noise reduction to a file that already has irreversible quantization noise baked in. A 16-bit recording of a 1940s radio broadcast will have a noise floor around -96 dBFS, but the hiss from the original medium may sit at -70 dBFS. That leaves only 26 dB of separation between the noise you want to remove and the digital noise floor. A 24-bit capture gives you 144 dB of theoretical dynamic range, pushing the digital noise floor far below the medium noise so that spectral editing tools can work on the actual source artifacts rather than fighting the recording format itself. Set your DAW to 24-bit/96kHz before you connect the turntable or cassette deck. If 32-bit float is available, use it. Downconvert only at the final export step, and only after you have verified that every restoration pass is complete.

Order of Operations

Most restoration guides tell you to grab a noise profile and hit reduce. That sequence destroys more recordings than it saves. The correct order is fixed: de-click first, then de-hum, then de-noise, then EQ last. Audacity's own documentation states that clicks and pops must be removed before noise reduction because those transients mask the noise floor, causing the algorithm to sample an inaccurate profile. Apply noise reduction first and the plugin treats every crackle as part of the signal, producing that swirly underwater artifact that beginners blame on the source medium.

Hum is tonal and narrowband; a notch filter or spectral edit can isolate it cleanly without touching the rest of the audio. A thread on a production forum notes that iZotope RX's spectral de-hum tool lets you visually select the exact harmonic series and remove it in one pass, whereas Audacity's built-in notch filter requires manual frequency entry and risks cutting adjacent content if the hum drifts slightly. Remove hum while it is still isolated, before broadband processing smears it into the noise floor.

Broadband noise reduction is the third step, and it should be applied in passes of 6–12 dB reduction each, not a single aggressive cut. The reason is perceptual: the human ear adapts to a constant noise floor, and a 6 dB reduction often sounds like "silence" once the music plays, while a 20 dB cut introduces the metallic flutter that forum threads call "the Audacity sound." Take a noise sample from a section of pure silence between tracks — not from a quiet passage with reverb tails — and apply reduction in two or three gentle passes, listening after each one.

EQ comes last, and this is where most hobbyists sabotage their work. Boosting high frequencies before denoising amplifies tape hiss and surface noise, making the noise reduction pass far less effective because the algorithm sees a higher noise floor. Apply a high-shelf boost around 3kHz only after all clicks, hum, and broadband noise are removed. For a 1940s radio broadcast that sounds muffled, a +3 to +6 dB shelf starting at 3kHz is typical, but the exact curve depends on the original recording's microphone and transmission chain — there is no universal preset.

For vinyl specifically, a dedicated de-clicker plugin like iZotope RX or the free ClickRepair tool outperforms Audacity's built-in click removal on severe surface noise. Audacity's algorithm works by detecting samples that exceed a threshold and interpolating across them, which leaves audible artifacts on long crackle trains. Spectral editing in RX lets you see each click as a vertical line in the spectrogram and remove it without touching the surrounding groove noise. A restoration engineer on a production forum describes spending three hours on a single side of a 78 RPM record using Audacity's click removal, then finishing the same side in twenty minutes with spectral editing — the difference is not speed but the absence of interpolation artifacts.

Avoid Over-Processing

The single most destructive act in home audio restoration is applying too much noise reduction in one pass. According to iZotope's published guidelines (as of July 2026), any reduction exceeding 6–12 dB in a single pass will introduce metallic artifacts and destroy speech intelligibility. The correct workflow is a gentle first pass at 6 dB, a careful listen, then a second pass if needed. One aggressive pass creates a "swirly" or "underwater" sound that no subsequent processing can fix.

AI-based tools like Adobe Podcast Enhance are particularly dangerous here. When background noise is louder than the voice, these tools often remove sibilant consonants — s, t, sh — producing a watery, muffled result that sounds worse than the original noise. Reddit threads on r/audioengineering consistently report that the "underwater" effect is the number one regret from beginners who trusted a single-click AI fix. The solution is to lower the reduction amount and increase the number of passes, never to rely on a single aggressive algorithm.

Spectral editing offers a precise alternative to broadband noise reduction. This is the correct method for removing electrical hum, not a global noise reduction filter that will eat the room tone and transients. To verify you have not over-processed, listen for "breathing" — the noise floor pumping up and down — and check the spectrogram for unnatural gaps or missing frequency bands above 8kHz. If you see a clean horizontal cut through the spectrogram, you have removed too much.

For batch-processing cassette tapes, the mistake is creating a new noise profile for every file. Instead, capture a single noise profile from a blank leader section of one tape, ly the same noise reduction settings to all files using Audacity's Macros feature. This ensures consistent processing across a batch and avoids the variable artifacts that come from re-profiling each track. The playback head azimuth alignment should also be checked with a 1kHz test tone before you start the batch; misalignment causes high-frequency loss that you cannot restore later.

Your next action: open your most recently restored file in Audacity's Spectrogram view. If you see any horizontal gaps or missing energy above 8kHz, delete that processed file and redo the restoration with passes of 6 dB or less. Do not save a file that shows spectral gaps — you have already destroyed information you cannot recover.

Repair Clipped Waveforms

If you see a waveform with flat tops instead of rounded peaks, you have clipped audio, and turning down the gain in post will not fix it. According to iZotope's documentation (as of July 2026), manual gain reduction cannot reconstruct the missing waveform information; you must use a declipping tool such as iZotope RX Declip, which interpolates the lost peaks by analyzing the surrounding signal shape. Clipping occurs when the input signal exceeds 0dBFS at the analog-to-digital converter stage, creating a hard ceiling that shears off the top of the waveform. The result is a harsh, distorted sound that no EQ or compressor can undo because the data is simply gone.

If you recorded at 32-bit float, the situation is different. 32-bit float captures such a wide dynamic range that the peaks are not technically clipped at the capture stage — they are merely distorted by the preamp or source. In that case, you can use a limiter or a soft-clipping plugin to reshape the waveform without losing information. One podcast editor on a production forum notes that declipping works best on speech, where the waveform is relatively simple and the interpolation algorithm can reliably guess the missing peaks. On complex music tracks with dense transients — think cymbal crashes or piano attacks — the same algorithm can introduce watery artifacts or phasey smearing, so listen critically and compare bypassed sections.

For tape recordings, saturation distortion is often part of the intended sound. Tape compression and harmonic saturation are musical artifacts that many engineers preserve deliberately. Do not attempt to "fix" tape warmth with a declipper; you will strip the character and leave the recording sounding sterile. The rule is simple: if the distortion is symmetrical and consistent across the waveform, it is likely clipping and should be repaired. If the distortion is asymmetrical and varies with signal level, it is likely tape saturation and should be left alone.

A concrete next step: open your recording in a spectral editor and zoom in on a section you suspect is clipped. If the waveform shows a flat plateau at the top or bottom of the cycle, apply a declipping tool in passes — start with a moderate setting and increase only if the artifacts remain audible. Compare the processed section against the original using a solo loop. If you hear new artifacts that sound like digital crackle or warbling, undo and reduce the intensity. The goal is to restore the shape, not to erase every trace of the original distortion.

Case Study: 1940s Radio Broadcast

The fastest way to ruin a 1940s radio broadcast is to treat it like a modern podcast recording. The source is almost certainly a single microphone feed that went through a transmitter, a receiver, and a disc cutter, so the frequency response is already a narrow band of midrange energy. The instinct to reach for a broadband noise reduction filter first is exactly backwards. You need to shape the spectrum before you try to clean it, because the noise profile you sample will be contaminated by the hum and the low-frequency rumble if you do it in the wrong order.

Work the problem in layers. Start with the hum, because it is a fixed frequency and easy to remove without touching the voice. If the broadcast was recorded in a region with 50-cycle mains, adjust accordingly. After the hum is gone, sample two seconds of pure silence between sentences and apply the Noise Reduction effect, but keep the reduction modest — a single pass at 12dB or less, with sensitivity around 6. The common failure here is applying one aggressive 24dB pass that turns the voice into a watery, phasey mess. Multiple light passes preserve the transient consonants that make speech intelligible.

Only after the hiss is under control should you touch the equalization. A high-shelf boost starting around 3kHz, typically +3 to +6dB, restores presence to muffled speech. The trap is boosting above 10kHz, which does nothing for intelligibility and only amplifies whatever hiss remains. For a 1940s broadcast, you are not chasing air or brilliance; you are chasing articulation. The difference between a usable restoration and a swirly one is usually this EQ decision, not the noise reduction settings.

If you have the budget, iZotope RX handles the same workflow with more surgical tools. Voice De-noise in Adaptive mode tracks the noise floor in real time instead of applying a static profile, which avoids the global smear that Audacity's Noise Reduction can introduce.

One warning about the AI one-pass tools. Adobe Podcast Enhance and NVIDIA RTX Voice can separate speech from noise in a single click, and they are genuinely impressive on modern recordings. On a 1940s broadcast where the noise floor is close to the voice level, they often remove sibilant consonants and leave a watery, underwater quality that is harder to fix than the original hiss. These tools assume a clean-ish source. They are not restoration tools; they are enhancement tools, and the distinction matters when the source is already degraded.

When you export, the final file should be 16-bit/44.1kHz WAV, which preserves CD-quality while keeping the file size manageable for sharing. According to Audacity's documentation (as of July 2026), this is the standard delivery format for restored audio. Before you share it publicly, check the copyright status. Per Copyright.gov (as of July 2026), recordings published before 1928 are in the public domain. Recordings from 1928 through 1977 may still be under copyright, and republication without permission can create liability even if the physical disc is yours. A 1940s broadcast is almost certainly in that protected window, so keep the restoration for personal use unless you can trace the rights.

Run the full chain on a two-minute test segment before committing to the whole recording. If the speech sounds natural and the hiss is gone, process the rest in batches. If you hear warbling or digital crackle, undo and reduce the reduction amount — do not push through. The difference between a restoration and a destruction is patience, not plugin count.

What to do next

The steps below will help you move from a finished restoration to a properly archived, legally sound file you can share or store for decades.

Also worth reading: Remove Reverb from Audio Recordings with AI · Why Your Podcast Deserves AI Audio Mastering · AI Audio Toolbox vs Paid Plugins: Which Delivers Best Value · How to Get Consistent Audio Across Multiple Takes with AI

Sources: audacityteam, lalal, integraudio, netlify