Skip to content
notionsolutions

A practical library for building,
organizing and working in Notion.

Workflow guides

Notion Tags: How to Add, Edit and Filter Them, and When to Use a Tags Database

A Notion tag is an option in a Select or Multi-select property, so tags live on database pages. Add a Multi-select, edit and lock the list, filter and color views by tag, handle pages outside a database, and build a shared Tags database only when two or more databases need the same tags.

Published
Blank white ceramic tags on brushed-steel rings beside a clear glass block and one electric-blue glass tag, and the headline Where Notion tags should live
Keep tags in one database's Multi-select until a second database needs the same list.

A tag in Notion is an option in a Select or Multi-select property, so tags live on database pages; a plain page has no properties to hold one. To add tags, open the database, add a Multi-select property and type a tag into any page's cell. For one tag list across several databases, build a Tags database linked by relations. I'd start with a Multi-select in each database and switch only when two or more databases need the same tags, because a shared list brings export and duplication costs.

Notion's database properties help page defines Select as choosing "one option from a list of tags" and Multi-select as choosing "one or more options from a list of tags." As Matthias Frank's guide to global tags points out, neither property is named Tags. The setup work is picking the right type, deciding where the list lives and keeping it clean.

Which property should hold your tags?

A tag property answers one question about a page, usually "What is this about?" or "What kind of thing is this?" Two things decide the type: how many answers a page can have, and how many databases need the same list.

Keep separate questions in separate properties. A Topic multi-select and a Type select are each easy to filter, while one list that mixes both makes you remember which values belong to which question. The same one question, one property rule applies to every field in a database.

How to add tags to a Notion database

If the pages aren't in a database yet, create one: type /database on a page and select New empty database, as Notion's data sources and linked databases page describes. Then add the tag property:

  1. Select + next to the right-most property. In a database with no properties yet, click Add property. In table view you can also click an existing property and choose Insert left or Insert right.
  2. Name the property for the question it answers, such as Topic, and choose Multi-select. Choose Select if each page should get only one value.
  3. Click the property's cell on a page, type a tag and press Enter. Add more tags the same way, one Enter per tag. Notion assigns each new tag a random color.
  4. On every other page, click the cell and choose from the tags already in the list, or type a new one.

Notion's help page says you can add as many unique tags as you want; it gives no fixed option-count cap. The options still count toward the database's size limits. That freedom is also how lists sprawl, since a typo saved with Enter becomes one more option in the menu. Glance at the menu before you create a tag.

Notion table with a Topic multi-select property and four example notes, including two tags in one cell
A Multi-select property can hold more than one tag. Here, Revise proposal belongs to both Pricing and Proposals.

Rename, recolor, delete and reorder tags

You edit tags from inside a cell of the property:

  1. Click a cell in the tag property.
  2. Hover over the tag you want to change and click the ••• that appears to its right.
  3. Rename the tag, pick another color or delete it.

To reorder the list, drag a tag by the ⋮⋮ handle on its left. Order matters for sorting too: for Select and Multi-select properties, Notion's views, filters and sorts guide says you define the sort order yourself by clicking the property and dragging its options up or down. Put the tags in the order you'd want to read a sorted view.

Once the list settles, lock it against accidental changes. On a full-page database, select ••• at the top → Lock database. Notion's intro to databases says a locked database prevents changes to properties and value options, including the tag list. Editors can unlock it; give contributors Can edit content when they should update records without changing the tag list or unlocking the database. If you're weighing which lock to use, here's how a page lock and a database lock differ.

Show tags on the page and in each view

Tags appear with the other properties at the top of a database page. To change that, click the ••• at the top right of the page, choose Customize page and set the tag property to Always show, Hide when empty or Always hide. I'd use Hide when empty for tags: untagged pages stay uncluttered, and the field comes back as soon as a page has a tag.

