Tags vs folders: when one link needs two homes

A folder gives each bookmark one home; a tag is a label, and one link can carry several. Folders work while every link has one obvious place to live, and tags work once the same link belongs to two projects at the same time.

What is the difference between tags and folders?

The difference is how many places one link can be: a folder holds it in exactly one, and tags let it appear under as many labels as you give it. A folder behaves like a directory on disk. Filing a link means deciding where it lives, and moving it to another folder takes it out of the first. A tag behaves like a sticker. Adding a second tag leaves the first one where it was, and the link shows up under both.

Browsers organise bookmarks with folders. Google's help page for Chrome bookmarks describes creating folders and moving bookmarks into them, and documents no tags or labels. Apple's Safari guide describes sorting bookmarks into folders on Mac and iPhone.

Why do bookmark folders stop working as a collection grows?

Folders stop working because every link has to pick one home, and the more links you keep, the more of them honestly belong in two. An article on pricing pages is research for the website redesign and also for the launch plan. Filed under one, it is missing from the other, and months later you look in the wrong place first.

Here is where each browser makes you choose that home.

In Chrome on a computer:

1. Create a folder from the Bookmark Manager (More > Add new folder), or right-click the bookmarks bar and choose Add Folder.
2. Move a bookmark by dragging it into a folder in the Bookmark Manager, or choose More > Edit on the bookmark and pick a folder.

In Safari on Mac:

1. When you add a bookmark, choose its folder (the default is Favorites), and optionally rename it and add a description.
2. Later you can move, rename, copy or delete bookmarks and folders, and create new bookmark folders.

In Safari on iPhone:

1. Create folders and move a bookmark into one.
2. Rename, reorder or delete bookmarks.

Once folders stop scaling, most people fall back on search. Chrome lets you search bookmarks from the address bar: type @bookmarks, press Tab or Space, then type your keywords. Safari on Mac has a search field at the top of the bookmarks sidebar that searches bookmarks by name. Search finds a link when you remember its name. It does not tell you which links belong to a project.

Safari on iOS 27 and macOS 27 adds one more option: with Apple Intelligence, bookmarks and Reading List items are grouped automatically into suggested topics when three or more are related. Those groupings are made for you, not labels you choose, and Apple Intelligence on iPhone needs an iPhone 15 Pro, iPhone 15 Pro Max or an iPhone 16 model or later.

How do I keep one link in two projects?

With folders you keep two copies, one per folder; with tags you give the one link two labels. Safari's Mac guide lists copy among the things you can do to a bookmark, so a copy can go into the second folder. That leaves two entries to keep in step by hand.

Shareling takes the tag route. Its interface says "folder", but ruling S-06 in the product's design record reads "A folder is a tag", and each link carries a set of folder names instead of a single parent. To file one link under two projects from an iPhone or iPad:

1. Open the share sheet on the page and pick Shareling.
2. In the field that reads "Add a note or add to folder", type #redesign followed by a space. The name leaves the text and becomes a chip.
3. Type #launch followed by a space for the second project. Tap a chip if you want to remove it again.
4. Write a note if you like, then choose Self and tap Send. At launch you can choose a person here instead; sending to a person is designed but not built yet.

Any words that are not # names become the note. The share sheet keeps the chips and the note apart, so #redesign pricing ideas files the link under redesign and sends "pricing ideas" as the note.

On a Mac, Shareling's library has an "Import topics from Chrome" action that reads your Chrome bookmarks and turns folders into Shareling folders. A bookmark gets every folder on its path, not only the innermost one. A bookmark saved under Bookmarks bar > Work > Research lands under both Work and Research, because the importer records each folder name below the root, outermost first. Chrome's structure becomes two labels you can use separately.

The import has one limit. If the same page sits in two Chrome folders, Shareling keeps the first bookmark it reads and skips the later one, listing it as "same page as an earlier bookmark in this file". The skipped copy's folders are not merged onto the kept one, so check links you had deliberately filed twice.

How does Shareling handle a label (the # rules, case, length)?

Shareling strips a leading #, keeps the name as you first typed it, matches names without regard to case, allows spaces, and refuses names longer than 64 characters. These are the rules in its Topic type, the code behind every folder:

• The # is optional. Leading and trailing whitespace is trimmed, then one leading # is removed, so #inspiration and inspiration name the same folder.
• Case is kept for display and ignored for matching. Equality, sorting and hashing use a lowercased copy of the name. If you create Design and later type design, you get the existing folder, still spelled Design.
• Spaces are allowed. A folder called read later is one folder, not two. Runs of spaces inside a name collapse to a single space.
• 64 characters is the ceiling. A longer name is refused. The source code calls this an inferred limit, one no user story asked for. When a Chrome folder name is too long, the import still brings the link in without that folder and lists it with the reason.

One gap between the rules and the share sheet: when you type a folder after #, the name ends at the first space. #read later files the link under read and puts "later" in the note. A folder with a space in its name currently arrives through the Chrome import.

Favorites and Read later are not folders in Shareling. Each is its own private flag on a link, so starring something never adds a folder.

Who sees my labels when a link is shared?

Only you see your folders; they are private to the person who applied them and never travel with the link. When you send a link, the other person receives the link and your note, not how you filed it. They can file it under folders of their own, and you never see those either.

This is ruling S-04: "Tags are private to whoever applied them and never travel. The note travels and is a field on the link record, written once at send time." In the code, a link record has no field for folders. Your folders sit in your own annotation of the link, kept in your own private zone and never written to the sender's. The same record holds read state, and because it is yours, Shareling has no read receipts (ruling S-07).

The reasoning in the ruling is that "filing is honest only when unobserved". Put plainly: a label like "later, maybe" is only useful if you can write it without the sender reading it. The cost: you cannot build one shared project folder with someone in Shareling. A channel runs between exactly two people, and the note is how you tell the other person why a link matters. If you and a partner want the same links grouped the same way, each of you files them under your own folders.

The guides and features indexes list the other Shareling walkthroughs.