Commissioned Research
Top 9 Best Shotlist Software of 2026

GITNUXSOFTWARE REVIEW

Art & Design

Top 9 Best Shotlist Software of 2026

Compare shotlist software options with practical tradeoffs for film teams, from CuePilot, SetHero, and Flow Production Tracking workflows.

19 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Shotlist software matters because it turns scene breakdowns into an operational data model that production teams can review, update, and route through departments. This comparison helps analysts and operators weigh planning depth against review throughput and integration needs when coordinating shot cues, camera rundown, and asset-linked tasks across the production pipeline.

CuePilot is the best choice for mid-size teams that need shot-focused review cycles, because shot-level feedback is tied to each planned item and revision so comments always map to the exact sequence; Flow Production Tracking is the better fit for enterprise workflows with governed, role-based shot status across departments.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

CuePilot

Shot-level review tied to shot status and shot list revisions, so feedback maps to the exact planned item.

Best for: Fits when mid-size teams need shot-focused review cycles with clear version control.

2

Flow Production Tracking

Editor pick

Shot status workflows that connect planning records to production progress with governed role permissions.

Best for: Fits when production tracking must drive shot status across departments with governed permissions.

3

SetHero

Editor pick

Storyboard linkage that maintains alignment between review comments and specific shot entries during shot status changes.

Best for: Fits when mid-size crews need shot planning, storyboard-linked review, and controlled updates across departments.

Comparison Table

1
CuePilotBest overall
vertical specialist
9.1/10
Overall
2
8.9/10
Overall
3
8.8/10
Overall
4
vertical specialist
8.3/10
Overall
5
8.1/10
Overall
6
enterprise
7.9/10
Overall
7
enterprise
7.6/10
Overall
8
vertical specialist
7.0/10
Overall
9
vertical specialist
6.8/10
Overall
#1

CuePilot

vertical specialist

Live production planning software with shot cueing, camera rundown, and visual sequence coordination.

9.1/10
Overall
Features9.1/10
Ease of Use9.1/10
Value9.1/10
Standout feature

Shot-level review tied to shot status and shot list revisions, so feedback maps to the exact planned item.

CuePilot’s core workflow centers on building a shot list, attaching notes to specific shots, and using a consistent review flow during production. The product includes shot status workflow and revision tracking so teams can manage progress and see what changed between versions. Shot-level collaboration and organized comments keep feedback tied to the exact planned item rather than a general project thread.

A key tradeoff is that CuePilot’s workflow is tightly oriented around the shot list and shot review loop, which can feel narrow for teams expecting deep departmental calendars or broad interchange formats. CuePilot fits best for productions that need quick update cycles between the shot list owner, the script supervisor, and the on-set review process during day-out-of-days.

Pros
  • +Shot-status workflow ties on-set progress to each planned shot
  • +Revision tracking keeps review feedback aligned to the correct shot list
  • +Card-style shot review reduces searching across long lists
  • +Collaboration stays focused on shot-level notes and decisions
Cons
  • –Shotlist-first design can be limiting for projects needing broader scheduling depth
  • –Interchange and export options may require extra process for advanced pipelines
Use scenarios
  • Line producers

    Track shot completion during daily review

    Fewer missed deliverables

  • Script supervisors

    Keep notes aligned to the current cut

    Cleaner continuity records

Show 2 more scenarios
  • Camera and assistant teams

    Review planned items on set

    Faster feedback loops

    Crew can work from the same shot review flow while updating shot status.

  • Post-production coordinators

    Route takes to the correct plan version

    Reduced rework

    Coordinators can link review outcomes to the revision that drove each shot decision.

Best for: Fits when mid-size teams need shot-focused review cycles with clear version control.

#2

Flow Production Tracking

enterprise

Production tracking software for shots, assets, tasks, reviews, and department workflows.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

Shot status workflows that connect planning records to production progress with governed role permissions.

Flow Production Tracking from Autodesk ties shot planning to production status so teams can track progress from outline to set and onward to delivery. It centers on production tracking workflows, custom fields, and permissions tied to roles, with integrations that connect production data to Autodesk ecosystems.

Shot-list usage is supported through structured shot records and exportable planning outputs that can feed scheduling and review loops. Automation comes through configurable processes and API-accessible data objects that reduce manual re-entry when shot data changes.

Pros
  • +Role-based access controls cover departmental work states and review ownership
  • +Configurable workflows keep shot status aligned with production progress
  • +API and automation support reduce retyping when shot plans change
  • +Structured shot records support consistent planning outputs across departments
