Build the EPK Bookers Can Scan in Thirty Seconds

An artist EPK that bookers and press actually use is a 30-second scan surface: who you are, what you sound like, where you are playing, proof you belong in the room, and how to book you — without a scavenger hunt. Fans can live on the homepage. Industry visitors need a dedicated path that does not make them click through merch drops to find a stage plot. This spoke sits under Websites That Feel Like Films.

The short answer

• Build a web EPK as the live source; keep a slim PDF as the email leave-behind.
• Above the fold: name, one-line positioning, booking email, Listen, and Download kit.
• Short bio for scanners; long bio one click away — never the other way around.
• Photos, logos, tech rider, and stage plot as named downloads, not 15MB attachments.
• Update quotes and stats when the fact changes — not on a vague “someday” calendar.

What is an EPK vs your full website?

Your site is the career home: listen, tour, merch, story. The EPK is the industry packet living on that domain — usually /epk or /press — optimized for bookers, promoters, festival programmers, and press.

ASCAP’s Bandzoogle brief states the split in plain language: fans come for songs and posts; media and industry come for the official bio and promo photos. CD Baby’s DIY Musician EPK guide says the same job in booking terms — a concise introduction for venues, agents, and talent buyers, hosted on the artist site so one URL travels.

Surface	Audience	Job	Tone
Homepage	Fans + cold traffic	Identity + listen/tour	Brand-first, cinematic
Tour	Fans	Buy tickets / waitlist	Utility + urgency
EPK / Press	Bookers, press, partners	Qualify + download + contact	Scannable, factual
About (fan)	Fans	Story and lore	Narrative
Pre-save / campaign	Paid + bio traffic	One release action	Disposable intensity

If your only “press kit” is a Google Drive folder with filenames like FINAL_v7_USE_THIS.zip, you do not have an EPK. You have a homework assignment for the booker.

On artist builds (Arkayla, Dog Park, Foxtide, Oliver Malcolm, Roe Kapara, and peers), press and booking paths belong in the IA — not as an afterthought PDF emailed from someone’s phone. Release campaigns stay on their own URL; do not let a pre-save page swallow the industry path.

A career site can feel like a film. The EPK still has to read like a packet.

PDF or web page — which format wins in 2026?

Web wins as the system of record. PDF wins as the attachable leave-behind.

CD Baby’s guidance is explicit: make a music website and host the EPK there so you have a simple URL when someone asks for a bio, a video, or a listen. A Drive or Dropbox folder is a supplement, not the kit.

Format	Wins when	Loses when
Web EPK	Always current; links to listen/tour; downloads on demand; works on a phone in a venue hallway	Booker is offline on a plane with only email
PDF one-sheet / short kit	Email threads, festival forms that demand a file	Becomes stale the week after you attach it; huge files get blocked
Drive / Dropbox dump	Overflow hi-res zips that exceed CMS caps	Unsorted files, broken permissions, “request access” walls

Practical dual-format workflow:

1. Maintain the web EPK as truth (bios, quotes, links, asset versions).
2. Export a 2–4 page PDF from the same facts when a form or agent asks for a file.
3. On the web page, offer “Download one-sheet (PDF)” as a button — generated or updated when facts change.
4. Never email a 40MB photo dump. Email the /epk link plus, if required, the slim PDF.

Gmail’s attachment help caps personal-account sends at 25 MB. Cross that line and Gmail strips the files and inserts a Drive link — which is how a “complete kit” arrives as a permission prompt the booker will not open.

Stating it plainly: a pretty PDF alone is a 2014 habit. Bookers open links. Your job is a page that loads fast and answers in one scroll — with a PDF for the minority of workflows that still require a file.

The 30-second scan path

Assume the booker has eight tabs open and a room to fill. Design the first viewport and the next scroll for this order:

1. Artist name (hero-level — not a tiny logo)
2. One-line position (“Austin indie rock · 2025 EP · touring TX/OK”)
3. Booking contact (email visible; no contact-form maze for industry)
4. Listen (2–3 priority tracks or a clean playlist link — not six embeds fighting)
5. Proof strip (notable press / support slots / cities — three facts max)
6. Download row (photos, logos, one-sheet, rider)
7. Short bio (~100–150 words)
8. Tour snapshot (next dates or “routing” note)
9. Longer materials below the fold (full bio, quotes, credits)

Second	What they should know
0–5	Who you are and that this page is for industry
5–15	How to book you and what you sound like
15–30	Whether you fit the bill (genre, draw signals, territory)

