Once you start generating TTS audio regularly — for voiceovers, proofreading, content repurposing, or personal projects — the files accumulate quickly. A script that produces 20 audio clips becomes 20 files. A chapter-by-chapter audiobook generates hundreds. Multiply by multiple projects and the collection becomes hard to navigate.
Without organization, you waste time searching for the right file, regenerating lost clips, and struggling to remember which voice and settings you used for a specific project.
This guide covers a practical system for organizing your TTS library on Mac: folder structure, naming conventions, voice preset management, project metadata, and archiving.
The Problem with Default Names
Most TTS apps generate files with names like output-001.mp3 or Spokio_Export_20260517_143022.wav. These names carry no information about the content. Six months later, you cannot tell which project a file belongs to, what it contains, or which voice generated it.
A naming convention solves this problem at the point of creation.
Folder Structure
By Project
The simplest structure groups files by project:
tts-library/
├── video-voiceovers/
│ ├── product-launch/
│ │ ├── script.txt
│ │ ├── narration-full.wav
│ │ └── clips/
│ └── tutorial-series/
│ ├── episode-1/
│ └── episode-2/
├── audiobooks/
│ ├── project-alpha/
│ │ ├── manuscript/
│ │ ├── audio/
│ │ └── manifest.json
│ └── project-beta/
├── blog-podcast/
│ ├── 2026-05/
│ ├── 2026-06/
│ └── rss-feed.xml
└── personal/
├── meditation-scripts/
└── journal-audio/Each project folder contains the source text, the exported audio, and any metadata or notes. Separate folders keep unrelated content from mixing.
By Voice
If you use the same voices across projects, store presets and voice profiles separately:
tts-library/
└── voices/
├── default-narrator.txt # Voice settings, speed, pitch
├── warm-narrator.txt
├── podcast-voice.txt
└── voice-clones/
├── brand-voice-sample.wav
└── brand-voice-notes.txtVoice profile notes should capture: which TTS app or model generated them, the voice preset name, any speed or pitch adjustments, and the source model version.
Naming Convention
Files
A consistent naming pattern makes files identifiable at a glance:
{project}-{content}-{voice}-{date}.{ext}Examples:
product-launch-script-1-narrator-20260517.wavtutorial-ep1-intro-warm-voice-20260517.mp3chapter-12-final-narrator-20260517.wav
Include enough information to identify the file without opening it. The three critical elements: what project it belongs to, what content it contains, and which voice generated it.
Folders
Use year-prefixed naming for time-based projects:
2026-05-product-launch/
2026-06-tutorial-series/This keeps folders sorted chronologically in the filesystem and makes it easy to find projects by timeframe.
Managing Voice Presets
If your TTS app supports multiple voice presets or configurations, document them. A text file per voice captures:
Voice: Narrator
App: Spokio
Model: Chatterbox Turbo
Speed: 1.0
Notes: Default narration, clear and neutral
Voice: Warm Narrator
App: Spokio
Model: Chatterbox Turbo
Speed: 0.9
Notes: Slightly slower, used for meditation and reflective contentStore these in a voices/ folder within your TTS library. When you start a new project, copy the relevant voice preset file into the project folder as a reference.
Project Metadata
For complex projects (audiobooks, multi-episode series, multilingual dubs), a manifest file tracks the full project state:
{
"project": "Project Name",
"voice": "default-narrator",
"created": "2026-05-17",
"source": "source-text/manuscript.md",
"chapters": [
{"id": "01", "title": "Introduction", "source": "manuscript/01-intro.md", "audio": "audio/01-intro.wav", "status": "done"},
{"id": "02", "title": "Getting Started", "source": "manuscript/02-start.md", "audio": "audio/02-start.wav", "status": "done"}
]
}For simpler projects, a notes.txt file in the project folder is sufficient:
Project: Product Launch Video
Voice: Narrator
Generated: 2026-05-17
Source: script-v3.txt
Output: narration-final.wav
Duration: 4:32Version Tracking
Scripts change. Voice settings change. Export formats change. Track versions without clutter.
Source Text Versioning
Keep the version of the source text that was used to generate each audio file. Name convention:
script-v1.txt → narration-v1.wav
script-v2.txt → narration-v2.wavWhen the script is finalized, archive the final version alongside the final audio.
Audio Iterations
Label iterations with the generation date rather than version numbers for quick identification:
narration-20260517.wav # First generation
narration-20260518.wav # Second generation after edits
narration-20260518b.wav # Third generation, same dayWhen a final version is approved, copy it to a stable name like narration-final.wav so downstream references always point to the current approved file.
Archiving Finished Projects
When a project is complete, move it to an archive:
tts-library/
├── active/
│ ├── current-project/
│ └── wip-episode/
└── archived/
├── 2025/
├── 2026-01-completed-project/
└── 2026-02-another-project/The active folder contains projects you are currently working on. The archived folder stores completed projects. This keeps your active workspace focused and your archive searchable by year.
What to Archive
For each completed project, keep:
- Final audio file(s)
- The source text that generated them
- Voice preset notes
- Any metadata or manifest files
Discard intermediate audio files (early iterations, test generations, failed exports). They consume space and add noise to the archive.
File Formats and Storage
Working Files
Use lossless formats (WAV, AIFF) during production. They preserve quality through edits and are the safest intermediate format.
Distribution Files
Convert to compressed formats (MP3, AAC) only at the final export stage. Keep the lossless original in your archive as the master.
Storage Estimates
- 1 hour of audio at WAV (48kHz, 24-bit): approximately 1.5 GB
- 1 hour of audio at MP3 (192kbps): approximately 85 MB
For active projects, store WAV files. For the archive, WAV for masters and MP3 for quick access.
Spokio for Library Management
Spokio supports the library organization workflow. It runs on Apple Silicon and Intel Macs, exports to multiple formats (MP3, WAV, AIFF, M4A), and supports batch export for processing multiple files with consistent settings.
Because Spokio generates audio locally, your organized library stays on your machine — no cloud uploads, no sync conflicts with external services, and no dependency on a cloud provider’s file organization system.
The most important organizational habit is the simplest one: name your files intentionally before you save them. A few extra seconds at generation time saves minutes of searching later.
