Zettelkasten IDs: Choose Stable Identifiers for Linked Notes

A Zettelkasten ID is a stable identifier that lets you refer to one note even when its title or location changes. Choose a scheme that produces a different ID for every note, keep that ID unchanged, and make sure you can search for it outside your usual navigation.

The purpose is dependable references, not elaborate numbering. When an idea informs active work, fenbs can retain its source reference beside reviewed project context, decisions, and next steps. Keep the original note in the system where you read and develop it.

How do you choose and test a note ID?

1. Choose the scope: one personal collection, several collections, or a shared archive. An ID must be unique wherever you expect to resolve its references.
2. Pick one simple format, such as a sequence or timestamp, and write down how duplicates will be prevented.
3. Create two sample notes and link one to the other. Include a readable title alongside the identifier so the reference makes sense to you.
4. Rename and move the target note using the normal controls in your app. Follow the original link, then search for the ID to test a second way to find it.
5. Export a small sample if portability matters. Check that the ID remains visible and that you can identify the target without relying on memory.

Run this small test before renaming hundreds of files. Your app may already provide stable document links, or it may update links when filenames change. Neither behavior should be assumed across every export format, external document, and shared copy.

Which ID schemes are practical for everyday notes?

Several schemes work. Pick according to how notes are created and shared, then spend your time writing useful connections. The examples below illustrate possible formats; they are not requirements of the Zettelkasten method.

Christian Tietze’s explanation of note identity↗ (opens in a new tab) describes his timestamp-based approach and distinguishes a note’s identity from its file representation. That distinction is useful even if you choose another format: an identifier answers which note you mean, while a filename describes one way it is stored.

Why keep a title if the note already has an ID?

The title tells you what the note contributes. The ID tells you which note it is. A reference such as “N0042: Examples reveal missing instructions” is easier to understand than a bare number, especially in a manuscript, a project summary, or a conversation with a colleague.

Change the title when your understanding improves, but keep the identifier. Do not encode a temporary folder, project status, or evaluation into the ID if those things are likely to change. A note can remain the same note while becoming relevant to a new project or supporting a more careful conclusion.

Keep the original source reference separate too. Your own note might be N0042, while the evidence comes from a particular article section or book page. The ID finds your thinking; the citation lets someone check the material that informed it.

For adjacent writing and capture questions, see the note template, Apple Notes setup, atomic notes, daily notes, and fleeting notes guides.

What happens when you rename or move a note?

It depends on how the link identifies its target. A link based on a filename may need updating after a rename. A document link may depend on the app retaining the same underlying document. Copying the text into a new document can create a different target even when it looks identical.

Obsidian documents automatic internal-link updates↗ (opens in a new tab) when files are renamed, with a setting to control that behavior. It also warns that its block references are specific to Obsidian. Test the exact kind of reference you use rather than treating every link as equally portable.

If you maintain IDs as plain text, keep the ID in the note when moving it. Search can then provide a fallback even if a clickable link breaks. For a shared collection, record where to search and who has access; a correct identifier is of little help when its target is in an unknown private account.

How do you handle duplicates and merged notes?

Treat duplicate IDs as a small maintenance problem to resolve before more references spread. Confirm that two separate notes share the same identifier, assign a new ID to one, and repair the references that meant that note. Do not silently assume every reference pointed to the first search result.

When merging notes, keep a short pointer at the retired ID if existing references may still use it. Explain which note replaces it. When splitting a note, retain the old note as a brief guide to the new ones if that preserves the meaning of old citations.

Avoid recycling an old identifier for an unrelated idea. Someone returning through a draft, saved conversation, or project record should find the original meaning or an explicit explanation of what changed. A compact archive is not worth a misleading reference.

What should you save beside an ID for AI-assisted work?

Save a readable title, a usable location, and the specific insight the project relies on. Include its limits and the part of the source that supports it. An assistant cannot infer what you accepted merely from a number and a link, and it may not have access to the note app.

Say a design project uses N0042 to justify adding examples to instructions. The project record should say which instruction needs an example, why the note is relevant, and what a person approved. fenbs keeps those references and current work context together without requiring the whole research archive to become a task list.

How to do this with fenbs

1. Create a free account and add the project that uses your research.
2. Save useful source references in Links and listings. Include the note ID and readable title where those help you identify the material.
3. Write a context note explaining the accepted finding and its limitations. Record a person’s project choice in Decisions and rules, and add the task that follows.
4. Connect a supported AI app through Integrations. Ask it to read the current context and verify that it can access any source needed for its task.

fenbs does not assign identifiers to your external notes or repair their links. A note app is sufficient if you only need a personal archive. Use fenbs when reviewed ideas need to stay connected to decisions and ongoing work; see the second-brain guides for that wider workflow.