Cover letters do not get you into festivals. Films do. But a generic cover letter can keep you out, because it signals that you are submitting in bulk rather than because you care about this festival specifically. The fix is short, addressed, and specific.
Three paragraphs, around 300 words, sent to a named programmer. That is the entire format.
Address the actual programmer
Most festivals publish their programming team. Find the name of the programmer who handles your strand (shorts, docs, your genre, your region) and address the letter to them. "Dear programming team" is a tell. "Dear Tariq Ahmed, Shorts Programmer" is research.
If you cannot find the name, address it to the head of programming, not the festival generically. If you cannot find that either, the festival probably does not read cover letters and you can skip writing one. Save the energy for festivals that do.
Paragraph 1: who you are and what the film is
One sentence on who you are. One sentence on what the film is, in plain English (not the logline, the version a friend would understand at a dinner party). One sentence on where the film is in its life: just finished, world premiere available, looking for its European premiere, etc.
Example: I am a director based in Glasgow, and my first short, "The Sluice", is a 14-minute fiction about a water bailiff who finds his teenage daughter at an illegal salmon farm. The film is finished, our world premiere is available, and we are targeting Edinburgh as our first festival of the year.
Paragraph 2: why this festival, specifically
This is the paragraph that separates research from copy-paste. Name one or two films the festival programmed in recent years that resonate with yours, and say why. Cite a strand the festival runs that fits your work. Mention a programmer's public statement about the kind of work they want to see.
If you cannot say something specific about why your film fits this festival, that is useful information. You should probably not be submitting.
Paragraph 3: a thematic angle, not a plot recap
Synopsise the film in two or three sentences that lead with theme, not plot. The reader already has the synopsis from the submission package. The cover letter version gives them a frame: what the film is doing, what question it is asking, why it matters now.
Match tone to genre. A cover letter for a horror film should not sound like a Sundance drama cover letter. The cover letter is the first prose sample of you the programmer reads.
Sign off short
One sentence thanking them for considering the film. One sentence with a link to the EPK if they want more. Your name and the contact details under it. Done.
The single biggest mistake
Copy-paste cover letters with the festival name swapped. Programmers read hundreds of submissions. They can spot a swapped name at 20 paces. If the rest of the letter is generic, the swap reads as cynical. If you do not have time to write a specific cover letter, send none. A missing cover letter is better than a transparent one.
Frequently asked questions
Do you need a cover letter to submit to a film festival?
A cover letter does not get your film into a festival; the film does. But a generic cover letter can keep you out, because it signals that you are submitting in bulk rather than because you care about this festival specifically. If a festival does not appear to read cover letters, you can skip writing one and save the energy for festivals that do.
How long should a film festival cover letter be?
Keep it to three short paragraphs of around 300 words, addressed to a named programmer. Anything longer reads as a plea. The three paragraphs cover who you are and what the film is, why this festival specifically, and a thematic angle rather than a plot recap.
Who do you address a festival cover letter to?
Address it to the named programmer who handles your strand, such as shorts, docs, your genre, or your region. Most festivals publish their programming team, so find that person and write to them. If you cannot find a name, address the head of programming rather than the festival generically.
What is the biggest mistake in a festival cover letter?
Copy-paste cover letters with only the festival name swapped. Programmers read hundreds of submissions and can spot a swapped name quickly, and if the rest of the letter is generic the swap reads as cynical. If you do not have time to write something specific, send no cover letter at all, because a missing one is better than a transparent one.
RelatedProgrammer profiles, in one place
Circkit's Insider module shows programmer and selection context where data is available, so paragraph two starts from research instead of guesswork.
