You have just finished recording a conversation with an elderly relative about their childhood, and the file sits on a laptop alongside dozens of other media. The raw audio is valuable, but the interview will be edited, transcribed, and eventually stored with other family documents. Without a clear process, the original and edited versions can become lost, overwritten, or corrupted, jeopardizing the ability of future generations to access the story exactly as it was told.
Why preserving interview files matters
The workflow addresses the risk of losing both the unaltered recording and the edited version that may contain timestamps, annotations, or selective excerpts. For long‑term family history, the original audio serves as primary evidence, while the edited file provides a curated narrative that is easier to browse. Keeping both ensures that future researchers can verify edits, resolve disputes, and understand the context of any cuts or rearrangements. The practice also aligns with archival standards that call for preserving source material alongside derivatives, reducing the chance that a single corrupted file will erase an entire family memory.
Free and paid tools
A minimal setup can be built from free software: Audacity for audio editing, FFmpeg for format conversion, and a plain‑text editor for notes. Cloud storage services such as Google Drive or Dropbox offer basic versioning and sharing. Paid options add convenience and reliability: Adobe Audition provides non‑destructive editing and integrated metadata fields; Avid Pro Tools offers advanced restoration tools; and dedicated digital‑asset‑management (DAM) systems like Canto or ResourceSpace supply searchable catalogs and automated backups. Choose the combination that matches the volume of interviews and the level of technical support you need, keeping in mind that free tools are sufficient for most family‑history projects.
Step‑by‑step workflow
The process can be broken into a numbered checklist that can be repeated for each interview. 1. Transfer the raw audio from the recorder to a dedicated “Incoming” folder on a local drive. 2. Verify the file plays without gaps; note any audible glitches. 3. Create a duplicate copy named with the interview date and participant’s name, then move the original to a read‑only archive folder. 4. Open the duplicate in Audacity, trim silence, and apply a light noise‑reduction filter if needed. 5. Export the edited version as a lossless WAV file and a compressed MP3 for easy sharing. 6. Generate a plain‑text transcript using a speech‑to‑text service or manual typing, then save it with the same base name. 7. Add a short README file that records the tools used, settings applied, and any decisions made during editing.
The most common mistake
The single most frequent error is overwriting the original recording when saving the edited file. Because many programs default to the same filename, the unedited source can be replaced without warning, eliminating the primary evidence. To avoid this, always work on a copy rather than the original and enforce a naming convention that distinguishes “raw” and “edited” files, such as adding “_raw” or “_edited” suffixes. Enable file‑versioning in the operating system or use a version‑control system that tracks changes, so that a previous state can be restored if an accidental overwrite occurs.
Consistent naming and filing
A clear naming scheme ties the interview files to the broader family archive. Use a fixed pattern: YYYYMMDD_ParticipantName_Role_Raw.wav for the source and YYYYMMDD_ParticipantName_Role_Edited.wav for the edited version. Store both in a folder hierarchy that mirrors the archive’s structure, for example: /FamilyHistory/Interviews/2024/20240315_Jones_Grandfather/. Include the transcript and README in the same folder. Consistency makes it easy for search tools to locate related items and prevents duplicate copies from accumulating under slightly different names.
Quality check and backup
Before deleting the original recorder’s card or archiving the source, run a quick quality‑check: open the raw and edited files in a media player, listen for missing sections, and compare waveform peaks to ensure no clipping occurred during export. Verify that the transcript aligns with the edited audio timestamps. Once satisfied, copy the entire interview folder to at least two separate backup locations: an external hard drive kept in a different physical space and a cloud storage bucket with versioning enabled. Document the backup locations in a master index file so that future users know where to find the preserved copies.
Dealing with damaged or incomplete source
If the recorder’s file is corrupted or missing sections, first attempt a repair with FFmpeg’s error‑recovery flags or Audacity’s “Import Raw Data” option. When repair fails, preserve the damaged file as‑is in a “Damaged” subfolder and note the issue in the README. Supplement the gaps with secondary material such as photographs, written recollections, or other recordings that reference the same event. Clearly label any reconstructed segments as “reconstructed” or “supplemental” to maintain transparency about what is original and what has been added.
Worth remembering: Always keep the original recording untouched, work on a clearly labeled copy, and store both raw and edited files in a consistent folder structure before backing them up in multiple locations.
Common questions
What format or settings should I use?
Save the raw interview as a lossless WAV file at 44.1 kHz, 16‑bit PCM; export the edited version as both WAV for archival quality and MP3 at 192 kbps for sharing.
How should I label the files or items?
Use a fixed pattern that includes the date, participant name, role, and a suffix indicating raw or edited, for example YYYYMMDD_Jones_Grandfather_Raw.wav and YYYYMMDD_Jones_Grandfather_Edited.wav.
How many backup copies should I keep?
Keep at least two independent copies: one on an external drive stored away from the primary computer and another in a cloud service that supports versioning.