Cons
  • –Shot list presentation depends on configuration, not a dedicated shot planning UI
  • –Complex setups can require governance discipline across many custom fields
  • –External review formats may need additional export or mapping steps
  • –Dense workflow customization can slow onboarding for small teams
Use scenarios
  • Film production tracking leads

    Map shots from outline to delivery

    Clear progress across milestones

  • Production schedulers

    Sync shot updates into schedules

    Less manual schedule churn

Show 1 more scenario
  • Post-production coordinators

    Route reviews using role permissions

    Fewer review mismatches

    Apply permissions tied to roles so stakeholders review the correct shot revisions during production cycles.

Best for: Fits when production tracking must drive shot status across departments with governed permissions.

#3

SetHero

SMB

Film production software for schedules, call sheets, crew coordination, and shot planning.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

Storyboard linkage that maintains alignment between review comments and specific shot entries during shot status changes.

SetHero is shotlist software that converts a script into a navigable shot planning workspace with review-ready pages. It supports shot list templates, shot number sequencing, and versioned shot status so teams can move from plan to set and then reconcile updates.

Core workflow relies on configuration of scenes and setups plus export options for handoff to production reporting and continuity tracking. It also supports storyboard linkage so editorial feedback can stay aligned with the shot list during revisions.

Pros
  • +Storyboard linkage keeps editorial notes attached to the matching shot entries
  • +Shot status workflow supports practical on-set progress tracking and reconciliation
  • +Template-based scene breakdown speeds creation of consistent day-out-of-days schedules
  • +Shot list export supports straightforward downstream distribution for departments
Cons
  • –CSV import coverage can be limiting when carrying over dense lens metadata fields
  • –Change history and version diff need consistent admin process to stay readable
Use scenarios
  • Editorial and VFX stakeholders

    Review shots with annotated footage

    Trackable review decisions

  • Production managers and leads

    Compile daily reporting per shoot day

    Consistent handoffs

Show 2 more scenarios
  • Production coordinators

    Plan scenes and daily work blocks

    Fewer scheduling conflicts

    Arrange scenes, cast, and crew while updating the plan as conditions change across shot planning.

  • Producers and finance stakeholders

    Route budget changes through approvals

    Clear approval history

    Maintain estimate versions and review steps so budget edits feed stakeholder reporting with context.

Best for: Fits when mid-size crews need shot planning, storyboard-linked review, and controlled updates across departments.

#4

Boords

vertical specialist

Storyboarding and animatic platform with shot list and frame management capabilities.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Storyboard linkage ties each shot to its visual panel while maintaining revision history for review cycles.

Boords is built around storyboard linkage so every shot has a visual anchor and editable details for blocking notes and production context. The tool’s revision tracking supports iteration across reviews, so changes to shots remain reviewable instead of overwriting prior planning. Shot list export is geared toward sharing with departments that need a stable planning artifact.

Pros
  • +Storyboard linkage keeps visual context attached to each shot
  • +Revision tracking makes shot planning edits reviewable
  • +Scene breakdown creation supports structured planning work
  • +Shot list export supports downstream production documents
Cons
  • –Shot structure setup upfront is needed for consistent exports
  • –Automation depth for custom workflows is limited versus general APIs
Use scenarios
  • Directors and storyboard artists

    Review shot flow against storyboards

    Fewer planning rework loops

  • Production coordinators

    Distribute a controlled shot list

    Cleaner crew handoffs

Show 1 more scenario
  • Script and production teams

    Convert breakdown into shot structure

    Less manual shot formatting

    Teams generate structured scene breakdowns and shot entries from script content for consistent planning.

Best for: Fits when visual shot planning needs disciplined revisions and dependable export for production handoffs.

#5

Celtx

SMB

Scriptwriting and pre-production platform including shot list and storyboard modules.

8.1/10
Overall
Features8.1/10
Ease of Use8.0/10
Value8.2/10
Standout feature

Script-to-shot continuity keeps shot list structure aligned as the script shifts during revisions.

Celtx’s shot list creation is anchored to script content, which reduces manual duplication when a scene changes. Shot planning can include blocking notes and setup annotations per shot, and teams can move through a shared status flow as planning progresses. Celtx’s collaboration layer supports review comments on production documents, which helps catch mismatched coverage before call sheets are printed.