ASCAP’s eight-element list matches this scan: bio, photos, music, video, press, notable achievements, contact, social. You do not need a ninth “vibe” section. You need those eight in an order a tired human can finish.

If they cannot find booking contact in five seconds, the page failed — regardless of how filmic the photography is. Keep the EPK ruthless. Fan conversion lives on the rest of the site.

What bookers need that fans don’t

Bookers are advancing a night. Fans are deciding whether to stay. Mix those jobs and both bounce.

Asset / fact	Booker need	Fan need
Short bio	Paste into offers / announcements	Optional
Long bio	Rare — features, programs	Story page
Tech rider + stage plot	Advance the show	None
Hi-res photos + logos	Poster, web, press	Aesthetic, not downloads
Territory / routing	Can we offer a date?	Tour list is enough
Drawing power signals	Soft proof (press, supports, cities played)	Social proof vibes
Hospitality / contacts	Production emails	None — keep private tiers if needed
Live video	Does this act hold a room?	Entertainment, later

Put fan merch CTAs elsewhere. An EPK that opens on a drop countdown trains the wrong behavior.

• Booking email is visible without a modal
• Listen works without an account wall
• Rider and stage plot are dated files, not “email us”
• Tour snapshot is current or explicitly “routing [region] [season]”
• No newsletter popup on first paint

Industry visitors will not create an account to hear two songs. If the embed requires a login, you already lost the hold.

Photos and logos that belong in the kit

Offer a small, curated set — not every shoot from five years. ASCAP asks for a few official photos with vertical and horizontal options, plus black-and-white, and hi-res for print. CD Baby adds the crop rule: horizontal, vertical, and a square that survives social and poster templates.

• 3–6 live or press photos, web-ready (~2000px on the long edge) and a downloadable hi-res zip
• Color + mono logos (SVG or transparent PNG)
• One preferred horizontal and one vertical crop for posters/stories
• Credit line and usage note (“Photo: Name — promotional use OK”)
• Updated date on the download card so stale kits get retired

Filename like ArtistName_Press_01_Photographer.jpg. Not IMG_4821.JPG.

Crop	Typical use	Do not ship
Horizontal	Posters, web headers, festival grids	A group shot with unreadable faces
Vertical	Stories, one-sheets, print ads	A crop that cuts the headstock off the brand
Square	Avatars, playlist art, some posters	A logo smashed into a selfie
B/W	Print programs, newspapers	A phone filter on a color original

AI-generated “press shots” of the band that does not look like the band will get you dropped mid-advance. Real photos only for EPK use.

Link text on those cards is not decoration. WCAG 2.2 Success Criterion 2.4.4 requires that the purpose of a link be determinable from the link text or its immediate context. “Download” repeated six times fails that. “Download stage plot (PDF, 180 KB, updated 2026-03)” passes for a booker and for a screen reader.

Short bio vs long bio

Bio	Length	Job
One-liner	≤160 characters	Meta, social, poster subhead
Short	~100–150 words	Default for bookers and most press
Medium	A few paragraphs	Festival copy, longer listings
Long	300–500 words	Features, about pages, grant apps

ASCAP’s Bandzoogle piece is the reason that table has four rows: bookers and festivals run different word limits, so you keep an elevator pitch, a one-paragraph short, a medium, and a long. CD Baby’s version is shorter — long and short — and adds a writing test: imagine it read aloud as a showcase intro.

SXSW’s own programmers have said the quiet part out loud. In application tips from the SXSW Music Festival team, programmer Rory Burbeck notes that a clear, succinct biography does two jobs: it gives the programming team context, and if you get in, marketing will reuse that bio in festival campaigns. Write the version you want repeated. Do not write a joke bio and hope they “get it.”

Lead with the short bio on the EPK. Link “Full bio” as expand or separate anchor. Writing the long bio first and dumping it on the page is how scanners bounce.

Voice tip: facts over adjectives. Cities played, releases, notable supports, and what the project is beat “boundary-pushing sonic journey.”

Live video bookers actually watch

Audio tells them the songs. Video tells them whether the room will hold. SXSW Senior Manager Stacey Wilhelm’s tip on that same application page: do not skip the YouTube link. Programmers use it for music videos and live footage — “what to expect from your live performance.”

CD Baby’s EPK guide agrees on the booking cut: a live video if you are trying to get rooms; a current single video if the kit is for a release cycle.

