ClipLogger base app$0to browse, log, search and keep your work.
Use your Mac and existing storage. Local AI has no per-clip service fee. Rush and Your API are optional.
Start a free logging sessionone-time license; first year of updates included
Premium is $349. Optional extra year of updates: $79 Standard / $169 Premium.
You can keep using your purchased version without renewal. Educational pricing is available. Currency follows the official page retrieved for this comparison.
Prices checked September 2026.
Check Kyno pricingWhat ClipLogger adds
ClipLogger is worth trying when you like browsing a drive in Kyno but still spend the evening filling out the log yourself. It adds reviewed subject evidence, reusable typed fields and vision-model suggestions to the work before the edit, with a free base app for each supported Mac. Comparing several tools rather than these two? Read Kyno alternatives for logging footage on a Mac.
Use suggestions to build a log you can search.
Kyno users already understand the value of drill-down, markers and subclips. ClipLogger brings that work together with a palette for your production, a roster for known subjects, and suggestions for the fields you chose. A machine can propose that a shot shows a celebration; you can correct the athlete, choose the useful span and decide whether the shot deserves five stars.
Maya Torres + celebration + 4 stars
GameDay_Maya-Torres_Celebration_004.movGameDay_Maya-Torres_Celebration_004.mov.logger.jsonCompare the capabilities
✓ Supported · ✕ Not offered · ◐ Different scope · ? Not documented. Unknown does not mean absent.
| What you can do | ClipLogger | Kyno |
|---|---|---|
| Search, browse and log without a paid subscription | YesFree base app, including native log search. | NoInitial license purchase; renewal optional. |
| See footage across nested folders | YesDrill-down brings the directory into one view. | YesDrilldown. |
| Scan clips as filmstrips and a continuous reel | YesSee how a clip develops, then move through the shoot. | Partial / different scopeContent thumbnails and assembly cuts; view behavior differs. |
| Learn a logging palette from existing filenames | YesInfer editable fields and options from an already named directory. | Not documentedDirectory-to-typed-palette workflow not documented. |
| Define typed fields and reusable logging controls | YesSingle / multi-select, subjects, flags, ratings, text and more. | Partial / different scopeTags, ratings and metadata sets; field/control model differs. |
| Use a roster and code replacement for known names | YesMap your codes to subjects and field values. | Not documentedRoster-driven code replacement not documented. |
| Recognize people, items and places from examples | YesName a subject, provide face or appearance examples, and review suggested matches. | Not documentedReviewed face and appearance matching not documented. |
| Suggest values using your own logging vocabulary | YesLocal, Your API or Rush; review the proposed log. | Not documentedVision-model logging suggestions not listed. |
| Discover footage by meaning or visual similarity | YesSearch by meaning, use a prepared text-to-image model, or Find Similar. | Not documentedSemantic visual discovery not listed. |
| Turn suggested ranges into virtual clips | YesInspect suggested spans; keep the useful range without duplicating the original. | Partial / different scopeManual subclips; AI-suggested ranges not documented. |
| Carry useful ranges and markers into an editor | YesSupported NLE exports; check the fields and timing each format carries. | YesMarkers, subclips and NLE integrations. |
| Copy and verify camera media | YesIngest with verification and a result you can inspect. | YesVerified backup; multi-destination support depends on edition. |
| Turn your reviewed log into actual filenames | YesPreview field-based names, then rename files on disk. | YesMetadata-aware batch rename. |
| Write separate subclip files when you need them | YesStream-copy or frame-accurate re-encode; keep the source original. | YesSubclip export and transcoding. |
| Keep readable metadata beside the media | YesEnable .logger.json output; retain written sidecars with the originals. | YesUser metadata in adjacent hidden XML folders. |
| Run vision-based logging on your own editing Mac | YesUse a supported model that fits your Mac; no per-clip local service fee. | Not documentedLocal vision-model logging not listed. |
| Run the logging app on Windows | NoApple silicon Mac; macOS 15 or later. | YesMac and Windows versions. |
| Play native RED R3D camera originals | NoR3D is outside the current supported playback set. | YesR3D in Premium. |
From the folder to the edit
Browse nested folders together. Reuse supported XMP values or learn a palette from existing filenames. Name people, items and places, review AI suggestions, then search the log by words, meaning or the values in your directory.
Filmstrips, Reel, markers and virtual clips help you collect useful moments. Write reviewed fields into filenames and sidecars, then export supported selects to your NLE. See the workflow.
What you keep after cancelling
Kyno is not a subscription trap: its purchased version remains usable without renewal, and it stores user metadata in XML inside hidden folders beside the media. ClipLogger’s advantage here is free entry and the richer logging workflow, not a claim that Kyno takes your metadata away. Keep Kyno’s metadata folders with an archive; write ClipLogger sidecars for the new work.
What the full workflow costs
A new assistant can start logging in ClipLogger for $0 in base-app fees. Kyno charges for the initial license, with optional update renewals and separate education offers. Neither comparison requires an invented recurring Kyno subscription. Add Rush only when its processing time is worth paying for.
ClipLogger’s base app stays free. Local models use your Mac’s memory and time; start a batch overnight to work through an old shoot. Pro is $20/month with 150 Rush credits ($240 over 12 months); one eligible clip uses one credit. Your API requires eligible paid access plus your provider’s usage bill. Plans and submission limits.
Choosing the right combination
Your workflow depends on Kyno’s transcoding, Windows support, or Premium codec coverage such as RED R3D. It also offers drill-down, verified backups, batch rename, markers and subclips.
ClipLogger fits when: You want to reduce repeated manual logging, reuse a production-specific palette, and search both visual meaning and confirmed metadata on your Mac.
ClipLogger currently requires an Apple silicon Mac on macOS 15 or later. It has no hosted video-review portal, and native RED R3D playback is not supported. Format and setup details.
If you use both
Keep Kyno for a camera format or transcode it handles well. Use supported originals or clearly identified derivatives in ClipLogger for roster lookup, palette-driven suggestions and source selection. Keep original paths and timing with any derivative so the editor can relink.
Try the work on one shoot
How much of the log can you prepare before an assistant starts typing?
Use the same 30 clips in both tools. Record the manual effort needed to name known athletes, log shot size and action, and mark the best ranges. In ClipLogger, build the roster and palette once, run suggestions, then count the corrections and useful selects. Measure review time as well as processing time.
Bring your current workflow into ClipLogger. There is no direct Kyno metadata-folder importer. Preserve the old XML and exports, then recreate the fields and ranges that matter in your first ClipLogger shoot.
Sources & scope
Checked September 23, 2026. Comparisons use vendor documentation; we have not benchmarked the products against each other.
- Kyno / Signiant · Licenses, pricing and renewal
- Kyno / Signiant · Features and edition differences
- Kyno / Signiant · Metadata storage and FAQ
- Kyno / Signiant · Release notes for Kyno