features··3 min read

Sub-Collections: Add One More Level of Organisation

Sub-collections let you group related collections under a parent without overcomplicating your hierarchy. Here's when to use them and how.

Share:XLinkedIn

Collections organise your bookmarks by topic. Sub-collections take that one step further — grouping related collections under a parent so your sidebar stays clean even as your library grows.

How sub-collections work

In Recallio, sub-collections are one level deep. A collection can have sub-collections, but sub-collections can't have their own children. This constraint is intentional — deep nesting is one of the main reasons bookmark systems become confusing.

Frontend (parent)
  └── React
  └── CSS
  └── Performance
  └── Browser APIs

In the sidebar, parent collections are collapsible. You can expand Frontend to see its sub-collections or collapse it to keep the sidebar clean.

Creating a sub-collection

  1. Right-click any existing collection in the sidebar (or click the three-dot menu).
  2. Select Add Sub-Collection.
  3. Name it and click Create.

Alternatively, create a new collection and set the Parent Collection dropdown to an existing collection.

Moving a bookmark between sub-collections

There's no per-card right-click or drag-and-drop for this yet — select the bookmark's checkbox (or select several at once), then use the bulk action bar's Move to collection button. The destination picker shows the full hierarchy including sub-collections, so you can move directly to any level.

What system collections can't do

The three system collections (Unsorted, Read Later, Archive) cannot be parents or children. They're permanent and flat. Sub-collections are only for the collections you create.

When sub-collections help

Sub-collections are most useful when:

  • A top-level collection would get too large: If your "Development" collection has 500 bookmarks, splitting by language or framework makes browsing much faster.
  • You have related but distinct topics: "Marketing" might have sub-collections for "SEO", "Email", "Social Media" — related but different enough to want separate views.
  • You're managing a project with multiple phases or areas: "Project X" → "Design", "Research", "Implementation".

When to avoid sub-collections

Avoid nesting for its own sake. If a sub-collection would only have 5 bookmarks, it's probably better to use a tag instead. Sub-collections add navigation overhead; tags are lighter.

A simple test: if you often want to browse a group of bookmarks together, make it a (sub-)collection. If you mainly want to filter across multiple collections, use a tag.

Renaming and deleting sub-collections

Right-click → Rename to rename. The collection slug updates automatically, and any existing bookmarks remain in the collection (they follow the rename).

To delete: right-click → Delete. You'll be prompted to choose what happens to the bookmarks inside — move them to the parent collection, move to Unsorted, or delete them too. Bookmarks are never deleted without explicit confirmation.

The right amount of structure

The goal isn't a perfect taxonomy — it's fast retrieval. A flat structure with good tags often works better than deep nesting. Start with top-level collections and add sub-collections only when a collection grows large enough that browsing it feels slow.

Most users find 3–6 top-level collections with 2–4 sub-collections each is the sweet spot. That's enough structure to organise thousands of bookmarks without the sidebar becoming a maze.

Share:XLinkedIn

Related articles

Ready to organise your bookmarks?

Join Recallio — free to get started, no credit card required.

Get started free