Video	Use on the EPK	Skip when
Live, 1–2 songs, recent	Default for bookers	The mix is unintelligible or the room is empty in a way you cannot explain
Official video	Press + release kits	It is three eras old and the lineup changed
Full set	Link below the fold	It is the only embed and it autoplays
Vertical phone clip	Fine as proof of a real night	It is the only “live” asset you have and you play theaters

Embed one primary video. Link a second. Do not stack four players that all start muted and fight the listen module.

• One live clip that represents the current lineup
• Posted on a channel you control (YouTube or equivalent)
• Title includes artist name + “live” + city or venue
• No 30-second unskippable preroll if you can host a clean file
• If you have no live video, say so and point to the best audio — do not fake a crowd

A well-shot phone video from a real gig beats a cinematic trailer of a band that cannot be heard. Bookers are not buying your color grade.

Tech rider and stage plot

Yes — include them if you play amplified rooms. Bookers and production need them before load-in, not in a panicked email the day before.

TecRider’s technical-rider definition is the production one I use in briefs: the document attached to a performance contract that specifies stage plot, input list, monitor and PA needs, backline, and power. Their practical rule matches what I see on advances: start with the plot, then a numbered input list, then monitors, backline, lighting, power, and a technical contact. Keep it to one or two pages. Engineers often open this minutes before load-in.

File	Format	Notes
Tech rider	PDF	Inputs, backline, FOH/monitor needs, contacts
Stage plot	PDF or PNG	Clear, current, matches the rider; label audience vs stage view
Input list	Often inside rider	Keep versioned (“2026-03”)
Hospitality	Separate PDF if you have one	Do not bury beer prefs in the input list

Host downloads on the EPK. Label versions with dates. When the package changes, replace the file and bump the date — do not leave three conflicting riders in a Drive folder linked from an old email.

Acoustic / DJ / electronic acts: still ship a one-page technical needs doc so nobody invents requirements for you.

Advance order that does not embarrass you:

1. Booking confirm → send current rider + plot the same day.
2. ~30 days out → resend if anything changed (member, backline, IEM).
3. Final production advance → confirm house specs vs your ask.
4. Day-of → the file on /epk matches the PDF in the last email.

If the web file and the emailed file disagree, the house will believe neither.

Where booking contacts live

Put the booking email (and territory notes if split) on the EPK and in the site footer. Optional: booking@ and press@ as separate lines. ASCAP’s list includes email and a phone for tight deadlines. I still lead with email. Phone is a second line for acts that actually answer it.

Pattern	Use
Visible email on /epk	Default — fastest for bookers
mailto: plus copyable text	Accessibility + mobile
Form only	Weak for industry — use as secondary
Manager link-in-bio only	Fragile; link dies when the bio changes
Agency desk with territory	Required once you have split representation

If booking goes through an agency, say so: “North America: Agency / Agent — email.” Ambiguity loses holds.

Do not hide contacts behind a logged-in portal. Bookers will not create an account to email you.

Schema can help machines, not bookers. Schema.org MusicGroup is the type for a band, orchestra, choir, or solo musician — Google’s July 2026 index note puts it on tens of thousands of domains. If you emit JSON-LD, use MusicGroup (or Person for a solo act), genre, album / track, and a contactPoint with contactType of booking or press. That does not replace a visible email. It keeps the same facts consistent for search.

Asset delivery without 15MB emails

Bad	Better
Zip attached to cold email	Link to /epk#downloads
Google Drive with 40 unsorted files	Curated download cards with sizes listed
“Hi-res available on request” with no owner	Hi-res zip ready, under a sane size, or a pull link generated from the page
Watermarked unusable previews only	Web previews + clear hi-res download
Six buttons labeled “Download”	Named files + size + date in the link text

Target: each primary download under a few megabytes where possible; hi-res photo zips can be larger but should be pull, not push. List file size next to the button so people on phone data know what they are starting.

This is also a CMS constraint, not a taste debate. Webflow’s File field caps images at 4 MB and documents (PDF, ZIP, and the rest of their list) at 10 MB. The Assets panel allows ZIPs up to 25 MB. A 40 MB photo dump will not live in the CMS. Host the overflow on a storage URL you control, and put the card on the EPK.

Gmail’s 25 MB send cap is the other wall. Even if you can attach the zip, you should not. The booker’s mail client is not your CDN.

