AI Video Editing Flows

How we curate and test AI video workflows

Curation and testing are two separate methods with separate evidence standards. This page explains each, how sources are dated and checked, and how to report an error so we can correct it.

How we curate and test AI video workflows

Two different things happen on this site, and we keep them apart. Curation means we find, audit and review resources made by other people. Testing means we ran something ourselves and measured it. A page says which one it is.

1. The resource library

Our curated picks come from a resource library of 378 entries. The library was audited on {{date:2026-10-17}} and {{date:2026-10-18}}. For each entry the audit recorded what it is, its licence, whether the source shows working output, when it was last updated and any red flags. The audit gave each entry a verdict and a check date, and those dates are shown on the cards.

2. What a pick shows

  • The name, the creator and a link to the creator's own page. We link out and credit; we do not copy.
  • Our own one-line take on what the resource is good for and where it falls short.
  • The licence, written out. Licence traps are called out, for example non-commercial licences, AGPL or GPL code, a company licence that applies from a team size, or code that is licensed but its sample media is not.
  • Warnings from the library's Warnings list: scripts that run arbitrary commands, telemetry on by default, unpinned installs, archived or stale dependencies.
  • The date we last checked it.

3. Review states

Every third-party entry moves through these states, in order. Only the last two change what visitors see.

  • Prescreened: the audit found it worth a closer look.
  • Queued: it is waiting for a person.
  • In review: a named person is reading the source, the licence and the warnings.
  • Reviewed: the person has written the one-line take and decided.
  • Published: it appears on the site.
  • Retired: it was removed, for example because it was archived, its licence changed or its link died.

Nothing third-party is published until a named human has reviewed it. Until then a card is a draft, and drafts are not shown to visitors.

4. Route statuses on effect pages

Each way of making an effect carries one of three statuses. They are not interchangeable.

  • Rendered and tested by us in HyperFrames 0.8.10 on the date shown on each route. We built it, rendered it on our own laptop and ran the checks below.
  • Source reviewed on the date shown on each route. Not tested by us. We read the source and the licence but did not run it.
  • Other ways, not tested by us. Routes in other tools that we describe but have not run.

5. Badges

There are three badges: Editorially Reviewed, Lab Tested and Editor's Pick. A badge only appears when a reviewed record backs it. Editorially Reviewed means a person finished the review above. It never means we tested the tool. Lab Tested needs a test we actually ran, with the date and the versions. Editor's Pick is a judgement by a named reviewer, and it is never decided by commission.

6. How previews are made

  • Each effect is a HyperFrames project, rendered on our laptop (AMD Ryzen 7 7735U, 31 GB RAM, Windows 11) with HyperFrames 0.8.10.
  • We also render a transparent ProRes 4444 MOV of the effect and composite it with FFmpeg 8.1.2 onto a moving background we generated. The previews are labelled as motion-only demos, not footage.
  • Every render goes through an automated flash check that approximates WCAG 2.3.1 (general flash and red flash). It is an approximation, not a certified test.
  • Every file has a size cap. Previews that go over the cap are re-encoded or rejected.

7. Prices and licences

Prices come from the vendor's own page and carry the date we read them. We recheck monthly. If a page does not state something, for example which price is monthly or annual, we say so instead of filling it in from elsewhere. Remotion's licence terms were read from its own FAQ.

8. What we do not do

  • We do not publish a number we did not measure or read from a named source.
  • We do not claim that AI is faster or cheaper than editing by hand. We have not measured that.
  • We do not re-host paid packs or other people's files. We use official embeds or links only.
  • We do not rank by install counts or by commission.
  • We have not recorded footage for tests yet, and we have not run a benchmark. Pages that need either are marked in testing and carry no results.

Corrections are logged on What changed: routes and releases we re-checked. To report an error use Contact us.

Last checked on Oct 10, 2026.