Views have their own switch. Open the settings menu at the top of the database, select Property visibility and click the eye icon next to the tag property. Each view keeps its own setting, so a weekly board can hide tags while a research table shows them.

Notion View settings panel with Property visibility highlighted for a gallery named Tagged notes
Open Property visibility in each view to choose which properties appear there. This menu shows where the setting is; the property list opens next.

Filter, sort and color pages by tag

A tag pays off in a view that answers a question, such as "Which notes are about pricing?" Filter, sort, group and color sit under View settings, and each view keeps its own settings.

When a tagged page is missing from a filtered view, look past the tag filter too. With sub-items turned on, the sub-item visibility settings also change filtered results, and tracing a task missing from a filtered view walks through the checks in order.

To show one tag's pages on a dashboard or project page, add a linked view of the database there and filter it to the tag. Views, filters, sorts and groups you create in a linked view leave the original database's views alone, while edits to its properties or pages carry through; what a linked database changes in the original has the details.

Can a plain Notion page have tags?

Not as properties. A page outside a database has no property fields. One r/Notion thread asks exactly this in its title: "New to Notion, why can't Pages have tags and properties?" You have two routes, and I'd pick the first whenever the page is free to move.

Move the page into a database

Database items are pages, and Notion's intro to databases says content you drag into a database, like bullets or to-do items, turns into pages there. Before moving a private note into a shared database, check the destination’s sharing and inherited permissions. Drag the note into your Notes database and it picks up the tag property like every other entry, so filters, sorts and colors work on it too. Then open Share on the moved note and confirm who can access it. If the note needs to stay private, keep it where it is and use the @-mention route below. If loose notes keep piling up, a second brain built on three databases gives each of them somewhere to land.

@-mention a tag page

If the page has to stay where it is, create a page for the tag, such as Pricing, and @-mention it in each page that belongs under it. Notion's links and backlinks help page says backlinks are created automatically every time you @-mention a page, and you open them with {#} backlinks under the page title. On the Pricing page, that list shows the pages that mention it.

Type @ for the mention rather than adding a Link to page block. A page referenced with Link to page shows up in the sidebar as a subpage of the page where you linked it, while an @-mention works more like a hyperlink and doesn't create a subpage. Two limits keep this a fallback. Backlinks show only pages the viewer can access, so teammates won't see your private pages in the list. And a mention isn't a property, so no view can filter, sort or color by it.

Use one tag list across several databases

A Multi-select list belongs to one property in one database. A Topic property in Notes and a Topic property in Projects are two separate lists, even when the tag names match. Frank's guide makes the same point: simple tags only organize information inside the same database.

That's the build: one Tags database with a page per tag, connected to each database you want to tag by a two-way relation. For a team dashboard, check each reader’s access to the original data sources too: sharing the Tags page alone does not grant access to the databases in its linked views. If relations are new to you, how relations and rollups connect two databases explains the mechanics first.

  1. Create a database named Tags (/database → New empty database) and add one page per tag, such as Pricing, Onboarding and Proposals.
  2. In the database you want to tag, for example Notes, add a property, name it Tags, choose Relation and pick the Tags database.
  3. Turn on the Show on Tags toggle and name the matching property that will appear in the Tags database, such as Notes. Relations between two databases are one-way by default, so this toggle is what puts each note on its tag pages. Click Add relation.
  4. Repeat steps 2 and 3 for every database that should share the list, such as Projects and Reading.
  5. To tag a page, click its Tags cell, search for a tag page and choose it. To remove one, hover over it and click the minus button.

Because the relations are two-way, tagging a note from the Notes database also lists it on the tag page. Open Pricing and you'll see one relation field per connected database, holding the notes, projects and reading tagged Pricing. To choose which details of those pages appear in the field, click the field, select ••• and drag properties into Shown in relation or Hidden in relation; the choice applies to every page in the database.

Notion Notes and Tags databases with matching two-way relations between three notes and their tag pages
A two-way relation connects each note to a tag page and lists that note in the Tags database. These three example pairs appear on both sides.

