Product
Introducing Projects: Workspace-Level Organisation for Your Video Library
When you manage footage for multiple clients, everything in one flat list stops working. Projects give you scoped workspaces that filter your entire library, from videos and sources to search and dashboard stats.
You have three active clients. Each has a couple hundred clips across multiple camera cards, a few interview sessions, and a growing pile of B-roll. You open FrameQuery and see all of it in one list.
Finding the right footage means mentally filtering out two-thirds of your library before you even start searching. That overhead compounds every time you switch context between clients. We built Projects to eliminate it.
What Projects actually do
A project in FrameQuery is a workspace filter. Select a project from the switcher in the nav bar, and the entire app scopes to just that project's content. Your videos tab shows only that project's clips. Your sources tab shows only that project's folders. Your dashboard shows stats for that project alone. Even search defaults to the current project.
Select "All Projects" and you are back to the full, unfiltered view. Nothing is hidden permanently. Projects are a lens, not a container.
The switcher
The project switcher sits in the top nav as a compact pill showing a color dot and the project name. Click it (or press Ctrl+P) and a dropdown opens with your project list, ordered by most recently used. Type to filter, arrow keys to navigate.
From the same dropdown you can create a new project, edit an existing one, or open the management panel to archive or delete projects you no longer need.
We went with a preset palette of twelve OKLCH colors rather than a custom color picker. Every color in the palette is tested against both light and dark themes to ensure the dot is always legible. No fiddling with hex codes, no accidentally picking a color that disappears on a dark background.
Sources follow projects
The more interesting design problem was connecting sources (watched folders, cloud drives) to projects. A source can belong to multiple projects, since the same drive might contain footage for different clients organised in subfolders.
When you link a source to a project, auto-assign is enabled by default. That means when FrameQuery scans that source and discovers new videos, they are automatically added to every project the source belongs to (where auto-assign is on). You can toggle this per source, per project.
This matters because video professionals rarely add footage one clip at a time. They dump a card, FrameQuery scans it, and the new clips need to land in the right project without manual sorting.
If you remove a source from a project, FrameQuery asks whether to also remove the videos that came from that source. If you say no, the existing video assignments stay, but no future auto-assignment happens. A small decision, but one that prevents accidental data loss.
Many-to-many, not folders
Videos can belong to multiple projects simultaneously. This was a deliberate choice over a folder-like model where each video lives in exactly one place.
The practical reason: shared footage exists. Your studio might have a library of stock B-roll that multiple client projects draw from. Or interview footage from a single shoot might be relevant to two different deliverables. Duplicating the video entry to put it in two "folders" would create confusion. Many-to-many assignment avoids that.
Assigning videos to projects works in bulk. Select a set of clips in the videos tab, right-click, choose "Add to project," and pick from your project list. The operation is idempotent, so adding a video that is already in the project is a no-op.
Scoped dashboard
When "All Projects" is selected, the dashboard shows a portfolio overview: a grid of project cards, each displaying video count, total duration, and storage used. Click a card and you switch to that project.
When a specific project is selected, the dashboard shows the same layout as before, but filtered to that project's data. You see processing status, storage breakdown, and activity for just the work that matters right now.
Scoped search
Search defaults to the current project. If you are working in "Client X" and search for "interview on rooftop," you only get results from Client X's footage.
For the times when you need to search everything, there is a toggle in the search bar to switch between "This project" and "All projects." You can also prefix your query with all: to do a quick global search without changing the toggle state.
What archiving and deletion look like
Archiving a project hides it everywhere: the switcher, the "All Projects" view, the dashboard, search results. It is a soft removal. You can find archived projects in the management panel and restore them with one click.
Deleting a project is permanent, but it only removes the project itself and its assignments. No videos or sources are deleted. Everything that was in that project becomes unassigned, visible again in the "All Projects" view.
Designing for real workflows
The goal with Projects was to match how freelancers and production teams actually work: juggling multiple clients, switching context frequently, and needing to keep footage separated without losing the ability to see everything at once.
We considered a simpler tagging approach, but tags do not scope your entire workspace. We considered a folder model, but folders force videos into a single location. The workspace-filter approach gives you the isolation of separate projects with the flexibility of a flat library underneath.
If you have thoughts on how Projects should work or features you would like to see, drop us an email at feedback@framequery.com.