File Naming & Version Control | Bounty_OS Docs
Recommended file naming conventions and organizational strategies for managing campaign content files across revisions and platforms.
Address▸
C:\Bounty_OS\Campaign Ops\naming.txt
Campaign Ops ▸ naming.txt
File Naming & Version Control
As you take on more campaigns, your content library grows fast. Without a consistent naming and organization system, you will lose track of revisions, mix up platform edits, and waste time hunting for files. This guide covers the naming conventions and folder structures used by top-performing creators on Bounty_OS.
Naming Convention
Use the following format for all exported content files:
[Campaign]_[Type]_[Platform]_[Version]_[Date].[ext]
Examples:
GlowSerum_Original_TikTok_v1_2026-02-10.mp4
GlowSerum_Original_TikTok_v2_2026-02-15.mp4
GlowSerum_Repurposed_Instagram_v1_2026-02-12.mp4
FitFuel_Original_TikTok_v1_2026-03-01.mp4| Segment | Description | Example |
|---|---|---|
| Campaign | Short campaign or brand name (no spaces, use CamelCase) | GlowSerum |
| Type | Original or Repurposed | Original |
| Platform | Target social platform | TikTok, Instagram |
| Version | Revision number starting at v1 | v2 |
| Date | Export date in YYYY-MM-DD format | 2026-02-15 |
| Extension | File format | .mp4, .mov, .jpg |
Folder Structure
Organize your local and cloud storage by campaign, with subfolders for status and asset type:
Bounty_OS/
├── Active_Campaigns/
│ ├── GlowSerum_Feb2026/
│ │ ├── Raw_Footage/
│ │ ├── Exports/
│ │ │ ├── TikTok/
│ │ │ └── Instagram/
│ │ ├── Thumbnails/
│ │ └── Brief_Notes.txt
│ └── FitFuel_Mar2026/
│ ├── Raw_Footage/
│ └── Exports/
└── Completed_Campaigns/
└── AquaGlow_Jan2026/
├── Raw_Footage/
└── Exports/Why Versioning Matters
- Track revisions after rejection — When a post is rejected and you need to fix it, increment the version number (v1 → v2). This lets you compare what changed and reference specific versions if support asks.
- Resubmission history — Keeping every version means you have a complete audit trail. If a brand disputes your content, you can prove what was submitted and when.
- Rollback capability — Sometimes v1 was actually better. Having all versions gives you options.
- Multi-creator households — If multiple people use the same workstation, clear naming prevents accidental overwrites.
Cloud Backup Strategy
Never Rely on Local Storage Alone
Hard drives fail, laptops get stolen, and phones break. Always maintain a cloud backup of both your raw footage and exported files. Lost footage means you cannot revise rejected content, potentially forfeiting earnings from the entire campaign.
- Google Drive — 15 GB free, integrates well with mobile workflows. Use the desktop sync client for automatic backups.
- Dropbox — 2 GB free, excellent for sharing files during pre-approval workflows.
- iCloud — Seamless for iPhone creators. Enable "Optimize Mac Storage" to manage space.
- External SSD — Keep a quarterly archive of completed campaign raw footage on a portable drive as a secondary backup.
Multi-Platform Variants
When a campaign targets multiple platforms, always save platform-specific edits as separate files. TikTok and Instagram have different aspect ratio preferences, caption overlays, and audio licensing. Never assume a single export works for both. Use the platform segment in your file name to distinguish them (e.g., _TikTok_ vs _Instagram_).
Related topics: Revision Protocol (revision-protocol), Content Batching (content-batching).
41 objectsUpdated 2026-02-10