Published by PitchChanger · Updated · How these guides are made
How to use this workflow
Identify what the name reveals
Review person names, client names, locations, dates and case identifiers before posting a screenshot or delivering an audio file. A recording can reveal context through its filename even when nobody hears the audio.
Use a private mapping
Assign a neutral project code and keep the code-to-person mapping in your own authorized notes. Preserve enough version information to distinguish revisions. Rename a copy; keep the original source organized separately.
Invented filename redaction examples
These original examples use fictional identities and projects. They illustrate filename minimization, not anonymization of the recording. Renaming does not remove embedded tags, spoken names or a recipient’s earlier copy.
Swipe or scroll sideways to read all columns.
| Invented original | Neutral delivery copy | Information preserved |
|---|---|---|
| Alex_River_therapy_take3.wav | project-Q7_take03.wav | Project and take |
| ClientOrchid_unreleased_chorus.mp3 | project-R2_chorus_v02.mp3 | Section and revision |
| Room12_interview_2026-10-30.wav | session-K4_excerpt01.wav | Session and excerpt |
Verify the result and record its limits
Keep the actual format extension unchanged. Renaming .wav to .mp3 does not convert the audio. Open the renamed copy and check its contents before sharing it. Review metadata separately using the linked metadata workflow; also check screenshots, folder paths and download history for the original name. Decide what your recipient really needs before including dates or locations.
Common questions
Was this example measured on my device?
No. The worksheet and any hypothetical numbers are explicitly labeled. Use a harmless recording to collect your own observations and record the browser, date and exact operation.