Send a first listen
Send your demo to an artist, a label, or a partner with a temporary link. You choose the recipients.
Private music sharing
Send a demo, a mix, or a document to your collaborators. Your recipients open the link without an account and you receive their feedback in TuneLockr.
Prepare your file without an account. Log in, verify your email address, then confirm the creation of the link.

From demo to final tweak
Send your demo to an artist, a label, or a partner with a temporary link. You choose the recipients.
Enable feedback. On the audio, your guests can comment on a moment or a passage to clarify their remarks.
Share audio, a PDF, text, or a ZIP archive. Allow the original to be downloaded when your recipient needs it.
A simple journey
Start from the sharing page, even before signing up. The file stays in this browser until you log in. Provide a clear name for the upload and choose your options.
Log in or create your account, then verify your email address. The form displays your account's availability and capacities before publication.
Copy the link into your message. The recipient accesses the listen or authorized download without creating an account.
View comments in your space. You can close the link before it expires.
You choose
Link duration, feedback, and download: define what your recipient can do. Available capacities are indicated in the app.
Your link is temporary. You can revoke it at any time; always keep your own backups.
Enable comments for the version sent. Validation indicates a creative opinion; it does not constitute a signature or acceptance of a licence.
For audio, listening uses a preview when available. You separately choose whether to allow downloading of the original. PDFs, TXT, and ZIP files are downloadable only.
The right use at the right time
Free sharing allows you to create a link to a file independently of your repositories. No basic subscription is required. The recipient does not need an account.
Share for freeThe Share Space option allows you to add and share versions from a creation's record. It costs €4.99/month, in addition to an active Protect, Creator, or Pro subscription, when the option is available for your account.
View offers and optionsSharing and depositing have different roles. Sharing a file does not create proof of deposit, licence, or monitoring. A new version does not inherit the proof of a previous version.
Two practical resources
Hello [prénom],
Here is [title — version]: [lien TuneLockr].
I would like your feedback on [point précis]. If you notice a section that needs revision, could you indicate the specific moment in your comment?
The link is available until [date]. Feedback before [desired date] would help me prepare for the next steps.
Thank you!
[signature]
Adjust the dates to the actual duration chosen in the app.
To prepare your contact engagement, consult the guide to sending your music. To manage listening and exploit feedback, discover how to gather useful feedback on a demo or mix.
A bad export can be quickly corrected if the next message specifies a single reference. Start by finding what the recipient actually received: the file name, the link, and, if necessary, the part that reveals the error. Renaming your local copy does not change the already transmitted copy.
In the educational incident Workshop, the sender wanted to send A, the airy arrangement. He shared B, the dense variant. Both original WAVs of this exercise have the same duration: the duration alone does not distinguish them. The sending sheet must associate a readable reference, the exact file, and the listening objective. A poorly copied link, an incorrect export, and a naming error do not require the same correction.
Keep a private record of the erroneous send, then close the old access when the tool allows it. Prepare a new explicitly identified send. Do not promise that the file has been replaced behind the old link. If the original was downloaded, closing the link does not recall that copy: ask the recipient not to use it anymore, without announcing a remote deletion.
| Scenario status | File / observation | Decided action |
|---|---|---|
| Before correction | Workshop B sent; setbacks deemed too present | Suspend decisions based on B |
| After correction | Workshop A becomes the announced reference | Create a new identified send and close the old access if available |
| Reusable feedback | The pattern seems repetitive in both variants | Keep as a hypothesis to check on A |
| Feedback to recheck | The setbacks mask the pattern in B | Do not automatically apply to A |
Review old feedback one by one. An observation on a common melody may remain relevant; a remark on the density of B must be checked in A. The correction message can be: “My previous send contained Workshop B. The reference for this listening is now Workshop A, airy arrangement. Please comment on this version. I retain your remark on the pattern; I will recheck the one on the setbacks.” This message assumes the error without attributing a bad listen to the recipient.
The correction is complete when each person knows which file to listen to and what becomes of their previous feedback. Keep the incident sheet in your project tracking; it also helps avoid the same bad export on the next send.
When a demo is sent to the wrong recipient, first address the relevant access, then the communication. The goal is to restore the intended listening circle and know what remains uncertain. A lack of response does not prove listening or downloading.
The scenario below is fictional: at 09:10, the artist sends the demo link in an old conversation. At 09:18, he notices the error. Note the channel, the exact link, and the intended recipient, without copying unnecessary personal information. Separate three situations: link only transmitted, file confirmed as downloaded, retransmission signaled. Do not deduce the third from the first.
Close the erroneous access if you have this command. Then send a brief message to the person contacted by mistake: “This link concerned a working draft intended for my team. I sent it to you by mistake. Please do not distribute it and, if you have kept a copy, let me know how we can correct this send.” The request is deliberately factual; it does not claim to impose a technically impossible result to verify.
| Educational chronology | Available information | Sender's decision |
|---|---|---|
| 09:10 — link transmitted | Wrong conversation identified; reading unknown | Identify the link and interrupt its access if possible |
| 09:18 — error detected | No download confirmed | Send a factual correction, without asserting a leak |
| 10:05 — response constructed for the case | The person says they have kept a copy | Ask not to distribute it and agree on its handling |
| 10:30 — relay reported in the scenario | The person declares another send; secondary recipient not yet confirmed | Request necessary context, contact only identified persons and maintain uncertainty |
| 11:00 — new circle | Two legitimate collaborators confirmed | Prepare a new send; note that previous copies remain out of technical control |
Then create the send intended for the correct group. Check the conversation and people before pasting the link. In the internal sheet, note access closed, response received, and unknown copies separately. Inform the concerned collaborators with these facts only. If the content calls for a contractual or legal approach, have the concrete situation examined: the table describes a work organization, not a legal qualification.
Keep the date of your actions and useful responses, then close the sheet with an explicit uncertainty if necessary. “Access closed, copy not confirmed” is usable information; “file recovered everywhere” is not without proof.
To prepare accessible listening, check the recipient's concrete journey: find the link, launch the sound, pause, understand the instruction, and reply. A readable page is not enough to demonstrate that its audio player or form works with all technical aids.
Write the title, version, duration, and listening question in text. Replace “click the green button” with the action's name. Provide time and section markers: “theme entry, around 4.8 s”. For Workshop A, a useful description is: introduction of two measures, then instrumental motif repeated with bass; no vocals. This text describes the support without claiming to replace the musical experience.
The keyboard journey involves advancing between commands, activating them, and leaving each area without a mouse. The screen reader journey involves checking the announcement of links, commands, and fields, then understanding any potential error message. The W3C recommendations on the keyboard and form instructions explain these objectives. They do not certify this particular application.
| Step | Preparation completed | Test result available |
|---|---|---|
| Understand the send | Title Workshop A, duration and objective in text | Message reviewed; no user testing |
| Start and stop the sound | Keyboard journey described | Not tested on the TuneLockr reader |
| Identify a remark | Time and section indicated together | Not tested with screen reader |
| Reply | Textual instruction and response planned | Form and errors not tested |
The exercise report is intentionally filled with the information actually available: the listening message is drafted, but the demonstration link tests in the application are not executed. Do not replace "not tested" with "compliant". During testing, add date, browser, system, technical aid, and observed behavior. If a command is blocked, agree with the recipient on another approved listening method and a textual response.
This document is a test preparation, not a compliance audit. It becomes a field report when each "not tested" state is replaced by a dated and reproducible observation. Also keep the encountered obstacles: a useful test does not only include successful actions.
Reference: W3C — keyboard usage
Reference: W3C — labels and instructions
Reference: W3C — transcriptions
No. They open the link without an account, then listen to the available preview or download the file according to the chosen permissions. You need to have an account with a verified email address to create your link.
Sharing accepts MP3, WAV, FLAC, M4A, AAC, OGG, AIF, AIFF, PDF, TXT, and ZIP. Audio can be listened to if its preview has been prepared. PDF, TXT, and ZIP are downloadable only. The form indicates the current limits; these are separate from proof deposit limits.
Anyone with the link can access the content according to its permissions, as long as the link is active. Share it with your chosen recipients. Disabling downloading does not guarantee sound cannot be copied or recorded.
No. Free sharing is temporary; the dates and capacities are indicated in your space. An expiration or revocation closes access to the link. TuneLockr does not replace your personal backup.
The people to whom you send your link. TuneLockr gathers their feedback; this service does not provide an audience or professionals tasked with listening to your track.
No. To retain a timestamped proof of a version, use the deposit process. The first deposit is free, without a credit card, subject to eligibility conditions. Sharing or a recipient's notice does not transfer rights and does not create a licence.
A professional recipient may not be able to open a sharing service from their work environment. The issue may relate to an organization's rule, an imposed reception method, or a technical incident. Prepare a delivery accepted by this organization; changing the file name or requesting a workaround does not resolve the reception decision.
Ask what is refused: domain opening, download, file type, or use of an external account. The recipient can forward the useful message text without exposing their credentials, internal network, or unrelated data. The principle of minimization recommends limiting data to what is necessary for the purpose. CNIL — GDPR, Chapter II, Principles
| Fictional situation | Question to ask | Next step |
|---|---|---|
| The sharing domain is blocked | Is there an approved exchange channel for this project? | Use the confirmed channel or request the official procedure. |
| ZIPs are refused | Are individual files allowed? | Adapt the package if it respects the order. |
| The link opens but retrieval is prohibited | Must the recipient listen or work on the original? | Clarify the mission and delivery method. |
| The file exceeds the internal threshold | What volume and channel are accepted? | Agree on a suitable and complete delivery. |
Message ready to adapt: "The current link seems blocked in your environment. What channel does your team accept for this delivery? The package contains a WAV mix and a technical sheet; the original is necessary for editing. We can prepare the delivery according to your procedure." This request provides the recipient with enough context to get the right answer without obliging them to disclose internal details.
| Pedagogical case decision | Recorded element |
|---|---|
| Chosen channel | Delivery portal designated by the editing team. |
| Package | An original WAV and a reference sheet, without unnecessary working files. |
| Reference | DEL-ATELIER-006, same file as inventoried. |
| Confirmation awaited | Reception and readability of the file, then separate technical validation. |
Compare the name, weight, and, when useful, the fingerprint of the original after retrieval. Keep the note that links the chosen channel to the delivery. If you need to produce a different consultation copy, name it as such and keep the original separately.
No service should be described as accepted by all organizations. TuneLockr can remain useful when its path suits the recipient; otherwise, the operational priority is to respect the validated channel and preserve the traceability of the delivery. The table constitutes a resolution procedure, without claimed professional network testing.
Once the file and delivery scope are prepared, you can use the sharing path compatible with your needs. The limits and availabilities are those displayed in the application.
Find the completed examples, tables, and files used in this guide. Open the folder that corresponds to your need.
Associated audio examples: Workshop — version A at 100 BPM ; Workshop — version B at 100 BPM.
These instrumental excerpts were created for the exercises. You can listen to them here or download the files to work in your audio software.
Prepare your file, choose your options, and create your link.
Adding {{itemName}} to cart
Added {{itemName}} to cart