• One-sheet PDF under a couple of megabytes
• Rider + plot as separate small PDFs
• Web-sized photo set for on-page previews
• Hi-res zip as a pull link with size disclosed
• Logos as SVG / PNG, not buried inside the photo zip

If a manager cannot replace a rider without opening Designer, the kit will rot. Pair the download row with a CMS collection — title, file, updated date — the same editor discipline as CMS Choices Clients Will Actually Use.

Should the EPK be indexed for SEO?

Usually yes, but softly. Index /epk so “Artist Name press kit” and brand searches can land. Do not try to rank the EPK for competitive fan keywords — that is the homepage and music pages’ job.

Practical SEO for EPKs:

• Title like Artist Name — EPK / Press Kit
• One short intro paragraph with the artist name and genre
• Indexable page, fast images, real text (not only a PDF embed)
• noindex only if the kit is temporary/private for a campaign

Google’s title-link documentation is the reason that title is not a mood line. Google may build the result title from the <title> element, the visible H1, og:title, headings, and other on-page text. If your H1 says “Press” and your title says “Home,” you get a junk snippet. Make them agree.

Use noindex the way Google documents it: a robots meta tag or X-Robots-Tag header, not a robots.txt disallow. Google has to crawl the page to see noindex. Blocking the URL in robots.txt can leave a zombie result built from other sites’ anchor text.

A PDF-only kit buried in Drive will not help search. A thin page that is only an iframe of a PDF helps almost nobody. Google’s SEO starter guide still starts with crawlable, unique, helpful text. The EPK is allowed to be short. It is not allowed to be an empty frame.

Indexing choice	When
Index /epk	Default public kit
noindex on a passworded advance pack	Private hold, guest list, unreleased assets
noindex on old /press-2019	After you 301 to the current kit
robots.txt block	Almost never for the live EPK

How often to update press quotes

Update when the fact changes:

• New notable press → add; demote or remove stale quotes that no longer represent the era
• Major lineup change / name change / rebrand → full EPK pass
• Tour cycle announce → refresh routing note and listen links
• Quarterly minimum if you are actively pitching

Quote hygiene	Rule
Max on page	3–5 strong lines
Attribution	Outlet + author when real
Links	To the article when live
Dead links	Remove or replace — broken proof is anti-proof
Small vs large outlet	A real interview can beat a name-drop; SXSW’s James Minor said exactly that

CD Baby’s press section is a swap rule, not a museum: one sentence, link the full piece, replace as you get better lines. ASCAP’s version adds pull-quotes under the link so nobody has to open five tabs to learn what was said.

SXSW’s 2027 music-application note is useful even if you never apply: their programmers ask for tastemaker press if you have it — and they name the kind of outlets they mean. They also ask you to name a publicist, agent, or DSP pitching team when those people exist. Empty flex is worse than a short, honest proof strip.

Fake or paraphrased “press” gets you remembered the wrong way. No quotes beat invented ones.

Do not invent monthly listeners, ticket counts, or “sold out” language you cannot show. I will not invent them here either. If the number is real, date it. If it is not, cut it.

Festival forms vs the live EPK

Festival and conference applications are a different surface. They will not click your cinematic homepage and “figure it out.” They will paste fields.

SXSW’s public application flow is the pattern: an official form, a primary contact who answers email, and fields for music, bio, press, and video. The 2027 application page is still about quality of the music, a recent or upcoming release, and a live show people will talk about — not about whether your PDF has a foil texture.

Form field	What you paste from the EPK
Short bio	The 100–150 word version, not the novel
Long bio	The 300–500 word version
Press	2–4 current links, not a 2018 blog recap
Audio	The same 2–3 tracks as the listen module
Video	The same live URL you embedded
Contact	The person who actually answers

Keep a plain-text paste kit next to the designed page:

1. One-liner
2. Short bio
3. Long bio
4. Three press URLs
5. Two audio URLs
6. One live video URL
7. Booking email
8. City / territory

The form is the exam. The EPK is the open-book desk. If those two disagree, the programmer trusts neither.

Not every field will apply. SXSW programmer Casper Mills said they ask for everything at the start and will not ding you for skipping SoundCloud if Spotify and Apple Music carry the music. Fill what you have. Leave blank what you do not. Do not invent a playlist add you cannot link.

How you send the EPK

The page is useless if the email is a scavenger hunt. CD Baby’s pitch rule is the same as a booker’s inbox rule: one link, then only the facts they asked for.

