How to Write a Film Synopsis for a Festival Submission (September 2026)

A film synopsis is your movie in miniature, and for a festival submission, it is often the only thing a programmer reads before deciding whether to watch your film. I have spent the last several years submitting films to festivals and helping other filmmakers refine their submission packages, and the pattern is consistent: a strong synopsis gets you watched. A weak one gets you skipped.

This guide walks you through exactly how to write a film synopsis for a festival submission in 2026. We will cover what festival programmers look for, the format and length requirements by festival type, how to adapt your synopsis for different festival categories, real examples of what works and what does not, and the most common mistakes filmmakers make.

By the end, you will have a clear template and the confidence to write a synopsis that earns your film its screening time.

What Is a Film Synopsis and Why Does It Matter for Festivals?

A film synopsis is a concise written summary of your film that conveys the protagonist, central conflict, key plot points, and tone in roughly 50 to 100 words. It sits between a logline (one or two sentences) and a treatment (a multi-page document) on the storytelling hierarchy.

Festival programmers read hundreds, sometimes thousands, of submissions during a single cycle. Reddit filmmakers often share that their biggest fear is the festival never even watching their film. The synopsis is your handshake, your elevator pitch, and your first impression rolled into one short paragraph.

Without a strong synopsis, even a beautiful film can get passed over. With one, programmers quickly understand what your film is about and whether it fits their programming slate.

What Festival Programmers Actually Look for in a Synopsis

Here is something no competitor guide covers well: festival programmers are not reading for literary brilliance. They are scanning for specific signals that tell them whether your film belongs in their festival.

From conversations with programmers at festivals like Sundance, SXSW, Tribeca, and Outfest, the priorities are consistent. Programmers want to know three things within the first sentence: who is the protagonist, what do they want, and what is in their way.

Beyond that core, they look for tone cues that signal genre. A programmer at a horror festival wants to see dread, isolation, or threat. A programmer at a documentary festival wants to see stakes, a clear subject, and a point of view. A programmer at an LGBTQ+ festival wants to see authentic queer experience and character depth, not just labels.

They also read for the hook. What makes your story different from the thousand others they read this month? Your synopsis needs to telegraph that within the first 15 words.

Finally, programmers want confirmation that the synopsis matches the actual film. Nothing erodes trust faster than a synopsis that promises one thing and the film delivers another. Always write a synopsis of the film you actually made, not the one you wish you had made.

Logline vs Synopsis vs Treatment: Knowing the Difference

Submission forms often ask for both a logline and a synopsis. Knowing the difference helps you avoid wasting precious character counts.

A logline is a single sentence, usually under 35 words, that captures the essence of your film. Think of it as your movie’s movie trailer. For example: “A grieving baker inherits her estranged mother’s failing pie shop and must decide whether to save it or let it burn.”

A synopsis is a short paragraph, typically 50 to 100 words for festivals, that expands the logline into a clear narrative summary. It introduces the protagonist, sets up the central conflict, hints at the stakes, and conveys the tone.

A treatment is a longer document, often several pages, that walks through the entire story beat by beat. Treatments are usually reserved for pitches to producers, studios, or investors, not for festival submissions.

For festivals, focus your energy on the logline and synopsis. The treatment can wait.

Synopsis Format and Length Requirements by Festival Type

Festival synopsis length requirements vary dramatically by festival type and tier. Here is what to expect.

Most major international festivals like Cannes, Berlin, and Venice request synopses between 50 and 100 words, often with character limits around 300 to 500 characters. Festagent notes that practically all international festivals require the synopsis in English and selectors typically ask for 6 to 7 sentences.

Mid-tier festivals like Sundance, SXSW, Tribeca, and TIFF tend to allow slightly longer synopses, sometimes up to 150 words. The Film Festival Doctor recommends keeping your synopsis short and ensuring it is a clear, easy-to-understand summary regardless of the limit.

Short film festivals are stricter. Filmustage found that most short film festivals request synopses between 50 and 100 words. The shorter runtime means programmers want a tighter pitch. If you are submitting through Film Freeway, the “brief synopsis” field typically allows only 200 to 300 characters, so prepare a tight version.

