6 Things Festival Programmers Actually Want From Your Film
Festival programmers watch hundreds, sometimes thousands, of films every year. Many of those films are beautifully shot and technically solid… yet still get rejected. What separates the few that make it into a line-up from the many that don't is rarely just "production value" or "who you know."
Here's the thing: festival programmers are programming for a festival. It's right there in the title. Before anything else, the fundamental question a programmer is asking is whether this film fits their programme, their mission, their ethos. Technical polish and strong storytelling matter, but they're secondary considerations. The first filter is alignment. Only once a film clears that bar does the next question come into play.
Programmers are curating an experience for their audience, and they're looking for very specific things that help them do that well.
Below are 6 things festival programmers actually want from your film and how you can give it to them, followed by a real-world example and common questions.
1. A Clear, Compelling Story (No Matter the Genre)
Festival programmers are looking for a strong, coherent story or idea above everything else. That doesn't mean your film has to be conventional or plot-heavy, but it does need to feel intentional and emotionally or intellectually engaging.
What they want:
A clear sense of whose story this is and what's at stake
A beginning, middle, and end — even in experimental work, some sense of progression or transformation
Emotional impact: laughter, tension, curiosity, sadness, surprise — something that stays with the viewer
A film that knows what it is: tone, style, and pacing working together rather than fighting each other
What hurts you:
Beautiful visuals with no narrative drive or clear point of view
Overly long running times for the story you're telling
Confusing structure that feels messy rather than deliberate
Characters who don't change, make choices, or reveal new layers
How to improve this before you submit:
Do test screenings with people who are not close friends. Ask:
"Where were you bored?"
"Where were you confused?"
"What do you think the film is about?"
Cut any scene that doesn't:
Move the story forward
Deepen character
Sharpen the theme
In a pile of submissions, the film that tells a story cleanly and confidently — even on a tiny budget — has a real advantage.
2. A Film That Fits Their Festival and Program
Programmers are not just picking "good films"; they're building cohesive programs: a shorts block that flows, a feature section with a specific flavor, a festival identity that audiences recognize.
If a festival has never programmed a horror film, has no horror strand, and has no history of horror winners, submitting a horror film — no matter how accomplished — is unlikely to result in placement. Poor fit is one of the most common reasons films get rejected, and filmmakers rarely find out that's the reason.
What they want:
Films that match their mission (e.g., first-time directors, regional films, underrepresented voices, genre focus, etc.)
Films that sit well within a specific program or block (e.g., LGBTQ+, horror, docs about climate, student films)
Proof you understand the festival: your film is not wildly off-brand
What hurts you:
Submitting a horror short to a festival that rarely or never programs horror
Sending a 40-minute short to a festival that's known for fast-paced 5-12 minute shorts blocks
Ignoring category rules (e.g., submitting a narrative film to a documentary category just because it was cheaper)
How to show fit:
Look at previous lineups and ask:
"Would my film naturally sit beside these titles?"
"Is there at least some track record of them programming films like mine?"
Be honest with yourself:
If their shorts are all under 15 minutes and you have a 27-minute drama, it may be a tough fit.
Use your cover letter, logline, or filmmaker statement to very briefly connect your film to:
The festival's mission
A specific program strand or theme
This research is a one-time investment that pays dividends across an entire career. Understanding what different festivals exist, what kinds of films they support, and what their programming history looks like gives you a clear sense of where your work actually belongs. For writer-directors, this means knowing instinctively where future projects will be submitted. For producers, it means having a working map of the landscape that can be applied across multiple projects.
This is essentially what paid festival submission agencies do — they look at a film and match it to the festivals most likely to respond to it. But there's nothing stopping filmmakers from doing this themselves. On one feature film, A Bird Flew In Her, an assistant spent a few days doing exactly that: researching festivals, reviewing the types of films they'd previously supported, and narrowing down a targeted list. The approach works.
Programmers are relieved when they see a film that obviously belongs in their world. Make it easy for them.
3. Strong Craft Where It Counts (Especially Sound and Editing)
Programmers understand low budgets. They don't expect you to look like a studio feature. They do expect competent craft, especially in areas that affect audience experience the most.
Bad sound is a significant issue. It directly impacts audience experience and will almost certainly get a film deprogrammed before it's seriously considered. It's one of the fastest reasons a programmer stops a screener.
What they care about most:
Sound: clean dialogue, balanced mix, no painful peaks
Editing and pacing: no flab, clear continuity (or deliberate fragmentation), a rhythm that suits the story
Performances: actors grounded in the same world, believable reactions, no "high school play" line readings
Clarity of image: not necessarily high-end cameras, but no incomprehensibly dark or muddy picture
What they're more flexible on:
Slightly rough color grade if the storytelling is strong
Simple production design or locations
Minimal VFX or simple visuals if they serve the story
Practical tips:
If you're submitting a work-in-progress, clearly label what's unfinished at the start (e.g., "Temp mix, color not final").
Prioritize your budget for:
Clean production sound
A good sound mix
Enough time to edit and test screen
Cut ruthlessly. Most shorts and many features are too long by 10-20%.
Programmers will forgive limited resources, but not a lack of respect for the audience's time and ears.
4. A Reasonable Runtime That's Easy to Program
A festival schedule is like a jigsaw puzzle. Programmers are trying to fit a certain number of screenings into a limited number of time slots. Your runtime heavily affects how "programmable" your film is.
Shorts:
Under ~10 minutes is often the sweet spot for many festivals' shorts blocks.
15-20 minutes can work if the film is truly exceptional or fills a specific programming need.
25-40 minutes is the toughest length:
Too long to easily slot into a shorts block
Too short to stand alone like a feature
Features:
80-100 minutes is generally the most programmable.
Very long features (120+ minutes) face a higher bar because each screening takes the slot of two shorter films.
What this means for you:
If you're still in development or production, consider aiming shorter rather than longer, especially for shorts.
If you already have a long short:
Ask yourself: "If I weren't the director, what would I cut?"
Aim to get to the leanest possible version instead of assuming festivals will accommodate the length.
Programmers might like your 32-minute short and still not be able to fit it. Make their job easier and your odds improve.
5. A Film (and Filmmaker) That Helps Them Attract Audiences
Festivals are public events. They need seats filled, buzz generated, and a sense that programming your film will energize the festival, not just occupy a slot.
What they want to see:
Evidence you can help bring an audience:
Past successful screenings
A decent social media or community presence
Cast and crew who are willing to attend and promote
A film that:
Offers something for marketing (clear hook, topic, star, angle)
Sparks conversation (after-screening Q&As, panels, community tie-ins)
How you can signal this:
Maintain a basic online presence for the film:
Simple website or page
Trailer or teaser
Clear logline and key art
In your submission materials, briefly note:
Any existing audience or community around the topic
Organizations, schools, or groups likely to attend
Prior screenings or awards (if any)
Programmers are not just curators; they're also event producers. Showing you understand that makes you significantly more attractive.
6. Professionalism, Clarity, and Honesty
Once your film is in serious contention, how you handle yourself can tip things in your favor — or out of it. Programmers and coordinators remember which filmmakers were reliable and pleasant and which ones created unnecessary stress.
What they look for:
Accurate information in your submission:
Correct runtime
Correct premiere status
Proper categories
Working screeners:
Passwords that function
No expired links
Compatible formats
Responsive, respectful communication:
Answering emails in a timely manner
Meeting deadlines for deliverables
Being clear and concise
Honesty about:
Premiere status and other acceptances
Whether the film is a rough cut or picture-locked
Red flags:
Misrepresenting premiere status to look more "exclusive"
Aggressive or rude follow-ups asking "Why was I rejected?"
Sending updates and new cuts every few days after you've already submitted, unless the festival has invited or requested them
It's also worth including a short cover letter or statement that briefly connects the film to the festival's specific mission or programme strand. That added context can genuinely make a difference — and it signals to the programmer that you've done your homework.
Programmers have long memories. Being professional not only helps you now — it helps you for future projects too.
Real-World Example: How a Short Film Got Programmed Widely
A good illustration of these principles is the journey of a fictional (but realistic) short film, "Second Shift," a 9-minute drama about a single mother working overnight at a warehouse.
What the film did well:
Clear, emotional story: In one night, the protagonist must decide whether to risk her job to attend her child's school performance. The stakes are simple but powerful.
Tight runtime: At 9 minutes, it slotted easily into shorts blocks. Festivals could pair it with comedies, social-issue films, or "local stories" programs.
Solid craft where it counts:
Clean production sound despite noisy locations
Confident, unobtrusive editing
A strong lead performance
Obvious festival fit:
Submitted primarily to festivals that showcase working-class stories, women filmmakers, and regional films
The director was from the same region as several festivals they targeted, giving programmers a local angle
Audience-friendly and promotable:
The topic connected to labor, parenting, and economic precarity — ripe for post-screening discussions
The team had relationships with local unions and community groups, who helped fill seats at screenings
Result:
"Second Shift" was accepted to a mix of regional and thematic festivals, winning a couple of audience awards. It never played the biggest "name" festivals, but it built a real audience and led directly to the director's next, higher-budget short and a TV writing opportunity.
From a programmer's perspective, this film was an easy "yes" because:
It told a powerful story efficiently
It fit clearly into multiple program themes
It was technically competent and respectful of audience time
The team was organized, responsive, and helped amplify the screenings
Common Questions and Answers
Q1: Is it worth submitting if my film isn't 100% finished?
It depends on the festival and how unfinished it is.
If you submit a work-in-progress, be transparent:
Add a card at the beginning: "Work-in-progress. Temp mix. Color not final."
Don't submit if:
The story isn't locked
You're still missing scenes or performances
Do submit if:
Picture is locked and you're just polishing sound or color
The festival explicitly accepts works in progress
Remember: programmers usually watch your film once. Don't rely on "It'll be better later" to sell it.
Q2: Do big-name actors or expensive gear really matter?
They can help but are rarely decisive on their own.
A known actor might make your film easier to market and sometimes easier to program.
Expensive cameras can improve image quality, but festivals regularly program films shot on phones or DSLRs if the story and craft are strong.
If you have to choose, invest more in sound, acting, and editing than in premium gear.
Q3: How important is premiere status?
For top-tier festivals, premiere status can be very important. For most mid-level and regional festivals, it's a nice bonus but not a deal-breaker.
Always be honest about:
World, international, national, and regional premieres
Previous festival screenings or online releases
Some festivals require at least a regional or national premiere; others are flexible.
If you're targeting a few "dream" festivals, build your submission strategy around their premiere requirements first, then expand outward.
Q4: Why did my well-made film get rejected?
Rejection doesn't necessarily mean your film is bad. Common reasons include:
It didn't fit the year's themes or programming needs
The runtime made it hard to slot, especially if it's a long short
The festival already had too many films similar in topic, tone, or style
There were simply more strong films than available slots
Use rejections as data, not judgment. If you consistently hear similar feedback from multiple sources (e.g., "too long," "confusing"), that's a sign to reassess the cut or your targeting strategy.
Q5: Should I email programmers before or after I submit?
A brief, respectful email can sometimes help, especially for smaller festivals:
Before submitting:
You can ask, "Given your past programming, does a [X-type] film usually fit your festival?"
After submitting:
It's usually best not to ask for status updates before their decision window.
Do respond promptly and clearly if they request materials or have questions.
Avoid long pitches or pressure. Programmers are busy and appreciate concise communication.
Q6: How many festivals should I apply to?
There's no magic number, but a strategic approach is better than a scattershot one.
Start by defining your goals:
Industry exposure?
Regional visibility?
Thematic alignment (e.g., LGBTQ+, environmental, student)?
Create a list that includes:
A few "reach" festivals (hard to get into)
A solid group of realistic festivals
Some smaller or niche festivals where your film is a particularly strong fit
Budget for submissions and be willing to stop submitting if the results and feedback suggest the film may have reached its natural limit.
Q7: Should I cut a "festival version" of my film?
Sometimes, yes.
If your short is 25-30 minutes, a lean 10-15 minute festival cut can be much more programmable.
Keep the version that's best for:
Online release
Educational or community screenings
Your reel or portfolio
Just be sure your festival cut still stands alone as a complete, satisfying story.
Q8: Does my cover letter, synopsis, or director's statement really matter?
They won't rescue a weak film, but they can:
Help programmers quickly understand your film's core idea and context
Clarify how it fits their mission or specific program
Provide hooks for marketing and Q&As
Keep these materials short, specific, and free of hype. Explain what the film is about, why you made it, and how it might connect with their audience.
If you shape your film and your submission strategy around these six things — clear story, festival fit, solid craft, smart runtime, audience value, and professionalism — you dramatically increase your chances of being the film a programmer fights to include instead of the one they regretfully turn away.achieve your clearly defined goals better than VOD, and at an acceptable level of risk.