Send	Do	Do not
First cold pitch	/epk URL + 2-sentence why this room / this week	12 links, a 20 MB zip, and “let me know!”
Hold / offer	/epk + slim one-sheet PDF if they asked for a file	A new Drive folder per venue
Advance	Same /epk#downloads rider that is live today	Last year’s PDF from a thread search
Press	/epk + the one quote and photo you want used	“Hi-res on request” with no owner

Email skeleton that does not waste a hold:

1. One line: who you are + the date or routing window you want.
2. One line: why this room (genre fit, support history, city).
3. The /epk URL.
4. Booking email repeated in the signature — same address as the page.
5. Attach the one-sheet only if the recipient or the form demanded a file.

If the page and the email disagree on contact, listen links, or the rider date, the booker will trust the last messy thread they already have. Keep one URL. Update the page. Resend the same URL.

Worked example: EPK page outline

Use this as a build checklist for Webflow or Framer:

1. Hero: name, one-liner, Booking email, Listen, Download one-sheet
2. Proof strip: 3 facts
3. Listen module: 2–3 tracks
4. One live video
5. Short bio
6. Downloads: photos / logos / rider / stage plot / one-sheet (with dates)
7. Tour snapshot + link to full Tour
8. Press quotes (3)
9. Long bio (collapsed or lower)
10. Credits / contacts footer

CMS field	Type	Required
Asset title	Plain text	Yes
File	File or URL	Yes
File size label	Plain text	Yes
Updated date	Date	Yes
Credit / usage	Plain text	Photos and logos
Show on EPK	Toggle	Yes

Pair that collection so managers replace a rider without touching layout. If the weekly editor will not log in, you do not have a living kit — you have a launch-day sculpture.

Keep campaign heat off this page. A pre-save module belongs on the release URL, not in the booker’s first viewport.

Failure mode: the fan homepage as EPK

Common failure: “Just send them the site.” The booker lands on a hero video, a merch drop, and a newsletter modal. Stage plot is nowhere. They email a competitor who sent a clean /epk link.

Cost: lost holds, slower advances, looking less professional than a smaller act with a tighter kit.

I have shipped hundreds of production sites. The music ones that book cleaner share one boring trait: a dedicated industry URL that still works on a phone in a loading dock.

Fix: one industry URL, scan path, downloads, booking contact. Keep the film-grade homepage for fans — do not make bookers suffer it.

Symptom	What actually broke	Repair
“They never replied”	Contact buried under a form or Linktree	Visible email on /epk
“They used last year’s photo”	Undated Drive folder	Dated cards; retire the old zip
“FOH had the wrong plot”	Three riders in old threads	One current file on the page
“They thought we were a DJ”	No live video, vague one-liner	Live clip + genre in the first line
“The PDF was empty in Outlook”	30 MB attach over the Gmail cap	Link + slim one-sheet

Bravery is not a press kit. A URL that answers in thirty seconds is.

FAQ

What photos belong in an EPK?

A curated set of 3–6 current press or live photos plus logos, with web previews and a hi-res download. Credit the photographer and date the zip so stale eras get retired. ASCAP’s digital press kit list still wants vertical, horizontal, and print-ready hi-res — not a camera-roll dump.

How long should the short bio be?

About 100–150 words for the default EPK bio. Keep a one-liner for posters and a longer bio below or behind a link for features. Festival forms often want both lengths; write them once and paste.

Do I include tech rider and stage plot?

Yes if you play rooms that advance production. Host dated PDF/PNG downloads on the EPK so promoters are not chasing attachments. A one-to-two-page rider with plot, input list, and a technical contact is enough for most club and theater advances.

Should the EPK be indexed for SEO?

Yes in most cases, with a clear press-kit title and real text. Do not force it to compete with fan landing pages for broad music keywords. Use noindex only for private or expired kits, and do not block the live URL in robots.txt if you want Google to see the tag.

Where do booking contacts live?

On the EPK above the fold and in the footer — email visible. Forms can be secondary. Agency territories should be labeled, not implied. If a human will not answer that inbox, it is not a booking contact.

How often should I update press quotes?

Whenever a stronger quote lands or an old link dies — and at least each tour or release cycle. Three current lines beat a graveyard of ten. Dead links are anti-proof; remove them the week they 404.

CTA

Thirty seconds. Clear contact. Assets they can pull without asking twice.

Explore /websites or book a Website sprint at /contact?intent=websites-sprint.