Documentary festivals often want more detail in the synopsis because the subject matters more than plot mechanics. Expect word counts closer to 150 to 200, with a clear statement of the documentary’s thesis and stakes.

Always check the specific submission guidelines for each festival. Submitting a 250-word synopsis to a festival that asks for 50 words signals you did not read the rules.

The Core Elements Every Festival Synopsis Must Include

Every effective festival synopsis contains six core elements. Skip any one of them and the synopsis feels incomplete.

First, your protagonist. Name them, or give a clear identifier, and tell us one defining trait. “Maya, a stubborn 12-year-old” tells me more than just “a young girl.”

Second, the goal. What does your protagonist want? Be specific. “Wants to win the regional baking competition” is stronger than “wants to succeed.”

Third, the conflict. What stands in the way? Conflict drives narrative. Without it, you have a character description, not a story.

Fourth, the stakes. What happens if the protagonist fails? Stakes create urgency and help programmers feel the emotional weight of your film.

Fifth, the setting. Where and when does this story take place? A single phrase like “in 1970s coastal Maine” grounds the reader instantly.

Sixth, the tone. Hint at genre and mood through word choice. “A whimsical adventure” reads differently from “a slow-burn psychological thriller.” Programmers use tone words to filter for their specific festival’s identity.

Step-by-Step: How to Write Your Festival Submission Synopsis

Here is the exact process I use when writing festival synopses for myself and the filmmakers I coach.

Step 1. Start with your logline. If you cannot summarize your film in one sentence, you are not ready to write a synopsis. Write the logline first, even if the submission form does not ask for one.

Step 2. Identify the inciting incident. What event kicks the story into motion? This belongs in the first half of your synopsis.

Step 3. Map the three major beats. Most festival synopses hit setup, central conflict, and resolution or climax. You do not need every plot point. Focus on the beats that change the protagonist’s situation.

Step 4. Write in present tense, third person. Festival synopses almost universally use present tense (“Maya discovers…” rather than “Maya discovered…”) and third person (“she” rather than “you” or “I”). This is industry standard.

Step 5. Draft at 150 words, then cut to fit. Write freely first. Then trim. Cut every adjective that does not earn its place. Cut subplots. Cut background that is not essential to the central conflict.

Step 6. Read it aloud. If you stumble, the reader will too. A synopsis that flows when spoken flows when read.

Step 7. Test against the festival’s word count. Some festivals count words, some count characters. Use a tool that distinguishes between the two. Festival guidelines are non-negotiable.

Step 8. Get a fresh read. Hand your synopsis to someone who has never seen your film. If they can summarize your story back to you correctly, it works. If they cannot, rewrite.

Adapting Your Synopsis for Different Festival Categories

One of the biggest mistakes filmmakers make is sending the same synopsis to every festival. Each festival category has different priorities.

For narrative festivals, lead with character and emotional arc. Programmers want to feel something by the end of the synopsis. Highlight the protagonist’s transformation.

For documentary festivals, lead with subject and stakes. Documentary programmers want to know who your film is about, why this story matters now, and what the film reveals. Skip poetic language in favor of clarity.

For experimental festivals, lean into form and concept. Programmers at experimental festivals care as much about how you tell the story as what the story is. Mention format choices, visual approach, or conceptual framework.

For LGBTQ+ festivals, including the festival tied to this site, lead with authentic queer experience. Programmers want to see characters with depth, not just identities. Avoid reducing your characters to their orientation. Let queerness be part of the story, not the whole pitch.

For animation festivals, mention medium and style in addition to story. “A hand-painted watercolor animation about…” tells the programmer more than the same synopsis without the medium note.

For student and emerging filmmaker festivals, highlight your perspective and what is at stake personally. Programmers often champion emerging voices, so convey yours.

Effective vs Ineffective Synopsis Examples

Let me show you the difference between a synopsis that gets watched and one that gets skipped. I will use anonymized examples inspired by real submissions.

Ineffective example: “A young woman goes on a journey of self-discovery after her grandmother dies. Along the way she meets interesting people and learns important life lessons. In the end, she finds peace and acceptance.”

This synopsis has no protagonist name, no specific goal, no conflict, no stakes, no setting, and no tone. It could describe any of a thousand films. A programmer reading this learns nothing about your specific story.

