Frame.io

frame.io

ALMOST

A weekend of work, and real gaps remain.

Video review at professional scale: frame-accurate comments, versions side by side, and camera-to-cloud upload straight from the shoot.

Promptfree, for everyone, and the only version there is
Build the video review tool I actually need instead of Frame.io — and be clear about which half you are giving up.

**The camera-to-cloud path and the editing-suite panels are not buildable.** They are hardware partnerships and plugins for closed applications. If footage arriving from set is why you pay, keep paying. If it is review and approval, that is entirely doable.

STACK
- Node 20+ with Fastify, server-rendered HTML with a little vanilla JS
- SQLite through better-sqlite3, WAL mode
- ffmpeg on a worker for proxies, hls.js for playback
- Object storage with a delivery network
- Caddy in front

THE DATA MODEL
- assets: id, project_id, name, source_path, duration_ms, status
- versions: id, asset_id, number, path, uploaded_at — **an upload is always a new version**
- renditions: id, version_id, height, path — the proxies
- comments: id, version_id, at_ms, out_ms, body, author, drawing_json, resolved_at
- decisions: id, version_id, reviewer, verdict, note, at — append-only

PROXIES, WHICH DECIDE WHETHER THIS IS USABLE
- Nobody reviews a 40GB master over a hotel connection. Transcode to a small ladder and serve HLS
- **Generate the proxy before the upload finishes if you can**, chunk by chunk. The wait between uploading and reviewing is where this kind of tool loses people
- A queue with a concurrency cap; ffmpeg will take every core you give it

COMMENTING, FRAME-ACCURATE OR NOT AT ALL
- Store the exact millisecond, and a range for a comment about a section
- **Snap to frame boundaries using the real frame rate.** 'At about 4:12' is what a comment in an email says, and the entire reason a tool like this exists is to be better than that
- Drawing over the frame, stored as shapes with the timestamp, never flattened into an image
- Keyboard: play, pause, step one frame, comment. An editor lives on the keyboard

VERSIONS
- Side-by-side playback of two versions, locked to the same timecode. That is what ends 'this note was never addressed'
- Comments stay attached to the version they were made on and carry forward marked as such

SHARING
- Token links with no account for clients, an expiry, and a download switch that is off by default
- **Watermark the reviewer's name into the picture for anything under embargo.** Unreleased footage leaks, and a burnt-in name is what makes somebody think twice

STORAGE, WHICH IS THE BILL
- Masters on cold storage, proxies on fast. Measure bytes stored and served per project
- A retention per project with a warning before anything is removed, never a silent deletion

WHAT MATTERS MOST
Fast proxies and frame-accurate comments. Without the first nobody reviews; without the second you have built email with a video player.

What you lose

  • Footage arriving from the camera before anybody gets home
  • Panels inside Premiere and Resolve where editors already work
  • Playback of very large files without waiting for a download
  • Storage and transcoding for terabytes of rushes

If you would rather not build

  • Filestage, if the work is not exclusively video
  • Frame.io itself, if footage from set is the reason

The escape hatch

open source · no votes, no paid placement

FFmpeg

$0

Proxy transcoding, frame extraction and burn-in watermarks.

FFmpeg/FFmpegfree · open source

hls.js

$0

Adaptive playback so a review starts instantly.

video-dev/hls.jsfree · open source

Why this verdict

our own opinion · changed only by a person

48/100

Verdict kinda at 48: review and approval are buildable, camera-to-cloud and the NLE panels are not. The proxy pipeline is what decides whether editors tolerate it.

History

tracked since 16 Aug 2026 · nothing is ever overwritten

Interest · last 30 days

Nothing recorded yet. This chart fills in once the page has visitors, votes or prompt copies — it will not draw a flat line to look busy.

Questions about Frame.io

answered from the record above

Is Frame.io free?

No — the plan we track is $15 a month. Pro at $15 per user per month billed annually, with storage limits per tier.

Can you replace Frame.io by building your own?

ALMOST. A weekend of work, and real gaps remain. Replacement score 48 out of 100, build time a weekend. Read what you lose before you decide.

How much does Frame.io cost?

$15 a month on Pro — $180 a year. Recorded 16 Aug 2026.

What do you lose by replacing Frame.io?

Footage arriving from the camera before anybody gets home; Panels inside Premiere and Resolve where editors already work; Playback of very large files without waiting for a download; Storage and transcoding for terabytes of rushes. If any of those carry weight for you, keep paying.

Is there an open-source alternative to Frame.io?

Yes: FFmpeg, hls.js. The prompt on this page is for when you want it your way instead.

Related entries

same category first, most replaced first

All 26 in Screen recording & video

Not sending yet

Every week, something stops being worth paying for.

New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click. Nothing is being sent yet — your address is kept here, and the first issue is the first thing it is used for.

free forever · no tracking pixel · stored here, never passed to anyone

Esc