The Version field is used to differentiate between various iterations of a release—such as remastered editions, deluxe versions, or live recordings. Digital Service Providers (DSPs), particularly Apple Music, require that this field follows strict formatting and content standards to ensure consistency across platforms.
Following these guidelines helps prevent delays, rejections, or metadata conflicts during distribution.
📌 General Guidelines
- The Version field should only include clear, descriptive terms that reflect real differences in the audio content or track listing from the original release.
- Must be enclosed in parentheses.
- Should match the audio content and appear exactly as listed in the metadata.
- Avoid marketing language unless it accurately reflects a unique version.
✅ Acceptable Version Field Examples
🔊 Audio Format or Quality
- (Remastered)
- (Remastered 2024)
- (Mono)
- (Stereo)
- (High-Resolution Audio)
🎼 Content Variations
- (Deluxe)
- (Expanded Edition)
- (Bonus Track Version)
- (Instrumental)
- (Acoustic)
- (Live)
- (Studio Version)
- (Radio Edit)
- (Extended Version)
- (Clean)
- (Explicit)
🌍 Language or Region
- (English Version)
- (Spanish Version)
- (Japanese Edition)
- (International Version)
🎤 Performance Type
- (Orchestral Version)
- (Piano Version)
- (Unplugged)
🎬 Album-Specific Identifiers
- (Original Motion Picture Soundtrack)
- (Music from the Series "XYZ")
- (Broadway Cast Recording)
- (Live at Madison Square Garden)
🚫 Unacceptable Version Fields
Do not use the Version field for:
- Marketing language without an actual content difference (e.g., “Collector’s Edition,” “Special Release”)
- Redundant information already provided elsewhere in the metadata (e.g., “Clean” in both title and version field)
- Generic or unclear descriptors that don’t reflect a change in audio or structure
Following these standards ensures a smooth delivery process and keeps your releases compliant with Apple Music and other DSP requirements.