Managing captures

Filtering

The filter row sits above the captures: the view toggle first, then Reviewer, Type, Tag, and Sort.

The Tag dropdown only appears once the project has at least one tag. A project where nobody has tagged anything shows three controls rather than four, and the fourth arrives the moment the first tag exists.

Filters are staged, then applied. Change a dropdown and an Apply filters button appears; nothing narrows until you click it. Put the dropdown back to what it was and the button goes away again, because there is nothing left to apply.

Clear filters appears only once a filter is actually applied. It drops the reviewer, type and tag filters and any group scope, and keeps your view and sort, because clearing what you are looking for should not change how you are looking at it.

Sort is not a filter. It is never counted as one, and Clear filters leaves it alone.

On a narrow screen

When the panel gets too narrow to hold the row, the dropdowns are replaced by a single Filters button that opens a sheet from the bottom of the screen. It carries a count of the filters currently applied. The view toggle stays outside the sheet.

The sheet uses checkboxes rather than dropdowns, so you can pick more than one reviewer, type or tag at a time. Multiple choices widen the result rather than narrowing it: checking two reviewers shows captures from either of them. The dropdown row is single-choice, so a multi-choice filter set in the sheet will show only its first value if you go back to a wide window.

What decides which one you get is the width of the captures panel, not the width of your browser window, so a narrow window and a wide one with a lot of chrome behave the same way.

Tags

Tags are free-form labels any member of the project can apply. They live on the capture, and the Tag filter reads from them.

Open a capture and use the Tags section: pick one of the project's existing tags, or type a new name to create and apply it in one step. The × on a tag chip takes that tag off the capture. A tag that ends up on no captures at all is cleaned up on its own, so the Tag dropdown never fills with dead entries.

Auto-tag app version

Owners can switch Auto-tag app version on from the ⚙ menu in the project's title row. With it on, each new capture is tagged with the version of the app the reviewer was running, for example 2.3.4 (16). It is an ordinary tag once it lands, so anyone can take it off, and it makes “show me everything from last week's build” a single filter click.

Select mode, archiving and batch moves

Click Select in the filter row to switch the gallery into selection mode. Cards and rows stop opening when clicked and start checking on and off instead. With a card focused, the space bar toggles it too.

With captures selected you get two batch actions:

• Archive or Unarchive, depending on what you have selected. The button reads Archive when everything selected is live and Unarchive when everything selected is archived. A mixed selection disables it: pick one direction at a time.
• Move to group…, which moves everything selected into an existing group or into a new one.

Click Cancel to leave selection mode. Switching between grid and list keeps your selection, since both views are showing the same captures.

Archived captures move into a collapsed Archived section at the bottom of the gallery, with a count. You will see it in grid and list, and inside a single group when you open one from the storyboard. It is deliberately absent from the storyboard canvas itself, where a project-wide archive pile sitting under a wall of groups belongs to none of them. The current filters and sort apply inside it exactly as they do above it, so a reviewer filter narrows both, and inside a group it shows only that group's archived captures. Unarchiving from the gallery goes through the same selection mode; a single capture can also be unarchived from its own page.

Archiving is a tidying action and nothing more. It does not pause, extend or otherwise change how long a capture is kept. An archived capture ages out on exactly the same schedule as a live one.

Any project member can archive, unarchive, tag and move captures. Only the owner can delete the project itself.

The capture page

Click a capture to open it in full. The media fills the page, and a rail beside it holds:

• The media. A screenshot opens with the reviewer's markup on it, and a toggle switches between Annotated and Original. A recording opens in a player, with the reviewer's narration in the video's own audio.
• Note, if they typed one.
• Group, showing which group this capture is in, with a control to move it to another group or to a new one.
• Tags, to add or remove labels.
• Captured, and then the context filled in automatically: device model, OS version, app version and build, screen size, and the length of a recording. This is what lets you reproduce what the reviewer saw without asking them what phone they own.
• Archive or Unarchive for this one capture, at the bottom.

The ← Back to gallery link returns you to the gallery exactly as you left it: same view, same filters, same sort, same group.

Timestamps everywhere in the app render in the timezone saved on your account. Set it on the account page.

Recent activity

Above the captures module, a horizontal strip shows the last 10 captures in the project, newest first, and scrolls sideways on its own without moving the page. Click one to open it.

The strip deliberately ignores your filters, sort, and any group you have drilled into. It always answers the same question: what has landed here lately.

Over-cap captures

Captures are never turned away because you have hit your monthly capture allowance. They are saved as normal, and the media on the ones over the cap is covered by an upgrade prompt in the gallery until the plan is upgraded or usage falls back under the limit. The facts around the capture, who sent it and when, stay visible throughout. Project owners see a banner explaining this above the captures.

Storage is the one limit that does turn captures away. See Plans and billing.

Expiry and export

Captures do not live forever: each plan keeps them for a set window. See Plans and billing for the numbers and the grace period.

Project owners get a warning at the very top of the project page when captures are close to the end of that window. It has two states, and they differ in wording and in icon, not only in color:

• Within three days: an outlined warning triangle, and a line like “3 captures expire within 3 days.”
• Within 24 hours: a filled triangle, heavier text, and “3 captures will be deleted in less than 24 hours. Export them to keep a copy.”

A matching notice appears on your dashboard, counting across all your projects, with a link straight to the export when only one project is affected.

To keep a copy, use Export project data in the project's ⚙ menu. It downloads a ZIP of every capture's media plus a metadata.json describing them, built at the moment you ask for it. The export includes captures that have already aged out of the gallery but are still inside their 30-day grace window, which is the last chance to get them.

Export is owner-only.

Need a hand?

Use the support form.