Large Format

Large format is the umbrella term for cinema sensors larger than Super 35, from full-frame class up to 65mm-style sensors.

What this is about

Directors reach for large format when the story wants presence: faces rendered with gentle perspective, backgrounds that fall away softly, landscapes with visible depth layering. The format's demands scale with the sensor — fewer lens options, higher rental tiers, larger data volumes and focus tolerances that punish sloppy blocking. Productions that choose it usually decide early and build the visual concept around it, because retrofitting a large-format look onto a Super 35 plan changes lenses, lighting levels and even location choices.

A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.

What runs differently here

In planning terms, that means:

  • Large format is a class, not one size: full frame, VV and 65mm-style sensors all live under the label.
  • The signature is perspective and separation at moderate stops, not resolution alone.
  • Every step up shrinks the pool of covering lenses and raises the rental line.

With TillyGen

In the production plan a large-format choice propagates into data, lens and lighting lines, so the budget reflects the sensor before the first shooting day.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.

Frequently asked

When is large format worth the extra cost?

When the visual concept needs its rendering — intimate faces, layered landscapes, soft separation. If the film lives in fast coverage and VFX-heavy plates, Super 35 often serves better.

How long does it take to get started with TillyGen?

A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.

Can the results be exported?

Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.