
File Naming
Overview
It’s important that every file is named to our specifications - this ensures that they are optimized for our tagging and search algorithms and will make it easy for users to find your sounds. Files not named according to our requirements run the risk of being misclassified or generating incorrect metadata which negatively impacts the searchability, discoverability and overall user experience. For real-world examples of finished packs, please see the Example Packs section.
File Names Must Be Unique
We require that all files have descriptive and unique names. Files that aren't named descriptively (snare_01.wav, snare_02.wav) aren't very memorable and don't perform as well. These names should be colorful and on-brand - usually an object, a place, a time, a feeling, or a literal description of the sound. Numbers should only be included in names to indicate BPM.
To illustrate,
ARTIST_808_01.wav could be ARTIST_808_gritty_E.wav
ARTIST_808_02.wav could be ARTIST_808_brooklyn_C.wav
ARTIST_808_03.wav could be ARTIST_808_shiner_A#.wav
Splice will not publish files with names that make reference to existing entities including but not limited to third party producers, artists, collectives, brands, associations, products, celebrities, trademarks, etc. The term “rhodes” for instance should be changed to “electric_piano”.
Characters
Supported Characters:
All Standard English Characters ( A-Z & a-z )
Numbers ( 0-9 )
Underscores ( _ )
Dashes ( - ) (used for time signatures outside of 4/4)*
Hash Symbols ( # )
Unsupported Characters:
Blank Spaces ( )
Special characters not listed above ( !@£$%^&*()+={}:"|;'|\/?><,.~±§`— )
Accented Characters ( å é ü ø )
Slashes ( / \ )
File Names - Audio
The table above shows example file names that follow our file naming conventions, and explains the various components that make up a full file name. If written out more simply, the files would like this:
SM_NP_100_electric_guitar_baby_Dmaj.wav
FF_MT_90_pad_angel_Cmin.wav
WMN_RC_snare_fat.wav
TC_BW_120_percussion_grimey.wav
X10_UKG_808_deep_C.wav
SC_BPS_85_synth_ripper_Fmaj.wav
Notice how the phrases “loop” or “one shot” do not need to appear in the file. We identify them by folder structure as well as tempos.
Descriptors
Adding descriptors to the names of samples can really enhance the experience for Splice users as well as make your sounds more searchable.
Though SM_DP_90_electric_guitar_angel_Dmin.wav is correct. SM_DP_90_electric_guitar_strum_angel_Dmin.wav is more descriptive.
Here are some more examples
SM_DP_kick_coldcut -> SM_DP_kick_dusty_coldcut
MG_OP_70_synth_cosmic_Amaj -> MG_OP_70_synth_chords_cosmic_Amaj
VOX_PV_80_vocal_fire_Fmaj -> VOX_PV_80_vocal_fire_wet_Fmaj
When adding descriptors consider what makes sense to the user. Descriptors like arp, melody, strum, pluck, chords, make sense after the instrument category ( synth, piano, electric_guitar, drum). Wet or Alt however can go at the end of the name before the keytag. This implies multiple versions. With vocal loops specifically it is common to have a wet and dry version of the loops.
Naming Stems
Drum Loops, Melodic Loops, and Songstarters can often have multiple stems attached to the “full” file. Below are some examples of one would name them.
Drum Loop Naming
SM_DP_90_drum_rocker.wav (this would be the mixed version of all the stems below)
SM_DP_90_kick_rocker.wav
SM_DP_90_snare_rocker.wav
SM_DP_90_hat_rocker.wav
SM_DP_90_percussion_rocker.wav
Melodic Loop Naming
FF_MT_100_melodic_silk_Cmaj.wav (this would be the mixed version of all the stems below)
FF_MT_100_electric_guitar_silk_Cmaj.wav
FF_MT_100_synth_lead_silk_Cmaj.wav
FF_MT_100_piano_silk_Cmaj.wav
Songstarter Loop Naming
X10_UKG_140_songstarter_fresh_Dmin.wav (this would be the mixed version of all the stems below)
X10_UKG_140_808_fresh_Dmin.wav
X10_UKG_140_synth_bass_fresh_Dmin.wav
X10_UKG_140_vocal_fresh_Dmin.wav
X10_UKG_140_electric_piano_fresh_Dmin.wav
File Names - Midi
The table above shows example file names that follow our file naming conventions, and explains the various components that make up a full file name. If written out more simply, the files would like this:
X10_FG_120_bass_heavy_Cmin.mid
FF_DS_90_arp_angel_Dmaj.mid
SM_DP_117_chords_grandpa_Fmin.mid
SO_SW_100_drums_pristine.mid
WMN_GP_75_melody_beauty_Dmin.mid
PLX_AA_140_chords_power_Gmaj.mid
When adding midi to your pack be sure the midi itself is useful. For example, a single sustained note over 4 bars may not be useful where as unique chords or a written out arp would be very desirable.
Each midi file requires an mp3 preview normalized to -1db. Please make sure the preview name and midi name match exactly with the exception of the .mid/.mp3 extensions.
File Names - Presets
The table above shows example file names that follow our file naming conventions, and explains the various components that make up a full file name. If written out more simply, the files would like this:
SM_NP_808_heavy
FF_RS_keys_beauty
X10_CRS_chord_minimal
SC_LO_pad_darling
Each preset file requires an mp3 preview normalized to -1db. Please make sure the preview name and preset name match exactly with the exception of the extensions.
Most sounds will be either a one shot, a loop, or a fill.
You do not need to include the words “one shot”, “loop”, or “fill” in a file name. We express which is which by having tempo added in addition to if it is in a “loop” folder or “one-shot” folder.
Your artist (or label) name and pack prefix go right at the front of the file name in CAPS. Everything else is lowercase.
There are no blank spaces allowed in the file names - always use an underscore (_) to separate the various elements.
Every periodic file with a rhythm - think loops, fills, and any one shots with a delay effect - gets a TEMPO (BPM). This goes right after the artist name and pack code.
Every tonal file - (anything that has notes) like a bass one shot or melodic loop - gets either a ROOT NOTE or a full KEY SIGNATURE.
Though we do allow alternate versions, we discourage from filling the pack with too many versions of the same loop or one-shot. If you would like to make an alternate version, please use a descriptor to express the difference IE wet, dry, distorted.