How to write a music pitch email that actually gets a reply
The structure of a pitch that gets opened and answered, plus a real template you can adapt in five minutes.
Updated July 2026
A good music pitch email is short, specific, and built around one clear ask. The reader (a curator, a blog editor, a radio host) opens dozens of these a day, most of them templated blasts that never mention who they are or why the song fits. The pitch that gets a reply does three things fast: it proves in the first line that I actually know their work, it hands them a one-click private link, and it asks for exactly one thing. Everything else is noise. Below is the structure that works, the exact template I use, and the small mistakes that get pitches deleted before the song ever plays.
Why most pitches get ignored
The people you are pitching are not ignoring you because your music is bad. They are ignoring you because the email gives them no reason to spend ninety seconds on it. The three most common reasons a pitch dies on arrival: it is obviously copy-pasted (no name, no reference to their actual work), it buries the song under three paragraphs of biography, or it makes the reader do work (log in somewhere, download a file, hunt for the track). Every one of those is fixable in the writing, before you ever worry about the music itself.
The anatomy of a pitch that gets opened
The subject line
The subject line decides whether the email gets opened at all. Keep it plain and descriptive. Name the genre and the format they publish: "Lo-fi indie single for your weekly playlist" or "Bedroom-soul track for a premiere". Skip the all-caps, skip the emojis, skip "PLEASE FEATURE ME". You want it to read like a note from a peer, not a press release from a stranger.
The first line
The first line is where you earn the read. This is the one line that must be specific to this person. Reference an actual playlist they run, an artist they recently covered, or the kind of thing they publish. "I saw you added [artist] to [playlist] last month and thought this might sit in the same lane" does more than three paragraphs of hype. If you cannot write a true, specific first line for someone, you have not researched them enough to pitch them yet.
The song and the link
Give them the track in one click. One private streaming link that plays instantly, no login, no download. Add a single line of context: genre, a one-word mood, maybe a comparison ("if you like [X] and [Y]"). That is enough for them to decide whether to press play.
The ask
End with exactly one ask, phrased as a low-pressure question. "Would this fit [playlist]?" or "Open to premiering it the week of [date]?" One ask, clearly stated, easy to say yes or no to. Never stack three requests into one email.
A pitch email template you can steal
Here is a template I have used to reach curators and blog editors. Fill in the brackets and cut anything that does not apply.
Subject: [Genre] [single/EP] for [their playlist or column]
Hi [name],
I came across [specific thing: their playlist, a recent post, an artist they featured] and it looked like our worlds overlap. I make [genre] out of [city], somewhere between [artist A] and [artist B].
I have a new [single/EP] called "[title]" coming [date]. Private stream here (plays in one click, no login): [link]
Would it be a fit for [their playlist / a feature]? Totally fine if not, and thanks either way.
[Your name] [One link: your Spotify or site]
That is the whole thing. Notice what is missing: no life story, no "I have been making music since I was five", no ten social links, no attachment. Just context, a link, and one ask.
Send it to the right person
A perfect pitch to the wrong person still fails. Before you write a word, make sure the recipient actually covers your genre and takes submissions, and that you are using the contact method they prefer. I keep a directory of verified music contacts with exactly that information: genre, format, and how each one wants to be reached, whether the target is a magazine like Glide Magazine or a playlist like parapop.
People who actually take pitches
Verified curators with their genres and preferred contact method, so your pitch lands with someone who wants it.
Pitching people who match your sound is the single biggest lever on your reply rate. Ten well-matched, personalized emails will beat a hundred blasts every time.
What to leave out
Cut the biography. Cut the "as you may know". Cut every link except the one they need. Do not attach files. Do not send to a general info@ address if a named person is listed. And do not pitch the same person the same song twice. Restraint reads as professionalism, and professionalism is rare enough in an inbox that it stands out.
After you hit send
Log the send in whatever tracker you use, then leave the thread alone for a week before a single, polite follow-up. Most replies come on the follow-up, not the first email, so tracking your outreach is not optional. For the exact follow-up wording, see the guide on how to follow up on a music pitch. For a full library of templates by contact type, see music pitch email templates.
A pitch this short takes longer to write than a long one, and that is exactly why it works. Draft yours against the anatomy above, then point it only at curators who already play your lane; the words start mattering once the address is right.
Frequently asked
How long should a music pitch email be?
Short. Aim for roughly 90 to 150 words: one line of context, one line on why you are writing to this specific person, a private link, and a clear ask. If the reader has to scroll, the pitch is too long. The goal of the email is to get a listen, not to tell your whole story.
Should I attach the audio file?
No. Never attach an mp3 or wav. Big attachments get flagged and slow the inbox down. Send a private streaming link (a SoundCloud private link, an unlisted YouTube, or a Bandcamp private stream) that plays in one click with no login required.
What subject line works best?
Plain and specific beats clever. Name the genre and the reason: "Dream-pop single for your new-music roundup" tells the reader what it is and why it fits them. Avoid all caps, "FEATURE REQUEST", and anything that reads like a mass blast.