Pros
  • +Script-linked shot lists reduce retyping when scene pages change
  • +Inline shot notes support blocking and setup documentation in one pass
  • +Document review comments support revision loops with fewer handoffs
  • +Shot list export supports distribution to departments that do not edit
Cons
  • –Integration and API coverage for custom pipelines is limited for scale-up teams
  • –Advanced taxonomy controls for shot-type filtering can feel constrained
Use scenarios
  • Directors and writers

    Revise scenes with consistent shot outputs

    Fewer mismatches across drafts

  • Production managers

    Track planning status across scenes

    Clearer readiness per scene

Show 2 more scenarios
  • Script supervisors

    Maintain continuity notes beside shots

    Better continuity capture

    Setup and continuity notes can be placed at the shot level to keep evidence attached.

  • Cinematography teams

    Standardize planning notes for camera setup

    More consistent camera prep

    Shot annotations help document planned lens and setup expectations for the crew.

Best for: Fits when crews want script-driven planning with review comments and shareable shot list exports.

#6

farmerswife

enterprise

Media production management software for scheduling, resources, projects, and production operations.

7.9/10
Overall
Features7.9/10
Ease of Use7.9/10
Value7.9/10
Standout feature

Frame-linked review annotations that attach directly to shot planning revisions during daily review.

Farmerswife focuses on shot list creation and review workflows for production teams, with emphasis on visual planning around each shot. The workflow supports scene breakdown planning, shot numbering, and review notes tied to specific frames so revisions stay traceable through production.

Pros
  • +Frame-linked review notes keep feedback tied to exact shots
  • +Scene breakdown oriented shot planning supports day-by-day revisions
  • +Import and export formats support practical handoffs between tools
  • +Role-based access reduces accidental edits during crew turnover
Cons
  • –Advanced automation and API surface are limited for fully programmatic workflows
  • –Storyboard and lens metadata linkage depth is thinner than dedicated review suites
Use scenarios
  • Media operations teams

    Standardize repeatable production structures

    More repeatable execution

  • Broadcast operations teams

    Coordinate shared facilities and staffing

    Improved resource coordination

Show 2 more scenarios
  • Studio and facility managers

    Manage bookings and shot-related workflows

    Shared operational visibility

    Coordinate studio bookings, equipment requests, media intake, and linked downstream review steps.

  • Pipeline and production operations

    Control handoffs between pipeline stages

    Controlled pipeline movement

    Link department statuses, review outcomes, publishing steps, and notifications across shot-based deliverables.

Best for: Fits when production teams need shot planning with frame-linked review notes and controlled crew permissions.

#7

ftrack

enterprise

Production management software for media teams with shot, task, review, and scheduling workflows.

7.6/10
Overall
Features7.6/10
Ease of Use7.6/10
Value7.6/10
Standout feature

Extensible review and change tracking that links notes to shot-level workflow states via API-driven automation.

ftrack is positioned for production operations that require coordination between planning, review, and downstream departments. It keeps shot work organized through project hierarchy and shot-centric workflow states. The platform also supports API and automation so scheduling and reporting can be driven from the same underlying shot records. Review feedback attaches to the work items being tracked instead of living only in a separate markup tool.

Pros
  • +Shot status workflow supports iterative revisions with visible history
  • +API and automation hooks keep cross-department pipelines synchronized
  • +RBAC and crew permissions reduce access sprawl across large projects
  • +Shot exports and interchange formats fit production handoff needs
Cons
  • –Shot import and mapping needs setup to match existing naming conventions
  • –Review UX can feel administrative compared with shot-by-shot marking tools
Use scenarios
  • VFX supervisors and post teams

    Run structured shot approval rounds

    Traceable approval paths

  • Studio operations and pipeline teams

    Automate shot status reporting

    Less manual status work

Show 2 more scenarios
  • Production operations supervisors

    Attach instructions to shot items

    Consistent access to instructions

    Attach work instructions and revision discussions directly to tracked production items to keep guidance current.

  • Game and digital content teams

    Track revision dependencies across assets

    Visibility into current versions

    Organize media revisions and monitor downstream handoffs by tracking how shot work depends on assets.

Best for: Fits when production teams need shot-status automation and governed access across departments.

#8

Shot Designer

vertical specialist

Camera blocking and shot list application for scene staging with real-time animation.

7.0/10
Overall
Features7.0/10
Ease of Use7.0/10
Value7.0/10
Standout feature

Shot-page workflow that connects scene breakdown work to setup notes used for day planning, with export outputs for production distribution.

