Version Control & History
Automatic version tracking, restore previous states, compare changes, and maintain complete project history
Coming Soon
Version Control is currently under development and will be available soon. This documentation provides a preview of the features that will be included.
Overview
Wubble automatically tracks every change made to your projects, creating a complete version history that allows you to restore previous states, compare different versions, and understand how your work evolved over time. Never worry about losing work or making irreversible changes—every edit is safely preserved.
Unlike traditional file-based backups, Wubble's version control is intelligent, space-efficient, and integrated directly into your workflow. No manual saving required—versions are created automatically at key moments and can be labeled for easy reference.
Version Control Features
How Version Control Works
Wubble intelligently creates versions automatically while keeping storage efficient and performance fast. Understanding when and how versions are created helps you work confidently.
Automatic Version Creation
Versions are automatically created when significant changes occur:
- • Audio regeneration or upload
- • Major mixing or processing changes
- • Track addition/removal in mixes
- • Restore from previous version (creates checkpoint)
- • Manual save point creation (on demand)
- • Before sharing with collaborators
Incremental Storage
Wubble stores only changes (deltas) between versions, not complete duplicates. This means unlimited version history without proportional storage growth. Space-efficient and cost-effective.
Smart Deduplication
If you restore a version and then restore back, Wubble recognizes the content and doesn't create redundant storage. Only unique states consume space.
Version Metadata Tracking
Each version includes comprehensive metadata: who created it, when, what changed, audio metrics (duration, loudness, quality), and user-provided descriptions.
Restoring Versions
Restore any previous version with one click. Wubble makes reverting changes safe and easy, removing fear of experimentation and mistakes.
Open Version History
Click the version history icon in project interface to see chronological list of all versions
Preview Previous Version
Click any version to preview it. Listen to the audio, view settings, and see what changed without affecting current state
Restore (with Backup)
Click "Restore This Version" to revert. Wubble automatically backs up current state before restoring, so you can undo the restore if needed
Verify Restoration
Restored version becomes current. Review to ensure it's what you wanted. If not, restore to the pre-restore backup
Restoration Safety
Restoring a version always creates a backup of the current state first. This means restoration is never destructive—you can always get back to where you were. Experiment freely!
Comparing Versions
Understand exactly what changed between versions with detailed comparison tools. Visual diffs, audio playback side-by-side, and highlighted changes make tracking evolution clear.
Settings Comparison
See exactly which settings changed: volume levels, effects parameters, mixing configurations, metadata updates. Changes are highlighted with before/after values.
Audio Comparison
Listen to both versions side-by-side or generate a difference file highlighting what changed sonically. Waveform visualizations show changes visually.
Metrics Comparison
Compare technical metrics: loudness (LUFS), duration, file size, quality scores, frequency balance. Understand objective changes between versions.
Change Description
Each version includes automatic description of what changed plus any manual notes added by editors. Understand not just what changed, but why.
Version Labels
Add custom labels to important versions for easy identification. Labels act as bookmarks in your version history, making it simple to find significant milestones.
Common Label Uses
Standard labels help organize project history:
- • Final Master: Production-ready version
- • Client Approved: Version client signed off on
- • Review v1, v2, v3: Versions sent for review
- • Before Major Change: Checkpoint before experiments
- • Milestone: Significant progress points
- • Platform-Specific: Instagram version, TikTok version, etc.
Color Coding
Assign colors to labels for visual organization: green for approved, red for rejected, blue for review, yellow for work-in-progress. Scan history at a glance.
Pinned Versions
Pin important versions to top of version list for instant access. Final masters, approved versions, or frequently-referenced states stay easily accessible.
Team Label Standards
Establish team-wide labeling conventions for consistency. When everyone uses the same labels, navigating any project's history becomes intuitive.
Version Management
While Wubble manages versions automatically, you have full control over how they're organized, stored, and accessed.
Download Specific Versions
Export any version as standalone audio file. Perfect for archiving approved versions, sharing specific iterations with clients, or maintaining offline backups.
Version Retention
All versions are retained indefinitely by default. For projects with extremely long histories, you can optionally archive old versions after specified time periods.
Search Version History
Search versions by label, date range, creator, or change description. Find specific versions in projects with extensive histories quickly.
Version in Collaboration
All collaborators see the same version history. Activity log shows who created each version and why, maintaining transparency across the team.
Version-Specific Sharing
Share specific versions with collaborators instead of always showing the latest. Useful for client reviews of specific iterations or comparing options.
Best Practices
Label Important Milestones
Immediately label versions when they represent important states: client approvals, final masters, major milestones. Labeled versions are much easier to find later.
Create Checkpoints Before Experiments
Before trying major changes or risky experiments, manually create a labeled version as a checkpoint. Makes returning to known-good state instant if experiment doesn't work.
Add Descriptive Notes
When creating manual versions, add clear descriptions of what changed and why. Future you (and collaborators) will appreciate context when reviewing history.
Compare Before Major Changes
Before sending to client or publishing, compare current version with previous approved version. Ensures all requested changes were made and nothing unexpected changed.
Use Version History for Learning
Review version history of successful projects to understand what worked. Trace how rough drafts evolved into polished finals. Learn from your own process.
Download Approved Versions
When clients approve versions, download and archive externally. Provides additional backup and proof of approval if disputes arise later.
Don't Fear Making Changes
Version control means experimentation is safe. Try different approaches without anxiety—you can always restore if something doesn't work. This freedom improves creativity.
Review Version History Periodically
Occasionally review old versions to see project evolution. Identify patterns in your workflow, see what kinds of changes you make most, refine your process.
Use Consistent Label Names
Develop personal or team conventions for label names. Consistency across projects makes navigation intuitive and searching more effective.
Educate Collaborators
Ensure all team members understand version control. Knowing they can safely restore previous versions reduces anxiety and enables bolder creative decisions.