GITNUXSOFTWARE ADVICE
Art DesignTop 10 Best Shotlist Software of 2026
Ranking roundup of shotlist software with technical criteria and tradeoffs for shot planning and review, featuring Shot Lister and Frame.io.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Boords is the best fit when visual shot planning needs disciplined revisions and dependable export for production handoffs, whereas Celtx works well if your crew prefers script-driven planning with review comments and shareable shot list exports.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Boords
Storyboard linkage ties each shot to its visual panel while maintaining revision history for review cycles.
Built for fits when visual shot planning needs disciplined revisions and dependable export for production handoffs..
Celtx
Editor pickScript-to-shot continuity keeps shot list structure aligned as the script shifts during revisions.
Built for fits when crews want script-driven planning with review comments and shareable shot list exports..
CuePilot
Editor pickShot-level review tied to shot status and shot list revisions, so feedback maps to the exact planned item.
Built for fits when mid-size teams need shot-focused review cycles with clear version control..
Comparison Table
Boords
vertical specialistStoryboarding and animatic platform with shot list and frame management capabilities.
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.
A key tradeoff is that complex breakdowns often require careful setup of shot structure up front so downstream exports stay consistent. Boords fits teams that review planning visually and then need a controlled shot list artifact for crew scheduling and call-time distribution.
- +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
- –Shot structure setup upfront is needed for consistent exports
- –Automation depth for custom workflows is limited versus general APIs
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.
Celtx
SMBScriptwriting and pre-production platform including shot list and storyboard modules.
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.
A key tradeoff is that automation depth for cross-department handoffs depends more on built-in document workflows than on a public extensibility layer. Celtx fits best when a small to mid-size crew wants script-to-shot consistency and ongoing review, instead of building custom integrations to other scheduling or camera-report systems.
- +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
- –Integration and API coverage for custom pipelines is limited for scale-up teams
- –Advanced taxonomy controls for shot-type filtering can feel constrained
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.
CuePilot
vertical specialistLive production planning software with shot cueing, camera rundown, and visual sequence coordination.
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.
- +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
- –Shotlist-first design can be limiting for projects needing broader scheduling depth
- –Interchange and export options may require extra process for advanced pipelines
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.
Shot Designer
vertical specialistCamera blocking and shot list application for scene staging with real-time animation.
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.
Shot Designer also targets interoperability through export paths for review and downstream production documents, including spreadsheet-friendly shot lists. Production teams that need fast review cycles for shot pages typically use it to standardize blocking notes, lens metadata fields, and revision tracking across iterations.
- +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
- –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
Best for: Fits when shot pages and shot status tracking matter more than review markup and heavy collaboration tooling.
SetHero
SMBFilm production software for schedules, call sheets, crew coordination, and shot planning.
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.
- +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
- –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
Best for: Fits when mid-size crews need shot planning, storyboard-linked review, and controlled updates across departments.
Gorilla Scheduling
SMBProduction scheduling software for script breakdowns, stripboards, cast, locations, and shooting plans.
Setup time blocking that recalculates scheduling impact when shot statuses or timing inputs change.
Gorilla Scheduling is a shotlist-focused scheduling tool that turns approved scenes and shot requirements into day-by-day shooting plans. It concentrates on setup time blocking, shot status workflow, and exportable shooting schedule outputs that production coordinators can circulate.
The workflow is built around practical field coordination, including crew permissioning for departmental access and revision tracking for ongoing plan changes. Gorilla Scheduling fits teams that need a workable bridge between shot planning and on-set execution rather than a general purpose review board.
- +Setup time blocking helps translate shot plans into realistic day-of scheduling
- +Shot status workflow supports incremental approval and execution updates
- +Export-ready shooting schedule outputs support fast coordinator circulation
- +Crew permissions support departmental access control across production roles
- –Shot planning depth is thinner than dedicated editorial review systems
- –Scheduling accuracy depends on consistent shot status and time estimates
- –Shotlist export flexibility is limited compared with tools built for heavy interchange
- –Automation coverage is narrower than API-first shot planning suites
Best for: Fits when production coordinators need day-by-day shooting schedules derived from shot plans and controlled access.
Flow Production Tracking
enterpriseProduction tracking software for shots, assets, tasks, reviews, and department workflows.
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.
- +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
- –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
Best for: Fits when production tracking must drive shot status across departments with governed permissions.
ftrack
enterpriseProduction management software for media teams with shot, task, review, and scheduling workflows.
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.
- +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
- –Shot import and mapping needs setup to match existing naming conventions
- –Review UX can feel administrative compared with shot-by-shot marking tools
Best for: Fits when production teams need shot-status automation and governed access across departments.
Kitsu
vertical specialistProduction tracking software for animation and visual effects assets, shots, tasks, and reviews.
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.
Collaboration and review happen on per-shot entities so editorial changes can be tracked against each shot’s metadata. Kitsu also supports exports that fit shot tracking handoffs when a downstream tool expects a spreadsheet-style workflow.
- +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
- –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
Best for: Fits when storyboard-to-shot list collaboration needs a structured per-shot record with review and handoff exports.
farmerswife
enterpriseMedia production management software for scheduling, resources, projects, and production operations.
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.
Farmerswife also supports importing and exporting shot lists for handoffs with editing, crew planning, and scheduling tools. Governance features include role-based crew access and versioned updates so departments can view the right revision during daily review cycles.
- +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
- –Advanced automation and API surface are limited for fully programmatic workflows
- –Storyboard and lens metadata linkage depth is thinner than dedicated review suites
Best for: Fits when production teams need shot planning with frame-linked review notes and controlled crew permissions.
Conclusion
After evaluating 10 art design, Boords 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.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right shotlist software
Shotlist software coordinates planned shots with revisions, review feedback, and downstream production use. This buyer’s guide covers Boords, Celtx, CuePilot, Shot Designer, SetHero, Gorilla Scheduling, Flow Production Tracking, ftrack, Kitsu, and farmerswife, with special attention to Shot Lister and Frame.io.
The strongest tools keep the shot structure stable while connecting feedback to the exact planned item. Boords prioritizes storyboard linkage with revision history for dependable review cycles.
Shotlist software for shot-numbered planning, shot-status workflows, and review-linked exports
Shotlist software manages a scene breakdown into a shot list with shot numbers, planned setups, and status tracking tied to production progress. Teams use it to maintain shot planning continuity across revisions and to attach review notes to specific planned items.
Boords and SetHero both emphasize storyboard linkage so visual context stays tied to each shot during revision and shot-status changes. Boords further couples that linkage with revision tracking to keep editorial edits reviewable.
Shotlist software capabilities that keep shot numbers and feedback aligned
Shotlist software succeeds when planned shot identifiers stay stable across revisions and when review feedback remains mapped to the exact planned item.
Boords leads with storyboard linkage plus revision tracking, and the rest of the list separates into review-first workflow tools, shot-page planning tools, and production-tracking systems with governed permissions.
Storyboard-linked shot entries with revision history
Boords ties each shot to its visual storyboard panel and keeps revision history so review cycles stay coherent. SetHero provides storyboard-linked review alignment during shot status changes, with a workflow aimed at controlled cross-department updates.
Shot-status workflows that map feedback to the planned item
CuePilot ties shot-level review to shot status and shot list revisions so feedback stays attached to the same planned entry as statuses evolve. Gorilla Scheduling and Flow Production Tracking both connect status updates to planning-to-execution, with Flow Production Tracking emphasizing governed role permissions.
Script-driven continuity for shot list structure during revisions
Celtx uses script-to-shot continuity so shot list structure stays aligned when scene pages shift during revisions. Kitsu maintains entity-linked shot notes across revisions without rebuilding the whole list, which reduces rework when teams iterate repeatedly.
Setup and day-planning notes derived from shot pages
Shot Designer uses a shot-page workflow that connects scene breakdown work to setup notes used for day planning and production distribution. Gorilla Scheduling adds setup time blocking that recalculates scheduling impact when shot statuses or timing inputs change.
Governed access and departmental workflow alignment
Flow Production Tracking covers departmental work states using role-based access controls and configurable workflows aligned to production progress. ftrack adds API-driven automation hooks so shot status workflow states stay synchronized across departments with extensible change tracking.
Extensibility and API-driven automation for cross-pipeline updates
ftrack provides extensible review and change tracking that links notes to shot-level workflow states via API-driven automation. Boords is stronger on storyboard linkage and revision review cycles, but its custom workflow automation depth is described as limited versus general APIs.
Choose shotlist software by workflow ownership, change-control needs, and automation depth
The right shotlist software depends on where change control lives. Some tools keep visual context attached to shots and preserve revision history, while others center on shot-status execution tracking or API-driven synchronization.
Teams also need to match automation depth to pipeline reality. Tooling that expects disciplined upfront setup can produce clean exports, while tools with thinner editorial governance can force manual reconciliation when shot structures get complex.
Pick the system of record for shot identity changes
If visual context must stay anchored while edits happen, Boords and SetHero both prioritize storyboard linkage so shots remain tied to specific storyboard panels during review and shot status changes. If the script is the change driver, Celtx aligns shot list structure to script revisions to reduce retyping when scene pages shift.
Decide whether review feedback must attach to shot status or to shot pages
CuePilot maps shot-level review to shot status and shot list revisions so feedback follows the exact planned item through the workflow. Shot Designer instead uses a shot-page workflow that connects scene breakdown work to setup notes used for day planning, so review and export follow the shot-page structure.
Match scheduling depth to the way time estimates change
If day-by-day planning must react to timing edits, Gorilla Scheduling recalculates scheduling impact using setup time blocking when shot statuses or timing inputs change. If shot status governs execution across departments, Flow Production Tracking emphasizes governed permissions and configurable workflows tied to production progress.
Validate pipeline automation needs against API and automation hooks
If cross-department synchronization must run through automation, ftrack offers API-driven automation hooks that connect notes to shot-level workflow states. If automation is mostly about review cycles and stable exports, Boords keeps revision tracking readable during shot planning edits with storyboard linkage.
Test imports against the metadata density of existing shot spreadsheets
If dense lens metadata fields need to carry over through CSV, SetHero notes that CSV import coverage can be limiting. If exports and review handoff formats feel spreadsheet-like, Kitsu exports are described as more spreadsheet-centric than production-report tailored.
Plan governance for workflows that rely on configuration
If workflows depend on many custom fields and configuration, Flow Production Tracking can require governance discipline to keep complex setups consistent. ftrack’s API-driven mapping also requires setup to match existing naming conventions so shot import and mapping do not drift.
Teams that match shotlist software to how they review and execute shots
Shotlist software fits best when the team needs stable identifiers for planned shots, mapped review feedback, and a clear shot status workflow.
Selection narrows quickly once the production method is known, because tools prioritize different centers of gravity like storyboard-linked review, script-driven continuity, or governed production tracking.
Editorial review teams that run iterative shot changes
Boords keeps visual context attached through storyboard linkage and preserves revision history so feedback stays reviewable across edits. CuePilot also keeps feedback tied to the exact planned item via shot-level review mapped to shot status and shot list revisions.
Script-driven planning crews that revise scenes frequently
Celtx maintains script-to-shot continuity so shot list structure shifts with script changes during revisions. Kitsu supports reusable templates and entity-linked shot notes so teams avoid rebuilding whole lists when recurring shot structures repeat.
Production coordinators who translate shot plans into daily execution
Gorilla Scheduling focuses on setup time blocking that recalculates scheduling impact when timing inputs or shot statuses change. Shot Designer centers day planning by connecting scene breakdown work to setup notes used for production distribution.
Cross-department teams needing governed permissions and shared status
Flow Production Tracking provides role-based access controls and configurable workflows so shot status aligns with production progress across departments. ftrack adds API and automation hooks so shot status workflow states remain synchronized with extensible change tracking.
Common shotlist software mistakes that break continuity between planning and review
Shot planning fails when the team underestimates how much structure the tool requires to keep exports consistent and feedback mapped.
Mistakes usually show up as unstable shot structure, mismatched imports, or workflows that require configuration discipline before they produce dependable results.
Starting with inconsistent shot structure and then relying on clean exports
Boords requires upfront shot structure setup for consistent exports, so teams should standardize the shot page structure early. Shot Designer also depends on careful upfront configuration for bulk changes to behave predictably.
Expecting a shot-status workflow system to provide deep editorial planning UI
Gorilla Scheduling is described as having thinner shot planning depth than dedicated editorial review systems, so it works best when shot planning already exists and scheduling needs recalculation. Flow Production Tracking’s shot list presentation depends on configuration rather than a dedicated shot planning UI, so teams should budget time for setup.
Assuming imports will map lens and metadata fields without adjustment
SetHero notes CSV import coverage can be limiting for dense lens metadata fields, so teams should validate their spreadsheet columns against the import mapping. ftrack also requires setup to match existing naming conventions, so teams should test mapping before importing large shot libraries.
Treating export formats as uniform when the output style differs by tool
Kitsu exports feel more spreadsheet-centric than production-report tailored, so teams that need production-distribution formats should test outputs early. Shot Designer focuses on shot pages and setup notes for production distribution, so it is better aligned with planning artifacts than spreadsheet-style exports.
How We Selected and Ranked These Tools
We evaluated Boords, Celtx, CuePilot, Shot Designer, SetHero, Gorilla Scheduling, Flow Production Tracking, ftrack, Kitsu, and farmerswife on features, ease, and value. Features accounted for 40% because storyboard linkage, shot-level review mapping, and shot status workflow behavior determine whether feedback stays attached to the correct planned item.
Ease and value each accounted for 30% because shot structure setup upfront, configuration complexity, and review UX affect how quickly teams can keep revisions readable. Boords earned the top position because storyboard linkage ties visual context to each planned shot while revision tracking keeps edits reviewable, and that combination maintains continuity across review cycles better than tools that prioritize execution tracking or shot-page setup.
Frequently Asked Questions About shotlist software
How do Boords and Kitsu handle shot numbering and revision traceability when a scene breakdown changes?
Which tools support storyboard linkage that survives shot status workflow changes?
When teams need on-set review tied to take-level edits, how do CuePilot and Gorilla Scheduling differ?
What breaks if a production requires managed departmental access and governed role permissions across departments?
Which tools provide API access or automation surfaces for shot status and review workflows?
How do teams migrate existing shot lists into shot planning systems using imports and export paths?
When shot status workflow must be coordinated with day-out-of-days planning, how do Shot Designer and Gorilla Scheduling compare?
Which tool best supports coupling planning data to asset and project hierarchies for consistent shot-centric collaboration?
How do Frame.io-style review loops map onto shot-level planning records in this market?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Art Design alternatives
See side-by-side comparisons of art design tools and pick the right one for your stack.
Compare art design tools→