How Long Should a Film Pitch Deck Be?

A film pitch deck needs enough space to make its project understandable at the level the recipient is being asked to consider. Start with any actual submission limit. Within that limit—or when none exists—choose the length by the explanation you need, not a supposedly ideal number of slides.

That is not an invitation to include everything. It is a way to distinguish a necessary sentence from an expensive habit.

The Los Angeles Film School's pitch-deck guide answers its length question in terms of communicating clearly without overwhelming the reader, rather than prescribing a number.[^1] Sundance Collab's feature-film guidance likewise presents its structure as discretionary and asks for readable design.[^2] Neither gives you permission to ignore a particular recipient's requirements. Neither supports deleting a story's logic to reach a number you found elsewhere.

A useful length decision sounds like this: “This version needs a separate story turn because nobody will be there to explain why she changes her mind.” It does not sound like “All decks should be ten pages.”

Give the length a job

Before cutting anything, finish a plain sentence: “After reading this, the recipient should be able to decide whether to…”

Perhaps the answer is read the screenplay. Perhaps it is discuss a directing collaboration or explore a specific development problem. These requests do not require the same explanation. You are not deciding what every future partner will eventually need to know.

Record the reading conditions beside that sentence. Will someone present the deck? Has the recipient read the script? Will other documents arrive with it? Is there a hard page limit, a file-size limit, or only a preference for brevity? A file-size limit is not a page-count recommendation; a page limit is not a word-count target.

When a binding limit makes your current plan impossible, change the selection before changing the type size. Combine repeated work, decide which example carries the argument, and check what the application already asks for elsewhere. Seek clarification when a real requirement is ambiguous. Do not quietly make a supposedly compliant file that is difficult to read.

Without a binding limit, start with a provisional contents plan. Let it change when you discover what cannot be understood yet. This is more useful than drawing an arbitrary set of empty rectangles and trying to make the film fit.

A short paragraph can still omit the important part

Consider a turning-point page for The Return Run, a fictional feature about a bicycle courier named Nell. Nell lost a parcel and allowed her coworker Dev to take the blame. After Dev is fired, she is assigned to return his belongings. Instead, she takes them back to the depot and admits the loss, putting her own job at risk.

Those are the fixed story facts for the following three versions. The film and the page copy are invented; this is a text comparison, not a report of audience testing or a finished designed deck.

Too little explanation

A different route

Nell takes Dev's belongings back to the depot. For the first time, she is ready to face what she has avoided.

This gives us an action and an emotional suggestion. It does not establish what Nell avoided, why Dev's belongings matter, or what the return could cost her. A reader could reasonably invent several films around it: perhaps she is grieving Dev, perhaps they were partners, perhaps the depot is dangerous.

The missing information is not decorative background. It is the relation that makes this action a decision.

More text, much of it doing the wrong work

A different route

The city has been built and rebuilt around its routes: older streets feeding newer roads, narrow lanes opening onto busy junctions, and the depot sitting among buildings from different phases of expansion. Couriers cross these layers every day, moving between the old city and the new. Nell has worked these streets long enough to know their shortcuts. She lost a parcel and let her coworker Dev take the blame. Dev was fired. Now Nell has been assigned to return his belongings. She cycles through streets shaped by years of change, past buildings that tell the city's story, toward the person who paid for her mistake. Then she turns back. Instead of completing the delivery, Nell returns to the depot and admits that she lost the parcel. Telling the truth could cost her own job. In a city always changing its routes, she finally changes hers.

The necessary facts are here. So are several versions of the same city description. The opening delays the human problem; the ending explains a metaphor the action can already carry.

The city might deserve its own treatment elsewhere. This paragraph has not connected its history to Nell's decision. Its repeated description does not become essential because it sounds like a film.

Enough explanation for this page's job

Nell stops concealing what she did.

Nell lost a parcel and let Dev take the blame. After he is fired, she is sent to return his belongings. Instead, she turns back to the depot and admits the loss to their employer, risking her own job rather than completing one more delivery that conceals what she did.

This revision is longer than the sparse version and shorter than the dense one. Neither comparison is its justification. It retains the responsibility, consequence, and choice that the page needs to convey, while removing the repeated city history.

It has not added a better plot to make the edited version seem stronger. Dev is still fired; Nell still caused the loss; she still confesses at risk to her job. Whether the employer believes her, and what happens to Dev afterward, belongs to the story's next movement. This page need not answer everything, but it must not conceal what its own action means.

Ask what disappears with the sentence

The removal test is simple: take out a passage and name the understanding that goes with it.

Remove “Nell lost a parcel and let Dev take the blame,” and her return loses its moral cause. Remove “risking her own job,” and the decision loses an immediate cost. Remove the second description of the city's layered streets, and this turning point remains intelligible.

Do not use the test to declare every atmospheric sentence wasteful. A description can establish the experience being proposed. If the approach page explains that the city is heard only from Nell's moving position, a passage about sound and movement may be doing specific cinematic work. That does not mean the same passage also belongs on every story page.

Separate three possible dispositions for material you remove. Some is unnecessary and should be cut. Some answers a worthwhile question that belongs later. Some belongs with a particular claim and must move with it.

