Cards, Stacks, and Lists: What’s the Difference?
Learn the fundamental building blocks of Stacklist.
Written By Kyle Hudson
Last updated 3 days ago
👉 Cards
A card is the fundamental unit of Stacklist. Every link you save becomes a card.
Each card can include a title, description, tags, and an image — making it easy to recognize and organize later. Think of it as a bookmark, but with context.
Cards can be anything with a URL:
A restaurant you want to try
A product you're considering buying
An article to read later
A place you want to visit
Example Cards (Single Places, Things, Products, etc)
👉 Stacks
A stack is a collection of cards grouped around a theme, topic, or purpose.
Stacks can be private (only visible to you), shared with specific people, or made fully public for anyone to discover.
Some examples of what a stack might look like:
"Best Food in Austin" — a curated guide to restaurants
"Design Inspiration" — a collection of sites and references
"Reading List" — articles and essays saved to read later
Example Stacks (Group of related Cards)
👉 Collections
A collection is a group of stacks organized under a broader category.
If stacks are chapters, collections are the book. They're useful when you have multiple stacks that belong together under one theme.
For example, a collection called "New York Favorites" might contain stacks like "Restaurants," "Things to Do," and "Places to Stay."
Collections are available on the Curator Plus plan and above.
Example Collections (Collections of related Stacks)
All my book Stacks
All my New York related Stacks
⚒️ How They Work Together
Everything in Stacklist flows from the bottom up:
Save a card — grab any link and save it with notes and tags.
Organize into stacks — group related cards into a themed collection.
Arrange into collections — bring related stacks together under a broader category.
The result is a structured, searchable, and shareable library of everything you care about on the web.