Relation fields are often enough. For a tag page that works like a dashboard, Frank adds a database template to his Global Tags database with a linked view and a self-referential filter for each connected database. In Notion, click the dropdown arrow next to New at the top right of the Tags database and select + New template. On the template, add a heading and a linked view for each connected database (/database → Link to existing data source). In each linked view, filter its Tags relation with contains and select the template you are editing. When you create a tag page from the template, Notion changes that filter to the new page. Notion's May 13, 2020 release notes introduced these self-referential filters in database templates, so each tag page made from the template opens with its views already narrowed to that tag. The views come with pages created from the template, so create new tags from it; setting a template as a view's default saves picking it each time. I'd add this template only once the plain relation fields feel crowded, since every connected database adds one more linked view to maintain.

What a Tags database costs you

Notion's relations and rollups help page documents the trade-offs, and they're why I wouldn't build global tags for a single database:

Nested tags: parent tags and sub-tags

A Tags database can also hold a hierarchy, such as Marketing with Email and SEO under it. Sub-items handle that. In the Tags database, open the ••• menu at the top right and select Sub-items. Notion's guide to sub-tasks and dependencies explains that this creates a self-relating property, that you can rename the pair in the Sub-items window, and that sub-items work for "anything you need," not only tasks. Name them Parent tag and Sub-tags, then select Create.

If you'd rather start from a ready-made setup, the Nested Tag System template describes itself as using sub-items for a hierarchy of tags and a relation to connect them to notes, with filtering by parent tag, sub-tag or both. Either way, sub-items change filtering in that database: with them on, the sub-item visibility settings also affect filtered results.

I'd keep tags flat until you notice yourself adding the same pair of tags to page after page. A hierarchy is one more structure to maintain, and a flat list with clear names is easier to filter and easier to hand to someone else.

Keep the tag list clean

Compare the four ways to tag in Notion

The table sets the four methods side by side on what Notion's help center documents: how many tags a page takes, where the list lives, how you edit it, which view tools apply and what each costs when you export or duplicate.

What Notion's help center documents for each tagging method
MethodTags per pageWhere the list livesEdit, recolor, deleteView toolsDatabase searchExport and duplicationBest fit
SelectOneThe property's menu in one databaseCell → hover → •••; drag ⋮⋮ to reorderFilter, sort in your option order, conditional colorProperties are searchedNo relation to breakMutually exclusive values, such as a Type
Multi-selectAny numberThe property's menu in one databaseCell → hover → •••; drag ⋮⋮ to reorderFilter, sort in your option order, conditional colorProperties are searchedNo relation to breakTopics inside one database; the default
Relation to a Tags databaseAny number, or 1 page if you set the limitOne Tags database shared by every connected databaseEdit the tag page; remove a tag from a page with the minus buttonFilter, conditional color, rollups such as Count all on the Tags sideCovered by property search in general; relations aren't singled outCSV gives plain-text URLs that can't be re-imported; a duplicated database gets a one-way relation; a relation filled in a template repeats on every pageThe same tags across two or more databases
@-mention of a tag pageAny number, in the page textAny page you choose as the tag pageEdit the tag page; remove a mention from the textBacklinks on the tag page, showing only pages the viewer can access; no filter, sort or colorNot a propertyNo relation to breakPages that must stay outside a database

The tagging setup I'd start with

For one database, I'd add a Multi-select named for the question it answers, such as Topic, build one filtered view for the tag you check most and lock the database against accidental option changes once the list settles. Use a Select when a page can only be one thing, and Status for progress. Move to a Tags database only when the same tags have to work in two or more databases and you accept that relations export as URLs and duplicate as one-way. For loose pages, drag them into a database; @-mention a tag page only when a page has to stay where it is.

Notion stores any tag you type. Deciding which tags deserve to exist, and retiring the ones that don't, stays with you.

Organize records with tags