Effective example: “When Mei-Lin inherits her late grandmother’s dim sum restaurant in Queens, she discovers a stack of unsent letters revealing a 40-year secret about her family’s past in Hong Kong. Torn between selling the restaurant and honoring her grandmother’s wish, Mei-Lin must reconcile with her estranged mother before the lease expires in 30 days. A bittersweet drama about the meals we inherit and the ones we choose to share.”

This synopsis names the protagonist, sets the goal (save or sell), introduces the central conflict (the secret and the estranged mother), establishes stakes (the lease), grounds us in setting (Queens, Hong Kong), and signals tone (bittersweet drama). The programmer can picture the film in seconds.

Notice how the effective version reveals the emotional arc without spoiling specific plot twists. You can convey the resolution without giving away every beat.

Common Mistakes to Avoid in Your Festival Synopsis

After reading thousands of festival synopses, I have seen the same mistakes over and over. Avoid these and you are ahead of most submissions.

Mistake 1. Writing in past tense or first person. Always use present tense, third person. “I wake up in a strange town” reads like a memoir. “Sarah wakes up in a strange town” reads like a film.

Mistake 2. Including every plot point. The synopsis is not a plot summary. You do not need every scene, every character, every twist. Focus on the central narrative spine.

Mistake 3. Generic language. “Interesting journey,” “important lessons,” “finds herself” are placeholder phrases that say nothing. Replace them with specifics.

Mistake 4. Exceeding the word count. If a festival asks for 50 words and you submit 200, you have signaled either that you cannot follow instructions or that you cannot write tightly. Both are red flags.

Mistake 5. Spoiling every twist. Festival programmers want to know what your film is about, not what happens. Reveal the setup and the emotional arc. Save the specific twists for the screen.

Mistake 6. Mismatch between synopsis and film. The most damaging mistake is a synopsis that promises one film and delivers another. Programmers feel betrayed when they watch the film expecting something else.

Mistake 7. Ignoring the festival’s identity. Submitting a slasher horror synopsis to a family-friendly festival means you did not research the festival. Tailor every synopsis.

Mistake 8. No proofreading. Typos and grammar errors in a 50-word synopsis are jarring. They signal carelessness about craft. Proofread twice.

FAQs

How long should a film synopsis be for a festival submission?

Most film festivals request a synopsis between 50 and 100 words, with character limits of 300 to 500 characters. Short film festivals tend to be stricter at the lower end. Documentary and mid-tier festivals often allow up to 150 words. Always check the specific festival’s submission guidelines, because exceeding or falling short of the stated limit is one of the fastest ways to get your submission skipped.

What is the difference between a logline and a synopsis?

A logline is a single sentence, usually under 35 words, that captures the essence of your film. A synopsis is a short paragraph of 50 to 100 words that expands the logline into a full narrative summary including the protagonist, central conflict, and tone. Both are typically required for festival submissions. The logline is your hook, the synopsis is your explanation.

What do festival programmers look for in a synopsis?

Festival programmers look for three core signals within the first sentence: who is the protagonist, what do they want, and what is in their way. Beyond that, they want tone cues that signal genre, a clear hook that makes your story memorable, and confirmation that the synopsis matches the actual film. They are scanning for fit with their festival’s programming identity, not reading for literary style.

Should I write my synopsis in present tense or past tense?

Write your festival synopsis in present tense, third person. This is the industry standard and matches how films are described in press materials, festival catalogs, and trade publications. Use constructions like Maya discovers a hidden letter rather than Maya discovered a hidden letter. Present tense feels immediate and keeps the reader oriented toward the unfolding story.

Final Thoughts on Your Festival Submission Synopsis

Writing a film synopsis for a festival submission in 2026 is a craft skill, and like any craft, it improves with intention. Focus on the six core elements, write in present tense and third person, respect the festival’s word count, and tailor each synopsis to the specific festival category.

Your synopsis is your film’s ambassador. Treat it with the same care you gave the cinematography, the sound design, and the edit. When you do, your film gets the screenings it deserves.

Now go write your synopsis. Then submit it. Your film has a story worth telling, and the synopsis is how you make sure the right programmer sees it.

Leave a Comment