EPK Basics for Indie Artists

The problem most indie artist EPKs have

Most electronic press kits fail for the same reason: they try to prove the artist worked hard instead of answering the question the booker or writer actually has. A ten page deck with every show you have ever played, six streaming links, and a 400 word life story does not get read twice. It gets skimmed once, maybe, and then ignored while the next email in the inbox gets the reply.

An EPK for an independent artist needs five things: a short bio, a few press-ready photos, your current links, a light tech rider if you play live, and one clear way to contact you. That is the whole kit. Everything else is noise that slows down the one person you are trying to move to "yes."

This guide covers what actually belongs in each section, the order to build it in, the mistakes that quietly kill good pitches, and how to keep the whole thing from going stale between releases.

What is an EPK actually for?

A press kit exists so a promoter, blog, playlist curator, or venue can learn who you are and book or cover you without emailing you five follow up questions. It is not a portfolio. It is not a biography. It is not a place to prove how much work you have put in.

Think of it as the fastest path from "who is this artist" to "yes, let's talk." Every section should answer a specific question a booker or writer actually has in the moment they are looking at it. If a section does not do that, cut it.

This is also why "how to make an EPK" and "what goes in a press kit" are two of the most searched questions for independent artists right now. Most guidance online either lists everything a label-signed act might include, or gives you a blank template with no order of operations. Neither tells you what to cut.

The five sections your EPK needs, in order

Build these in this order. Each one depends on decisions you make in the one before it.

1. **One clear ask.** Decide this first, even though it goes last in the layout. Book me, review this, license this. Everything else in the kit should support this one sentence. 2. **Bio.** Two versions: a two to three sentence version and a short paragraph version. Covers genre, location, and what makes the project recognizable. 3. **Photos.** Three images: a clean portrait, a live or performance shot if you have one, and a visual-brand shot that matches your release art. 4. **Links.** Your site, your current single or release, and your main streaming profile. Nothing else. 5. **Tech rider lite.** One page, only if you play live.

Building the ask first sounds backwards, but it keeps the rest of the kit from drifting into general-purpose filler. A bio and photo set built around "book me for a release show" reads differently than one built around "feature this track on your blog." Decide the ask, then write everything else to serve it.

How long should an artist bio be for a press kit?

Shorter than you think. Aim for two versions:

- A two to three sentence bio for quick use in a lineup announcement or a blog post that just needs a line of context. - A short paragraph version, under 150 words, for anyone who wants a bit more.

Skip the life story. Cover genre, where you are based, and one or two things that make your sound or project recognizable. Save the deeper story, the influences, the backstory on your name, the full discography, for your artist site, where readers who actually want it can click through.

A common question we see online is whether to write the bio in first or third person. Third person is the safer default for press use, since writers often copy and paste it directly into coverage. First person reads more personal on your own site or socials, but it creates friction when a blog has to rewrite it before publishing.

What photos actually get used?

Three is usually enough:

1. One clean headshot or portrait, well lit, no heavy filter. 2. One live or performance shot, if you have one worth using. 3. One image that fits your visual brand, artwork adjacent, moody, whatever matches your release covers.

All three should be high resolution and shot landscape or square so they drop into blog layouts and press pages without an awkward crop. Label the files clearly, something like `artistname_portrait_2026.jpg`, not `IMG_4821.jpg`, and credit the photographer if someone other than you took the shot. Skip filters that will look dated in a year. A photo that looks very "of the moment" trend-wise often reads as dated faster than a plain, well lit shot.

What links actually belong in an EPK?

Fewer than most artists include. Three links cover almost every use case:

1. Your home base site. 2. Your most current single or release. 3. Your main streaming profile.

If you are pushing a specific song or tour, that link goes at the top, not buried in a list under four other platforms. This is also where a home base matters: a site you control is easier to keep current than a folder of individual platform links that drift out of date every time you drop something new.

If you have not set one up yet, [why independent artists still need a home base site](/blog/why-artists-need-a-website) covers the basic case for it, and [what belongs on an artist site homepage](/blog/artist-site-homepage-checklist) breaks down what that page should actually hold.