Shot Designer is a shotlist and planning tool built for camera-work workflows, with a focus on translating storyboards and script breakdowns into production-ready shot pages. The product centers on scene-based shot numbering, shot status movement, and setup-level notes that support day-out-of-days planning.

Pros
  • +Scene-based shot pages keep numbering and context aligned during revisions
  • +Setup blocking notes reduce handoff gaps between planning and on-set execution
  • +Spreadsheet-friendly exports support crew-facing review and offline edits
  • +Shot status workflow helps track what is scheduled versus still in development
Cons
  • –Automation depth for bulk changes depends on careful upfront configuration
  • –Collaboration controls and audit trails are limited compared with review-first platforms
  • –Template customization can be slower when adding new metadata fields mid-project
  • –External tool integration breadth is narrower than video review ecosystems
Use scenarios
  • Camera-work production teams

    Turn storyboards into shot pages

    Faster shot page preparation

  • Shot pages review teams

    Standardize blocking and lens metadata

    Consistent metadata capture

Show 2 more scenarios
  • Production coordinators

    Plan day-out-of-days with statuses

    Better day-to-day alignment

    Update shot status as setups shift and export review-friendly shot lists for downstream production documents.

  • Downstream document workflows

    Export spreadsheet-friendly shot lists

    Easier downstream handoffs

    Export shot information to support spreadsheet-style review and handoff documents used later in production.

Best for: Fits when shot pages and shot status tracking matter more than review markup and heavy collaboration tooling.

#9

Kitsu

vertical specialist

Production tracking software for animation and visual effects assets, shots, tasks, and reviews.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Entity-linked shot notes that stay attached to each shot across revisions without rebuilding the whole list.

Kitsu manages shot planning by linking storyboard, scripts, and production notes to a shot list workflow. It offers a structured production data model that supports reusable shot templates and scene breakdown organization.

Pros
  • +Per-shot entities keep notes and edits attached to the exact item
  • +Reusable templates reduce friction for recurring shot structures
  • +Scene breakdown organization supports coverage-style grouping
  • +Export flows support handoff to spreadsheet-based review steps
Cons
  • –Shot list exports feel more spreadsheet-centric than production-report tailored
  • –Governance requires consistent setup to avoid permission sprawl
  • –Workflow automation depends on project configuration discipline
  • –Import interoperability is narrower than XML or XMP-based sidecar workflows
Use scenarios
  • Reviewers and artists

    Manage per-shot feedback and approvals

    Current review state visible

  • Production managers and coordinators

    Coordinate milestone-based timelines

    Shared progress visibility

Show 2 more scenarios
  • Producers and department leads

    Coordinate shot and asset pipeline handoffs

    More visible ownership

    Use shared shot, asset, and task records to coordinate ownership as work moves through pipeline stages.

  • VFX studios and post-production teams

    Coordinate shot tasks across disciplines

    Connected task ownership

    Track VFX shot tasks, versions, and review rounds using connected shot-level entities for handoffs.

Best for: Fits when storyboard-to-shot list collaboration needs a structured per-shot record with review and handoff exports.

Conclusion

After evaluating 9 shotlist software, CuePilot stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
CuePilot

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Shotlist Software

