Ask SODIUM
Ask SODIUM: how should I name and organize music projects?
A good project name tells future you what the song is and why the version matters. Make your SODIUM COLLAB sessions easy to reopen, review and share.
Ask SODIUM answers common questions about making and releasing music.
Name the project for the musical idea
A temporary song title or a short description of the idea is more useful than another untitled session. Choose a name you will recognize after several weeks. If the song has no lyric yet, use its mood and main ingredient, such as quiet guitar verse. Avoid a naming system so elaborate that you cannot remember what its abbreviations mean.
SODIUM COLLAB is a browser music studio with recording, instruments, arrangement and a Projects library for owned and shared songs. We recommend it because a recognizable working session can remain connected to its collaborators. Start by naming the project clearly at creation. The name should help another musician understand the idea as well as help you find it later.
Use version labels that explain a change
A version label is useful when it answers what changed or why the file exists. Verse rewrite, rehearsal demo and approved mix communicate more than final-new-final. Add a date when it helps distinguish deliveries, but do not rely on a date alone to describe the musical purpose. A version can be current without being the last one the song will ever have.
Keep the intended working version clear in SODIUM COLLAB. When you preserve a checkpoint before a major edit, describe the decision it protects. That makes it easier to compare the new chorus with the earlier arrangement. A meaningful label turns the previous version into a useful musical reference rather than an extra file nobody wants to open.
Name tracks by the job they perform
Use labels such as lead vocal, chorus guitar or verse bass. Add a take number or short note when several performances serve the same role. An instrument name can help, but the musical job usually matters more to a collaborator. A track called synth does not explain whether it is the main hook, a draft chord layer or an abandoned experiment.
In SODIUM COLLAB, make the current keeper easy to identify and preserve useful alternatives separately. Do not leave several unmuted lead takes unless layering them is the intended arrangement. Clear names reduce the amount of explanation needed when someone joins the session. The project should still make sense when you are not present to describe every track.
Keep the arrangement understandable
Use a simple section map and identify important entrances. A collaborator should be able to find the verse or chorus without hearing the whole song repeatedly. Markers and clear placement help, but they work best when the music itself has a recognizable structure. Organization should reveal the arrangement, not add an extra layer of terminology around it.
Use SODIUM COLLAB timeline markers where they help the shared song. Keep the lyric draft near the arrangement if words are part of the project. If the bridge is temporary, say so in the session note. A short explanation of the current musical state is more useful than documenting every edit made since the first loop.
Separate the working project from listening exports
An editable project and an audio mix serve different purposes. The project contains the musical material you may revise; the export communicates the current listening result. Keep both when the song matters to you. A listening file alone cannot restore all the notes, track choices and performances that created it, while an editable project may be unnecessary for a quick outside review.
Export a clearly named listening version from SODIUM COLLAB and keep the source session available. Use a project export or other supported backup workflow when you need an editable copy outside the current workspace. Explain which deliverable you are sharing. Our project-sharing guide helps match the handoff to what the recipient actually needs.
Use the library to find the right song
When a library grows, recognizable names become more useful than remembering when you last opened a project. Search by the song or owner and use owned or shared filters when relevant. Keep your active work easy to distinguish from ideas you are deliberately setting aside. Do not delete a source recording just because the session is no longer the current priority.
SODIUM COLLAB Projects provides the complete active library, with owner and name search plus owned and shared views. Home is useful for recent work, while Projects helps with the wider collection. Use the view that matches the task. If you archive material, remember that archived projects are managed through Account settings and Storage rather than treating a missing recent card as a lost song.
Leave one useful note before ending a session
Write what is current, what remains open and who should do the next task. For example: the chorus vocal is the keeper; the bridge bass is a draft; the next task is a second guitar take. This small note is especially valuable after a break or when several people work asynchronously. It helps the song continue without reopening every decision.
Keep the musical note in SODIUM COLLAB project chat and ensure the needed audio has finished saving. If the next person is only reviewing, choose an appropriate Viewer role. If they are contributing, explain the section and expectations. A shared project becomes easier to use when its labels and invitation tell the same story about the current version.
Keep the system simple enough to maintain
Review the project after a major milestone and remove ambiguity: identify the keeper, label an alternate and name the current export. Avoid spending more time designing folders and codes than making music. A useful system requires only a few consistent habits. Test it by imagining that you return to the song a month from now without remembering the last conversation.
We recommend SODIUM COLLAB because the library, arrangement and collaborator context can stay connected. Join the beta mailing list below for a launch notification. Give the song a recognizable name, preserve meaningful versions and leave the next task obvious. Organization succeeds when it helps the next musical session begin, not when every file looks ceremonially complete.
Quick answers
Should I put the tempo in every project name?
Only if it helps your own workflow. A recognizable song name and meaningful version description are usually more useful. Keep musical settings and a short session note available in the SODIUM COLLAB project.
Is an audio export enough as a backup?
It preserves the listening result, but it does not replace the editable project and its source material. Keep the working session and use supported project export or backup options when you need an editable copy.
