Questions and thoughts about shot planning
The shot list is rarely something the cinematographer builds alone — at least not without input from the director, and not the version that ends up on set. It develops in conversation: ideas about the emotions a scene wants to transport, perspective, blocking, pacing, what the scene is really about visually. The tool you use should support that conversation, not get in the way of it.
There are three common approaches:
PDF export. You build the shot list, export as PDF, email it. Simple and universal.
Cloud platforms. Several tools let the director join your project online. Works for team-heavy productions, but the director needs an account, sometimes a paid seat, and your screenplay lives on someone else's server..
Share package. If your director is also building or editing the shot list — or if you want to hand off a fully editable project — CINEside lets you export a .cnsf share package. It contains the project and all reference images in a single file. The other person opens it in CINEside, chooses a name and location, and continues working on it as a normal project. Private notes are stripped before sending.
Companion app. CINEside CONNECT takes a different route for annotation. You export a .cnct package, your director opens it in CINEside CONNECT — a free companion app — adds notes to shots, script passages, and reference images, and sends their notes back as a separate file. The director doesn't pay or sign up for anything and your script never goes through a cloud. CONNECT is read-only — it's designed for reviewing and annotating, not for editing the project itself.
Whichever approach you choose, the deeper question is the same: how do you keep the conversation alive when the director and cinematographer aren't in the same room? Especially in early prep — when ideas are still moving and the script is still changing — that question shapes the whole process.
Yes. Most modern shot-list tools are cloud-based. They sync across devices and let teams collaborate from anywhere. Your screenplay lives on their servers, and you need a stable internet connection to work.
For some productions, that's fine. For others, it's not an option at all. Sometimes it's the legal side — franchises, studio projects under NDA, unreleased material where the producer rules out cloud tools on day one. Other times it's simply where you're shooting. Remote locations where connectivity is bad or non-existent. Even when there's signal, a laptop in sand, rain, or snow is its own problem. Electronics and the elements don't mix. Some filmmakers also simply prefer a printed script once shooting begins — and offline prep fits naturally into that workflow.
The offline options on Mac are narrower. CINEside is built specifically around this — your script, shots, references, and notes all stay on your machine. Works the same way at your desk, on a mountain, or on a plane. Other offline-capable apps focus on specific aspects of prep, like camera diagrams or blocking. Spreadsheets and paper remain valid choices, especially for smaller productions — just harder to keep in sync across revisions.
If you mostly work where cloud is fine and you always have a connection, web tools have their advantages. If you regularly handle NDA-protected scripts, work in remote locations, or shoot in rough conditions, offline isn't just a preference — it becomes a requirement.
Yes. Most modern tools accept PDF exports from screenwriting software — Final Draft, WriterDuet, Fade In, Highland, Celtx, or anything else. You export your screenplay as PDF from your writing tool, then import that PDF into the shot-list app.
The quality of the import varies. A good one detects scene headings automatically, keeps the script text searchable rather than a flat image, and handles revised drafts — when a new version comes in, it can match it against your existing project and keep your shots, notes, and references attached to the scenes that still exist.
That last part matters more than it sounds. Screenplays change during prep, sometimes heavily. On Tales of Franz, the script kept evolving right up to the start of principal photography — and in a good way. A lot of the changes came directly out of the shot-list work with the director. When you sit down and picture what you want to see on screen for a scene, you start thinking differently about the whole film. Questions come up that aren't really about the shot list — they're about the story, the character, the structure. Those conversations feed back into the script.
At the time, I didn't have the right tool yet. I assembled photos and text fields across different apps and stitched them into a PDF. Every new script version meant adapting the whole system by hand. When the AD needed the shot list in a different format, I did the reorganizing manually. Some days I felt more like an office administrator than a cinematographer. That's one of the reasons I started building CINEside.
CINEside handles screenplay revisions with a two-mode import — full replacement for major rewrites, or a revision merge that keeps your work attached where scenes still match. A review step lets you confirm anything that's ambiguous. The goal is simple: you should be able to welcome a new draft instead of dreading it.
With the script. Not with the shot list tool, not with a camera diagram.
First I try to read it as the audience, not as a cinematographer trying to find ideas. Then after talking enough with the director about how they want to tell the story — and when I'm sure I understand enough of those impulses — I start thinking about visual ideas. Only after reading the script several times do I begin a scene-by-scene process.
I read through each scene the way an audience will eventually experience it, without thinking about the camera yet. What is the scene really about? What does it want the audience to feel? Where is the tension, the turning point, the thing that lies underneath? That reading — before any technical decision — shapes everything that follows.
Only then do I start thinking about where to eventually put the camera. Not "what shot do I need here" but "which perspective feels right for it." Sometimes that's an obvious choice. Sometimes it takes a while, and sometimes those ideas are changed multiple times and then done differently on the shooting day. But it is all valuable for the process.
The shot list itself comes out of that process — it's a record of decisions already made, not a place to make them for the first time. If I'm staring at an empty shot list wondering what to write, it usually means I haven't spent enough time with the scene yet.
In practice: I go scene by scene, in script order, and note the shots that feel necessary. I try to keep it lean — only what I actually need to tell the story, not everything I could theoretically do. A long shot list isn't a sign of good preparation. It's often a sign of uncertainty.
Once I have a rough pass, I look at the whole thing from the outside: does it hold together? Does the visual approach stay consistent? Are there scenes where I haven't really committed to a perspective yet?
The shot list is never finished before the shoot. It changes on location scouts, in conversations with the director, on the day. The goal isn't a complete document — it's a clear enough picture of the film that you can make good decisions when things change, and to give your collaborators enough information for their work.
It depends on how you work.
Some cinematographers prep extensively, with detailed shot lists, shooting scripts, references, lighting plans. Others keep most of it in their head and rely on the AD to make sure nothing gets missed. Some prefer a single notebook over any digital tool. None of these are wrong, and the choice is partly about temperament: some people think clearer when everything's written down, others when it isn't.
What does seem to help across most workflows is having one place where the script and the shots or ideas sit next to each other. Whether that's a paper screenplay with handwritten notes in the margins, a spreadsheet with scene numbers in one column, or a dedicated app — the principle is the same. Information flows back and forth between scene and shot, between intent and decision, all through prep. Splitting that across separate files or apps is where things tend to break down.
What matters most to me, beyond all the technical details and the structure and the scheduling: I never want to lose sight of why we're doing this. It's the emotions a film wants to carry, the creative decisions, the way a scene will eventually be felt by an audience in the cinema. Keeping the script connected to the visual ideas helps me hold on to the whole picture — not just the shots and the schedule, but what the film is really about.
That's why I prefer to have both layouts available during prep — the shot list as a flat sequence, and the shooting script as a marked-up screenplay — each useful for different conversations. The shot list when planning the day with the AD, the shooting script when discussing intent with the director or a department. CINEside lets you build both simultaneously, anchored to the same screenplay. But the more important thing is finding the workflow that actually fits the way you think — and the way you feel about the film.
Yes — and a lot of times, this is just how my early prep happens.
Much of my recent work begins long before anyone is in the same room. The director might be in Los Angeles, in Texas, in Stockholm, while I'm in Munich. We talk over video calls, we share script ideas and references, sometimes we build the early shot list across time zones. What used to mean weeks of back-and-forth over email is now genuinely workable.
What makes it work — or not — is how easily ideas can be shared and built on without losing context. A reference image without the scene it belongs to is just an image. A note about a shot without the script passage it relates to is hard to act on later. Whatever tools you use, the goal is to keep everything connected: the script, the shots, the visuals, the notes from the conversation — all in one place that both of you can see.
I took this remote process further than ever on There There, a film about emotional distance between people. With director Andrew Bujalski, we made a deliberate choice to mirror the story's themes in how the film was shot: actors never met their counterparts on screen, each one isolated in a different location, sometimes thousands of miles apart. Andrew and I were never on set with them. Every "location" in the script was actually two different real places. Scenes were shot weeks or months apart, edited together later. The whole prep process was remote by design — and it surfaced exactly the kind of organizational challenge that prompted me to start building CINEside.
There There was an extreme case — but it surfaced exactly the kind of challenge that CINEside is built for. The director gets a package file, opens it in CINEside CONNECT, and adds notes directly to shots, script passages, and reference images. You import the notes back, see them all highlighted in context, and respond. No accounts, no shared servers, no syncing problems. The screenplay and everything around it stay between the two of you.
No — and it's not meant to.
Cinematographers already use specialized tools for specific tasks: Helios or PhotoPills for sun position, Shot Designer for camera diagrams and blocking, Artemis for framing and lens previews. Each of these does its one thing very well, and replacing them isn't the goal.
CINEside is built around the screenplay — a place to bring everything together. Research the sun position in Helios, take a screenshot, drop it into the Sun Position field. You export a sketch from Shot Designer and drop it into the Sketch field. Reference images from anywhere — paintings, photos — go into scenes or individual shots. The shot list, the script, and the visual material from your other tools sit side by side, ready to share with your director, your gaffer, your AD.
That's how I work myself, and it's part of why CINEside is built the way it is — not as a replacement for the tools I already trust, but as the place where their outputs come together with the script.
No — it depends on the tool.
Subscription-based tools charge monthly or yearly. Most web-based tools are subscriptions by default. The model makes sense if you're a production company with parallel shoots and teams that need to collaborate, or if you want every feature update as it ships. The tradeoff is continuity — your access to the tool, and often to your files inside it, depends on keeping the subscription active.
One-time purchase tools let you pay once and keep the software. CINEside is €79 in early access — a one-time purchase, with free updates and no subscription. Older desktop tools sometimes work this way too. This model makes sense for individual cinematographers who prep a project, wrap it, and may not touch the tool for months between jobs. Your projects stay openable as long as the app still runs on your Mac.
Free and freemium tiers exist on some platforms — usually limited to a single project, a single scene, or a basic feature set. These work well for trying things out, for short-form work, or for commercials and music videos where the scope fits within the limits. For longer, more complex productions, the paid tiers usually become necessary.
The right answer depends on how you work. A working cinematographer who preps a handful of projects a year often gets more value from a one-time purchase — the cost is small and the project files stay openable years later. A production company with parallel shoots and teams that need to collaborate may find the recurring features of a subscription worth the cost. Different workflows, different tools.
Depends entirely on the app.
Cloud-based tools upload your screenplay to their servers. That's how they enable team collaboration and access from anywhere. If you're working with material that needs to stay confidential, it's worth understanding where exactly the file lives and who has access to it.
Offline tools like CINEside store everything locally. Your screenplay never leaves your computer unless you explicitly send it.
But "send it" matters. The moment you email a project file to your director, it's no longer strictly offline — it passes through your mail server, theirs, and whatever services handle the transit. If that's a concern for a particular project, there are safer ways to hand over a file: a USB stick passed directly, an encrypted drive, or a secure file-transfer service your producer has approved. Offline tools don't force you into the cloud, but they don't solve the question of how you move files. That part stays with you.
For pre-release productions, franchise work, or anything under strict NDA, offline storage is the professional standard. Many studios and showrunners require it.
Not yet. CINEside is currently a Mac-only application.
Most of the people I've worked with use a Mac — that's where I focused first.
A Windows version isn't ruled out for the future. If demand is there and the technical path makes sense, it's something I'd consider. For now, CINEside runs only on Mac (macOS 10.13 or newer, Intel and Apple Silicon).
If you're a Windows user and CINEside is something you'd want — drop me a line at info@cineside.app. It helps to know.
No — CINEside is a desktop application for Mac only.
Building a shot list is detailed, layered work. Importing screenplays, anchoring shots to specific passages, dragging in references and floorplans, writing department notes — it's the kind of thinking that benefits from a real screen, a keyboard, and the focus a desktop or laptop gives you. On a phone or tablet, the interface would have to be cut down so far that the depth of the tool gets lost.
What works well on mobile is viewing. Once your shot list is built, you can export it as a PDF — facing pages with script and shots, just the shot list, or a notes sheet — and send that PDF to your iPad or iPhone for reference on set. There's also a dedicated iPad / Tablet PDF format with larger text and a wider margin on script pages, designed for Apple Pencil annotations.
The work itself happens at the desk — and what you bring to set is the PDF.
Further reading: CINEside User Manual ↗ — complete feature reference, all export options, keyboard shortcuts.
Written by Matthias Grunsky, cinematographer. CINEside grew out of my own preparation work over the past years.
Questions, suggestions, or things you'd like to see covered here? info@cineside.app — every message is read personally.
© 2026 Matthias Grunsky · CINEside