How do Boords and Kitsu handle shot numbering and revision traceability when a scene breakdown changes?
Boords ties scene breakdown work to shot numbering and maintains versioned revision history so reviews map to the exact prior state. Kitsu keeps per-shot entities linked to metadata so editorial changes attach to each shot record without rebuilding the list.
Which tools support storyboard linkage that survives shot status workflow changes?
SetHero links storyboard feedback to shot entries and keeps alignment during shot status updates. farmerswife attaches frame-linked review annotations to the planning revision so daily review stays connected to the planned item, including after shot status changes.
When teams need on-set review tied to take-level edits, how do CuePilot and Gorilla Scheduling differ?
CuePilot uses a card-based workflow per take and maps feedback to the exact planned shot item via shot status workflow and revision tracking. Gorilla Scheduling focuses on setup time blocking and day-by-day shooting schedule outputs, so on-set review happens through the schedule and access-controlled plan updates rather than per-take cards.
What breaks if a production requires managed departmental access and governed role permissions across departments?
Flow Production Tracking from Autodesk and ftrack both center on permissions tied to roles, so teams that need governed access find fewer gaps. Tools that rely mainly on shared exports and manual handoffs, such as Boords, increase the risk of departments reviewing stale revisions outside a role-governed workflow.
Which tools provide API access or automation surfaces for shot status and review workflows?
Flow Production Tracking from Autodesk exposes API-accessible data objects and configurable processes that reduce manual re-entry when shot data changes. ftrack emphasizes API-driven automation that links shot-level workflow states to review and change tracking across a pipeline.
How do teams migrate existing shot lists into shot planning systems using imports and export paths?
Boords supports importing breakdown content and exporting shot lists for downstream production documents, which fits migration from older breakdown formats. Shot Designer and Kitsu both focus on export paths that feed review and spreadsheet-style handoffs, which helps when the starting point is a sheet-driven workflow.
When shot status workflow must be coordinated with day-out-of-days planning, how do Shot Designer and Gorilla Scheduling compare?
Shot Designer emphasizes setup-level notes and scene-based shot numbering tied to shot status movement, which supports day planning outputs. Gorilla Scheduling recalculates scheduling impact from setup time blocking when shot statuses or timing inputs change, so it is built around the schedule as the control surface.
Which tool best supports coupling planning data to asset and project hierarchies for consistent shot-centric collaboration?
ftrack uses project and asset hierarchies to keep teams aligned while linking notes to shot-centric work items through statuses and revision workflows. Kitsu also attaches review and changes to per-shot entities, but ftrack’s hierarchy-first model is more explicit for multi-asset production structures.
How do Frame.io-style review loops map onto shot-level planning records in this market?
CuePilot maps review feedback to the exact planned item through shot-level review tied to shot status and revisions. farmerswife links frame-linked review annotations directly to shot planning revisions, which reduces ambiguity about which planned shot the feedback targets.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Shotlist Software

Shotlist software differs most in how well it keeps shots organized end-to-end, especially around the shot list template you start with and the shot list export format you need at the end. We favor tools that track changes across production without turning exports into manual rework.

Template flexibility for your workflow

Why it matters

Template flexibility for your workflow decides whether the system can match how your team labels scenes and shots, or whether you’ll fight the structure every day. This shows up quickly when your first project doesn’t fit the defaults.

How to check

In the demo, create a shot list from a blank template and one from a provided template. Ask whether you can add or rename fields (like scene labels and notes) and keep them consistent across new projects.

Export formats that match your partners

Why it matters

Export formats that match your partners determine whether you can hand off clean shot lists without reformatting. When the output doesn’t match a receiving workflow, the shot list becomes a source of errors.

How to check

Export a sample shot list and inspect the result for ordering, required columns, and readable text. Ask if you can choose between a spreadsheet-style export and a document-style export.

Revision tracking with visible change history

Why it matters

Revision tracking with visible change history matters when schedules move and departments ask what changed. Without usable history, you lose confidence in whether the current shot list is the real one.

How to check

Make two edits to the same shot (e.g., add a note or change status), then check whether the tool shows what changed and when. Ask if the history is exportable or at least viewable per shot.

Importing existing shot lists without loss

Why it matters

Importing existing shot lists without loss prevents re-entry after you switch tools. The risk is subtle: fields shift, columns drop, or shot numbering gets scrambled.

How to check

Import a small CSV or spreadsheet file you already have, then verify every expected column maps correctly. Confirm that ordering and shot labels remain stable after import.

Shot status workflow your team can use

Why it matters

A usable shot status workflow your team can use reduces chasing and ambiguity during production. If statuses are too rigid, you’ll bypass the system and rely on side documents.

How to check

During the demo, set up a few statuses (planned, ready, in progress, filmed) and assign them to shots. Ask whether the tool supports simple progression rules and whether it’s visible in a per-shot view.

Camera and lens metadata handling

Why it matters

Camera and lens metadata handling matters when you attach technical intent to the shot list. If metadata can’t be captured cleanly or exported predictably, it ends up stranded in the editing workflow.

How to check

Add lens and camera-related fields to a shot and verify they validate correctly. Export the shot list and check whether those metadata fields remain intact and readable.

Red flags

  • Exports that reorder shots or drop columns you rely on
  • Revision history that can’t show what changed at the shot level
  • Imports that break your existing shot labels or scene structure

Fit by situation

  • If you already have a spreadsheet shot list to bring over, prioritize importing existing shot lists without loss.
  • If multiple departments need the same current document, prioritize revision tracking with visible change history.
  • If you hand off shot lists to partners in specific layouts, prioritize export formats that match your partners.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.