Tech rider lite: do you actually need one?

If you play live at all, a one page version of your technical needs saves you from answering the same text messages before every show. Keep it to:

- Inputs needed (vocal mics, DI boxes, number of channels). - Whether you bring your own backline or need the venue to supply it. - Any non negotiable staging or sound needs (in-ear monitors, a specific mic, a DJ booth setup).

This is "lite" on purpose. A full production tech rider with stage plots and power requirements is for a different stage of career. Most independent artists only need enough detail for a sound engineer to set up without guessing twice.

One recent proof point

Add one line that shows the kit is current: a recent show, a release date, or a press mention. This is not the place for streaming numbers or follower counts. Keep it to information a booker or writer can act on. A single sentence like "released a new single in March 2026, now booking a fall release show" tells a promoter exactly where you are. A follower count tells them nothing they can use.

Common mistakes that quietly kill a good EPK

1. **Multiple asks.** "Book me, review this, license this, and check out my merch" forces the reader to guess which one matters. Pick one. 2. **Six links instead of three.** Every extra link is a chance for the reader to click the wrong one or get distracted before reaching the one that matters. 3. **A bio that reads like a diary entry.** Save the personal story for your site. Press copy should be scannable in ten seconds. 4. **Outdated proof points.** A "recent show" from eighteen months ago reads as a red flag, not a credential. 5. **Low resolution or cropped photos.** A photo that looks great on a phone screen can look rough on a blog header. Always check at full size before sending. 6. **No file naming or photo credit.** Small detail, but it signals you have done this before. 7. **Burying the ask at the bottom of a long document.** If a booker has to scroll past three sections to find out what you want, you have already lost some of them.

The phone test for your EPK

Before you send your EPK anywhere, run it through the same kind of quick check you would run on a mix: does it still hold up outside the environment you built it in?

Open your EPK on your phone, the way most bookers and bloggers will actually see it first, often while scanning email between other tasks. Check three things:

1. **Does the ask show up without scrolling?** If someone has to swipe past your bio and three photos before finding out what you want, move it higher. 2. **Do the photos load fast and look sharp at phone size, not just on your desktop screen?** A photo that looks crisp on a 27 inch monitor can look soft and slow to load on mobile data. 3. **Can you read the whole kit in under 30 seconds?** Time yourself. If it takes longer, something needs to be cut, not reformatted.

This "translate it to a different screen" habit is the same instinct you would use checking a mix on a laptop speaker, in a car, or on earbuds. The venue changes, the content should still land the same way.

How do I keep an EPK from going stale?

The same way you keep a site current: update it when something actually changes, not on a fixed schedule you will not stick to. A new release, a new primary link, or a new photo set is a reason to revisit it.

If this sounds familiar, it is the same logic behind [keeping an artist site updated without a full redesign every drop](/blog/artist-site-monthly-care). An EPK built as part of your site is easier to maintain than a separate PDF you forget exists until a booker asks for an updated one.

Troubleshooting: when an EPK is not landing

If you are sending your kit out and not hearing back, check these before assuming the music is the problem:

- **Is the file or link actually opening on the recipient's end?** A PDF that will not open on mobile, or a Google Doc with the wrong sharing permissions, kills the pitch before anyone reads a word. - **Is the ask matched to the recipient?** A blog does not need a stage plot. A venue does not need your Spotify for Artists bio. Tailor the ask line to who is receiving it. - **Is your best track actually embedded or linked at the top, not buried under a bio paragraph?** Writers and curators often listen before they read. - **Are you sending it cold with no context?** A one line email that states the ask, with the EPK link attached, outperforms an EPK sent with no message at all. - **Is it current?** A press kit referencing a single from two releases ago tells the reader you have not touched this in a while.

Checklist: build your EPK in order

1. Write your one sentence ask. 2. Write the two bio versions (short and paragraph). 3. Select and label three photos. 4. Choose your three links, with the most relevant one first. 5. Build a one page tech rider if you play live. 6. Add one current proof point. 7. Run the phone test before sending it anywhere. 8. Set a reminder to revisit it at your next release, not on a calendar schedule.