For example, “depot exterior identified; interior access unconfirmed” cannot become “depot identified” merely because the qualification is inconvenient. Either keep the whole statement or remove the claim from this version. Moving the caveat to a distant appendix while leaving a confident location claim in the main deck changes what you are saying.

A compact working note can record the decisions:

The table is an editing record, not a required slide. It prevents “shorter” from becoming a reason you can apply indiscriminately.

Eight pages for a live conversation; eleven for independent reading

Here are two deliberately bounded plans for the same invented film. Neither is an industry norm. In both, the next request is a screenplay read followed by a development conversation. The difference is whether the maker can supply part of the explanation aloud.

The eight-page live aid has these jobs:

A live aid is not an excuse to hide qualifications in speech. Page 7 still distinguishes confirmed facts from plans. The presenter supplies explanation, not a different project reality.

The eleven-page read-alone plan distributes that same argument differently:

The additional space carries three separations. The story's cause and turning point no longer share one spoken explanation. The filmmaking principle and its representative sequence have room to relate. Current project facts and the question proposed for development no longer depend on a presenter distinguishing them.

Eleven is not inherently more complete. The eight-page file could carry all that explanation with another layout. The eleven-page file could still be full of vague claims. These plans illustrate where the work goes; they do not establish a race to either count.

Nor should every heading become a page automatically. An actual page may hold two closely related jobs. An image sequence may need more than one. Keep the overall plan flexible enough to give consequential material room without multiplying title pages that do no work.

Check the decision you are preparing, not every possible question

After editing, read the file under the conditions you have chosen. For an independent-reading version, close the speaker notes. For a live aid, rehearse the spoken explanation with the actual pages. Do not test one use and assume you have tested the other.

A useful check on the courier page is to ask an unfamiliar reader what Nell does, why she does it, and what she risks. Ask them to point to the material that supplied each answer. These are instructions for an exercise, not results obtained for our invented pages.

If they cannot account for her responsibility, inspect the causal link. If they can explain the decision but want to know whether Dev forgives her, that may be a question for the subsequent story page or screenplay. If they cannot tell whether the depot is secured, the status wording needs attention. Different unanswered questions require different repairs.

Do not ask only whether the deck feels too long. Find the passage where attention loses its object, the page whose purpose is unclear, or the missing explanation the reader had to invent. A global reaction can start the discussion; a specific observation can guide the edit.

Stop when the remaining material supports the intended decision and its qualifications remain intact. For The Return Run, you can now explain why the independent file has eleven pages, why the turning point regained a sentence, why the city-history repetition was cut, and why detailed staging was deferred. That is a defensible length—not a number waiting to be obeyed.

Sources

[^1]: The Los Angeles Film School, “The Ultimate Guide to Creating Your Film/TV Pitch Deck”, FAQ “How Long Should a Film Pitch Deck Be?” The cited answer is general instructional guidance, not a study establishing an optimal length. The removal test and fictional page plans here are original editorial teaching examples.

[^2]: Sundance Collab, Pitch Deck for Fiction and Nonfiction Feature Films, page 1, opening note and design guidance. Text and page 1 inspected. Neither this resource nor the example page plans replace a recipient's specific requirements.

Frequently asked questions

Is there an ideal number of slides for a film pitch deck?

No. Start with any actual submission limit. Within that limit, or when none exists, choose length by the explanation the recipient needs rather than a supposedly ideal number of slides. The cited guides answer length in terms of clear communication and readable design, not a prescribed count.

How can I decide which passages to cut?

Use the removal test: take out a passage and name the understanding that goes with it. Remove the fact that Nell caused the parcel loss, for example, and her return loses its moral cause; remove the risk to her job, and the decision loses an immediate cost. A repeated account of city expansion can be cut if the turning point remains intelligible, but atmospheric description may stay if it does specific cinematic work.

Why might a read-alone deck be longer than a live deck?

A live presenter can supply transitions, detail, emphasis, and answers aloud. A read-alone deck must carry enough context itself. The article's deliberately bounded plans for one fictional film compare an eight-page live aid with an eleven-page read-alone plan; the extra space separates story cause from turning point, filmmaking principle from representative sequence, and project facts from the proposed development question.

What should I do if a binding page or file-size limit conflicts with my plan?

Change the selection before changing the type size. Combine repeated work, decide which example carries the argument, and check what the application already asks for elsewhere. Seek clarification when a real requirement is ambiguous. Do not quietly make a supposedly compliant file that is difficult to read.

How do I know when to stop editing?

Stop when the remaining material supports the intended decision and its qualifications remain intact. Check the file under the conditions it will be used: close speaker notes for an independent-reading version, and rehearse the spoken explanation with the actual pages for a live aid. Ask an unfamiliar reader what a character does, why, and what she risks, then ask them to point to the material that supplied each answer.

Further reading

• What Is a Film Pitch Deck—and What Is It For? — Read this first if you need to establish what the deck is for and which reader decision it must support before choosing a length.
• Your Film Pitch Has a Hook but No Middle. Is the Problem the Deck or the Story? — Read when a deck has enough pages but its middle still feels vague, to separate missing story turns from a synopsis that omitted them.