Editing & Content
When should I use a query instead of a collection?
Editing & Content
When should I use a query instead of a collection?
You decide what goes in a collection. A query includes every note that matches a rule you set. It makes maintenance much easier.
How to choose
We recommend a collection when:
- You want full control over exactly what is in the set
- The group stays within a single object type
- What is on the list changes because you add or remove items, not because a date or status changed
We recommend a query when:
- What is on the list follows clear rules (finished this year, linked to this project, tagged
#to-watchand#video) - The set should update on its own as you work
- You want the same filter on a dashboard, inside a project page, or in a template
You can use both on the same type. For example, keep a Recommend this month collection on Images for a list you build by hand, and a query on Images filtered by Category for every handwritten note scan. The collection stays manual; the query stays automatic.
Tags and object types
Collections cannot span object types. If you need one theme across pages, quotes, and weblinks, use tags or a query filtered by tags instead of a collection.
Queries are Pro
Saving and reusing queries is part of Capacities Pro. Collections are available on all plans. If you are on the free tier and hit the limit, you can still use filters on object dashboards; you save them as named queries once you upgrade.
Examples
| Goal | Better fit |
|---|---|
| Every book you finished in 2025 | Query on Book type, filter Finished on |
| Five papers you pick for students this term | Collection on a Paper or Weblink type |
| All meetings for the project you are viewing | Query embedded on the project, with a variable filter |
#to-watch videos only | Tag page, or a query with that tag plus any extra filters |
| A shortlist you rearrange by hand | Collection |
Concrete setups (bookshelves, project pages, tag combinations, and similar patterns) are in Queries examples.
Ask a question! - The Docs Assistant knows everything about the documentation, and the ideas and feature requests from other users.
Create a ticket on our feedback board. - Let us know if you have an idea for a feature, improvement or think there is something missing.
Request additions to the documentation. - If your questions are not getting answered, let us know and we will extend the documentation.