EDL · OpenTimelineIO · FCPXML · 2-10 person studios

Your cut is the shot list. Stop retyping it.

Import the EDL, OTIO or FCPXML (Final Cut & DaVinci Resolve) and every shot, duration and version is already there. Point at the renders folder and statuses update themselves. One click runs the conform check - missing shots, short ranges, stale versions - and a turnover diff shows what changed since the last cut, before the client runs it for you.

Flat A$29/mo per studio not per seat Local-first pixels never leave your machine No setup phase productive in the first hour

14-day free trial · No credit card · Works with Resolve, Final Cut, Premiere and Avid

NEON HARBOR EP101 CUT 04 / conform24 fps · 8f handles
14
OK
2
Missing
3
Range
1
Stale
SH010ok v002124 frames - covers cut + handles
SH020missingNo renders found on disk for this shot
SH030range40 frames; the cut needs 48 + 8f handles = 64
SH040staleCut references v001 but v003 exists on disk
SH990not in cutRendered, but the shot left the edit
The problem

Small studios get the worst of both worlds

The spreadsheet drifts

The Google Sheet was accurate for a week. Then the cut changed, three shots got new versions, nobody updated row 40, and now the sheet is a rumour. Every status in Cutlist Tracker comes from the cut file and the renders folder - the two things that are always true.

The big trackers are built for ILM

Flow Production Tracking runs about US$50 per user per month and assumes a pipeline TD configures it. ftrack is US$25 a seat. For five people that's US$1,500-3,000 a year for software you spend a week setting up - to track thirty shots.

Conform day is an ambush

Missing shots, renders short of handles, a v001 in the timeline while v003 sits on disk - you find out when the online editor does. A one-click check against the actual folder finds it while it's still a Tuesday problem, not a delivery problem.

Features

Tracking that derives itself

The cut IS the shot list

Import a CMX3600 EDL, .otio or FCPXML (Final Cut & DaVinci Resolve) and shots, cut ranges, durations and in-cut versions populate themselves. No retyping, no drift.

Token name mapper with live preview

Tell it once how your names work - {show}_{shot}_{task}_v{version} - and watch every clip map to a shot in the preview table before you commit.

Folder scan = status update

Scan the renders folder and every shot learns its latest version and frame coverage. What's on disk is the status.

One-click conform check

Missing shots, ranges short of cut + handles, gaps inside sequences, stale versions, renders that fell out of the cut - one report, exportable.

Sequence health

Flags the quiet inconsistencies before they bite - mixed frame padding, mixed extensions, and shots carrying multiple versions on disk - across every sequence in the folder.

Status file, not a server

Statuses and notes save into a small cutlist-status.json in the project folder. Teammates scanning the same folder pick it up automatically, merged by timestamp with who/when attribution - your file server is the sync.

Turnover diff between cuts

Drop in the previous cut and see exactly what changed - shots added, dropped, re-timed, re-versioned or reordered. Stop comping a shot that got cut in v05.

Per-department matrix

List your tasks - comp, roto, fx - and a shot × department grid shows whether each department is delivered against the cut, not just "does any render exist".

Reports + delivery manifest

Export the conform report as CSV or a printable page, and a delivery manifest of the shots marked Final - version, frame range and path - to hand back to editorial or the client.

How it works

Cut to conform in three steps

1

Import the cut

Drop the EDL or .otio from Resolve, Premiere or Avid. Pick your naming pattern and watch the live match preview.

2

Scan the renders folder

Point at where renders land. Sequences are grouped by shot, task and version - names only, no pixels read.

3

Read the report

OK / missing / range / stale / not-in-cut, per shot. Fix, re-scan, export, send.

Honest comparison

Where it sits

The incumbents are excellent at what they're built for - large-facility production tracking. This is built for the other 90% of studios.

Cutlist TrackerFlow Production Trackingftrack StudioSpreadsheet
PricingA$29/mo flat per studio~US$50/user/mo~US$25/user/moFree
5-person studio / year~A$348~US$3,000~US$1,500Free (plus the drift)
Shot list sourceThe imported cutManual / pipeline integrationManual / integrationManual
Status sourceThe renders folderPeople updating tasksPeople updating tasksPeople updating cells
Conform check vs diskBuilt in, one clickVia pipeline scriptingVia pipeline scriptingBy eye
Server requiredNone - local-firstCloudCloudCloud/file

Vendor prices are public list prices as observed mid-2026 and can change; all trademarks belong to their owners. No affiliation.

Pricing

Flat. Like your budget needs.

Billed monthly. Every plan starts with a 14-day free trial - no credit card required.

Solo

1 user

$9/mo

For freelance editors & VFX generalists

  • EDL + OTIO + FCPXML import, unlimited cuts
  • Folder scan & conform reports
  • CSV + printable exports

Enterprise

Multi-show studios

$79/mo

For studios juggling several shows

  • Everything in Studio
  • Priority support
  • Feature-request fast lane

Prices in AUD, billed worldwide · Cancel anytime · No credit card required to start your trial.

Guides

Read before you need it

VFX conform checklist

Missing shots, handles and stale versions.

FCPXML vs EDL vs OTIO

Which cut format VFX should use.

Reading a cut diff

What changes between two turnovers.

The VFX delivery manifest

Proving what you delivered.

Task tracking without ShotGrid

The per-department matrix at small scale.

ShotGrid alternatives (2026)

What small studios actually need.

The CMX3600 EDL, explained

Events, timecodes and FROM CLIP NAME.

Shot naming conventions

Names that survive the pipeline.

FAQ

Questions, answered

What formats can I import?

CMX3600 EDL, OpenTimelineIO (.otio) and FCPXML - covering DaVinci Resolve, Final Cut Pro, Premiere Pro and Avid exports.

Does my media get uploaded?

No. The folder is scanned by file NAME only, in your browser; pixels never leave your machine. Only your account and subscription status are stored, via Supabase and Stripe.

How do teammates share statuses with no server?

The tracker writes cutlist-status.json into the project folder. Anyone scanning the same folder picks it up automatically; you can also export/import it manually.

What browser do I need?

Folder scanning works best in Chromium browsers (Chrome, Edge, Brave) via the File System Access API; other browsers fall back to a basic folder picker.

My naming convention is weird. Will it map?

Probably - the pattern editor takes any {token} arrangement, and the live preview shows exactly which clips map before you commit. If your names truly contain no shot code, no tool can save you.

Is there a free trial?

Yes - 14 days, no credit card. There's also a one-click example cut so you can see a full conform report in the first minute.

Conform day should be boring.

Import the cut, scan the folder, fix what the report finds. Then go home on time.

14-day free trial No credit card Cancel anytime
Pixels never leave your machine
Flat per studio - not per seat
Start Your Free Trial

Product news & updates

Occasional product news, new importers and tips. No spam; unsubscribe anytime.