Guide
How to Send Music Without Requiring a Login
Marc Aaron Jacobs
Founder, DropCue · Composer
Every login screen between your pitch and a supervisor is a place the pitch dies. The fix is not a better login. It is not having one.
Who this is for
Anyone pitching music to someone who has no reason to care about your software. Composers sending cues to supervisors. Publishers sending selects to agencies. Artists sending unreleased material to labels. Producers sending mixes to clients.
The common thread: the person on the other end is busy, is not your user, and will not sign up for anything to do you a favor.
The audience-specific reality
A music supervisor gets somewhere between dozens and hundreds of pitches a week. Their triage is brutal and mostly unconscious. If a link opens and plays, they listen. If it asks for anything first, they move on, and you never find out that is what happened.
The things that kill a pitch at the door are predictable. An account signup wall. An app download. A 400 MB zip that has to finish before anything plays. A file format their browser will not play. A link that works on desktop and breaks on the phone they are actually holding.
This is why the default workflow is still an email attachment, which has its own failure mode: attachment size limits, no analytics, no version control, and no way to revoke access once it is out. WeTransfer solves the size limit and nothing else. Dropbox and Google Drive solve storage and then ask the supervisor to download before listening, or to sign in when the sharing permissions are set slightly wrong.
Requiring a login is not a security feature in this context. It is a conversion problem.
Why DropCue fits this workflow
A DropCue share link opens and plays. No account, no app, no download step. The supervisor clicks, the waveform loads, and audio starts streaming. Large WAV files stream with range requests rather than downloading in full first, so a 200 MB master starts playing in about a second.
Access control without an account. You can password-protect a share, set an expiry date, and control whether downloads are allowed per format, all without the recipient ever creating a profile. The password is on the link, not on a user record, which is the distinction that keeps it frictionless. Passwords are hashed server-side rather than stored in the clear.
Per-recipient links mean you know who listened. Each recipient gets their own URL, so analytics resolve to a person rather than to a link. You see who opened it, which tracks played, for how long, and how many times. Recipients also only see their own timestamped comments, so a pitch to three supervisors does not become a group chat.
Revocation actually works. Because access runs through a link you control rather than a file you sent, you can deactivate a share, set it to expire, or adjust download permissions after the fact. An email attachment is gone the moment you send it.
It works on the phone the supervisor is holding. The player is browser-based and mobile-first, so the link that lands in email at 11pm plays without an app install.
The features that matter most
✓ Browser playback with no account
The supervisor clicks and hears music. No signup, no app, no download. This removes the single most common place a pitch dies.
✓ Streaming with range requests
A 200 MB WAV starts playing in about a second instead of downloading in full first, so high-resolution masters do not cost you the listen.
✓ Password and expiry on the link
Protect unreleased material without making the recipient create an account. Access control lives on the share, not on a user record.
✓ Per-recipient URLs
Analytics resolve to a person rather than to a link, so you know which of the three supervisors you pitched actually listened.
✓ Revocable access
Deactivate or expire a share after sending. An email attachment cannot be recalled once it is out.
✓ Per-format download control
Allow a WAV download for the supervisor who needs to cut with it, while keeping streaming-only for everyone else.
Names you may know in this space
WeTransfer
Solves the attachment size limit and nothing else. No analytics, no revocation, no version control, and the recipient still ends up with a downloaded file rather than something that plays.
Dropbox
Fine as storage. As a pitch delivery tool it either asks the supervisor to download before listening or, when permissions are set slightly wrong, asks them to sign in.
Google Drive
Same failure mode as Dropbox, with a sharing permission model that produces the request-access screen more often than people expect.
SoundCloud
Plays in the browser without a login, which is why composers reach for it. Built for public audiences rather than private pitching, so access control and per-recipient analytics are not really there.
Pricing for this audience
Login-free sharing is core to the product rather than a premium add-on, so it works on every plan including Starter at $5 a month with annual billing. Password protection and full analytics sit on Pro, which starts at $15 a month for 1,000 tracks. The recipient never pays anything and never creates an account regardless of your tier.
Frequently asked questions
Does the person receiving the music need a DropCue account?
No. That is the entire point. They click a link and audio plays in their browser. They never create an account, never install anything, and never see a signup wall.
How is this more secure than a public Dropbox link if there is no login?
Access control lives on the link rather than on a user account. A share can carry a password, an expiry date, per-format download rules, and per-recipient URLs, and it can be revoked after sending. A public Dropbox link has none of that, and a permissioned one asks the supervisor to sign in, which is the problem you were trying to avoid.
Can I stop someone from downloading the files?
Yes. Downloads are off unless you enable them, and you can control which formats are downloadable. Streaming-only is the default posture for unreleased material. Note that anything streamable can ultimately be captured by a determined recipient, so treat this as friction and access control rather than as DRM.
Will a large WAV file play, or does it have to download first?
It streams. Playback uses HTTP range requests, so a large master starts playing in about a second and seeking works without pulling the whole file. This is the main practical difference from a Dropbox or WeTransfer link, which hands over a file and makes the listener wait.
Do I know whether they actually listened?
Yes, and per recipient. You see who opened the link, which tracks played, how long each played, and repeat listens. A pitch with zero plays is useful information that an email attachment never gives you.
Does it work on a phone?
Yes. The player is browser-based and built mobile-first, which matters because a large share of pitch links get opened on a phone rather than at a desk.
