Three-Point Lighting
Three-point lighting is the classic arrangement of a key, a fill and a backlight around a single subject.
What this is about
As a scheme, three-point lighting is a checklist rather than a style: exposure from the key, contrast from the fill, separation from the back. That makes it genuinely useful where speed matters and the subject does not move — interviews, corporate work, talking heads, product tables. Narrative sets treat it as the thing they build away from, because a drama needs light that comes from somewhere in the room, and actors walk through a space instead of sitting in a chair. Learning the three roles is still worth it: they name what each unit on a complex set is actually doing.
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
Where this differs from the general case:
- The scheme is built for a static subject; the moment an actor walks, the three fixed positions stop working.
- Its three roles remain a useful vocabulary even on sets with twenty units and no recognisable scheme at all.
- A background light is often added as a fourth unit, which is why some crews teach it as four-point.
With TillyGen
For interview days TillyGen can keep one lighting note across setups, so the schedule reflects that the rig is dressed rather than rebuilt.
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
Is three-point lighting outdated?
For drama, largely. For interviews and fast corporate work it remains the reliable default, and it teaches the vocabulary bigger setups still use.
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.