Launched this week

Clipto
Fully local, natural language search over terabytes of media
740 followers
Fully local, natural language search over terabytes of media
740 followers
Like Google Photos, but fully local. Turn the terabytes of video, audio, meetings, and files you work with into searchable memories, without uploading anything to the cloud. Clipto automatically tags people, dialogue, and scenes, so you can instantly find any moment buried in your media just by describing what you're looking for. It's fast too: on a MacBook Pro M5, Clipto indexed 2TB of videos in just 24 hours.











Raycast
We've been honing Clipto's story for a few months. At the end of our last call @henry_kang proved the value of the product.
He and his team were out in the desert, testing Clipto remotely: minimal reception, terabytes of footage sitting on his laptop, and he needed to find a specific shot for the launch video.
He searched for: "the wide drone shot where the car enters the desert".
He didn't want "a cinematic moment." Not a "vibes" search.
He knew he had the clip but in the pre-Clipto world, it would take hours of video scrubbing to find it.
He found that clip in seconds using natural language to search over his own media, fully local.
Just like Google Photos — but nothing lives in the cloud.
This isn't an easy problem to solve. Henry's been pursuing this direction for over twenty years, when at CMU's Robotics Institute (my alma mater, FYI), he began pushing the limits of computer vision. He starting with indexing hundreds of images and then advanced to millions of objects — and watched recognition basically explode once memory scaled.
Clipto is in many respects the culmination of that work, pointed at your personal hard drive.
And it's quick: a modern M5 MacBook chews through ~2TB of video in about a day. Why not push yours through its paces?
Clipto
@chrismessina
Thanks Chris. 🙏
One thing we’ve learned from today’s discussions is that people aren’t really looking for “AI magic.”
They already know the clip exists.
They already own the footage.
They just need a reliable way to find it.
Whether it’s:
• the exact moment a decision was made in a meeting
• a specific quote from a podcast recorded months ago
• a particular shot buried in terabytes of footage
the common problem is the same:
our computers store everything, but remember nothing.
That’s ultimately what we’re building toward: a local memory layer for the media people already own.
@henry_kang I'm really glad that you mentioned the fact that people are not looking for AI magic - that's indeed true. Great stuff!
Clipto
@sk_uxpin Thanks! 🙌
ViralSort
This looks really interesting.
I'm curious about how deeply it understands media content.
Does it recognise things like camera angles, shot types (wide, medium, close-up), camera movements, transitions, B-roll, and multi-camera sequences?
It would be incredibly useful if I could search for something like "close-up shot of a person smiling" or "drone footage with a slow pan" and instantly find matching clips across my archive.
Would love to know how detailed the visual understanding gets beyond basic object and dialogue detection.
Clipto
@pradeepmalakar That's a really professional cinematography question. We're working hard to enrich our understanding of cinematic language to better serve professional video creators — here's what we can reliably recognize today:
Shot Type: Wide Shot, Medium Shot — e.g. "wide shot of a city street" or "medium shot interview"
Camera Angle: High Angle, Overhead/Top-down — e.g. "overhead shot of a table" or "high angle crowd scene"
Framing & Composition: Landscape — e.g. "landscape framing outdoor scene"
Scene & Setting: Urban/City, Green Screen/Studio, Day — e.g. "studio interview daytime" or "urban street scene"
Technical Specs: AV1, Rec.709, 4:2:0, 8-bit, 25FPS — e.g. filter footage by codec or color space when you need format consistency in an edit
Focus & Quality: Out of Focus — e.g. quickly filter out unusable takes
...and more, these are just a few examples across the many dimensions Clipto tags. Sorry I can't list them all here! Every case shown in our demo video is a real.
Camera movements, transitions, B-roll classification, and multi-camera sequences — those are on the roadmap and we're heads-down on it.
Would love to hear what specific search queries matter most to your workflow — it really helps us understand what to build next:)
'like Google Photos but fully local' framing is clean but Google Photos works because the index follows you across devices seamlessly. curious how Clipto handles the multi-device problem. if i index 2TB on my MacBook and then want to search from my iPad or a second machine, what does that look like. is the index portable or does each device need to reindex independently because that changes the use case significantly for anyone with more than one machine
Clipto
@ansari_adin That’s a very insightful question.
Today, Clipto works independently on each machine. The index is built locally and stays local, so if you index 2TB of media on your MacBook, that index currently doesn’t automatically appear on another device.
We made that tradeoff intentionally because our first priority was privacy, local ownership, and offline usability.
That said, we completely agree that long-term memory becomes much more valuable when it can follow you across devices. Cross-device memory and synchronization are already on our roadmap, and we’re actively exploring ways to do that while preserving the local-first principles that make Clipto unique.
In many ways, this is one of the most interesting problems for us: how do you build a Google Photos-like memory layer without giving up control of your data to the cloud?
Cool concept. Real question though — is this doing actual frame-by-frame visual understanding or is it metadata/transcript/keyframe analysis? Because the gap between those two is enormous for practical use. What I actually want: upload 10 raw clips of the same scene, AI watches them all, ranks by emotional resonance, suggests best cuts.
Clipto
@joe_rucker Great question. It’s not just metadata, transcripts, or simple keyframe extraction.
We combine multiple signals, including metadata, speech transcripts, visual understanding, and information extracted directly from the video stream.
That said, we also don’t do naive frame-by-frame analysis across every frame. At scale, that becomes extremely expensive while often adding little value. Instead, we use a more selective approach to identify and analyze the most informative moments within a video.
Our current focus is helping users find the right moments and clips from large media libraries as quickly as possible.
The workflow you described, where AI reviews multiple takes, ranks them, and suggests the best cuts, is a fascinating direction. While Clipto doesn’t currently optimize for edit recommendations, many of the underlying building blocks are already there.
Out of curiosity, what’s your current editing workflow today? Are you using Premiere, Final Cut, Resolve, or something else? And how much of the selection process is still manual versus AI-assisted?
We’re spending a lot of time thinking about how AI agents and creative tools could work together, so I’d love to learn how you’re approaching it.
the 'store everything but remember nothing' line is the whole thing imo. the part people underrate is that the hard bit was never the search, its doing the indexing on-device without melting the laptop or quietly shipping stuff to a server, which is exactly why most tools just punt it to the cloud. respect for taking the harder path. one thing im curious about: once the first 2TB is indexed, is re-indexing incremental as you add footage, or does it re-chew the whole library? thats kind of the thing that decides whether this stays usable for anyone whose archive keeps growing
Clipto
@dhanishta_likhar That’s a very insightful observation.
We actually agree with your premise. For local AI products, you have to solve the hardest problem first. If you can’t make large-scale on-device indexing practical, everything else is just a demo.
As for indexing, it’s incremental. Once your library has been processed, Clipto only analyzes newly added or changed files. It doesn’t re-chew the entire archive every time.
A lot of our engineering work has gone into task scheduling, indexing pipelines, and resource management to make sure growing libraries remain practical over time.
That’s ultimately the difference between a product that works for a 50GB library and one that can keep scaling as your archive grows year after year.
Local-only across audio + video + files is the version of this I keep waiting for, congrats on shipping. The piece that usually breaks under real load is the indexing job, not the search itself. How are you handling the initial pass on someone with 5 years of meeting recordings? And does the index update incrementally or do new files queue behind the original backfill?
Clipto
@fabriziowexare Great question. We learned pretty early that indexing is actually the harder problem than search itself.
For large backfills (for example, years of meeting recordings), we’ve spent a lot of effort on scheduling, prioritization, and resource management.
The index is incremental. New files don’t have to wait for the entire historical backlog to finish processing.
If you’re indexing five years of recordings and a new meeting arrives today, Clipto will use a priority-based scheduling system to process the new content much sooner, rather than forcing it to sit behind a massive batch job.
Under the hood, we continuously balance long-running indexing tasks with newly arrived media so the system remains responsive while the library keeps growing.
Out of curiosity, how large is the media library you’re managing today? We’re seeing some users push well beyond the “normal” use case, which has been fascinating to learn from.
YouMind
This is genuinely impressive — local-first AI search for video is something I didn't know I needed until now. The desert story really sold it for me.
Quick question: does Clipto index audio content like podcast recordings or interview transcripts the same way it handles video footage? I have hundreds of hours of recorded interviews and this could be a total game-changer for my workflow.
Clipto
@jaredl Absolutely. Video gets most of the attention, but Clipto works with audio just as well.
Podcasts, interviews, meetings, voice recordings, and other audio files are all indexed and made searchable. You can search across transcripts using natural language and jump directly to the relevant moments.
In fact, if you’re sitting on hundreds of hours of recorded interviews, that’s one of the strongest use cases for Clipto. Those recordings often contain valuable insights that are almost impossible to rediscover later without a system like this.
We’d love to hear how you’re currently managing and searching those interviews today.