When You're Done with a Note, Move It — Don't Click 'Archive'

An "Archive" button inside a note app marks a flag the operating system cannot see. A folder named Archive/ is the open-format version of the same idea — it works in any reader, it is queryable with one shell command, and it survives every app. Move the file. Skip the flag.

The POSIX mv utility is older than every note app you have ever used and is specified to do exactly one thing well: "the mv utility shall move the file named by the source_file operand to the destination specified by the target_file." ¹ The same spec promises that "the time of last data modification and time of last access" are "duplicated for each file in the hierarchy" ². A mv ~/notes/Projects/old.md ~/notes/Archive/ keeps the file, keeps its mtime, and adds zero vendor metadata. The plugins that ship a button for this — Simple Archiver and Note Archiver in the Obsidian ecosystem — both archive to a real folder, then fall back to it cleanly when the plugin is gone ^{3 4}. The button is a convenience. The folder is the contract.

The single habit — move the file, do not flag it

When a note is done, move it. Open your file manager or your shell, and move the file from where it lives to a folder named Archive/. That is the whole habit. The file stays on disk, in plain Markdown, with its original modification time intact. Nothing depends on the app you wrote the note in surviving next year.

A note is "done" in three ordinary ways. A project finishes — you shipped it, you abandoned it, the client paid the invoice. A draft goes cold — you stopped editing it months ago and you keep scrolling past it. A topic leaves your daily desk — the company you were tracking got acquired, the conference you were planning is over. In every one of those shapes, the right action is the same one verb in a different folder.

Bruno Paz, writing about his own plain-text vault, names the function exactly: "The Archive folder is where I keep notes that are no longer relevant or useful for my daily activities. This can be notes related to old projects that I have finalized, ideas that are no longer relevant, etc. I might prune this folder periodically to avoid clutter." ⁵ The same essay states the lifecycle in one line: "Tempoary content that is no longer relevant will be deleted or Archived. Content that I want to permanently save, I will clean up and move to the appropriate location, into other folders." ⁶ (The "Tempoary" is the author's; preserved verbatim.) The folder is the noun. The move is the verb.

The folder approach is the convention every 2026 Obsidian guide teaches. Studio Obsidian's PARA-method walk-through labels the bin directly: "📁 Archives — Inactive items / Everything that is no longer active. Projects end, areas get deprioritised, resources become outdated — they all go here." ⁷ Obsibrain's 2026 guide tells PARA users to "archive completed projects by adding status: archived to properties and moving them to an Archive folder" ⁸ — frontmatter as an optional alternative, the folder as the primitive.

The five-minute version — the move primitive

The workflow is four steps. Decide the note is done, move the file with mv, verify it landed with ls -lt, and run the one durable query a vendor flag cannot answer with find -mtime. Three of the four are one shell command apiece; the fourth is the thought that says the note is finished.

# 1. Decide — this note is done. (You.)
# 2. Move — one POSIX command (Stat 1).
$ mv ~/notes/Projects/website-redesign.md ~/notes/Archive/

# 3. Verify — the file is there, the mtime is intact (Stat 2).
$ ls -lt ~/notes/Archive/website-redesign.md

# 4. Query — the question a plugin's "archive flag" cannot answer.
$ find ~/notes/Archive -mtime +365 -name "*.md"

The GNU find man page describes the time predicate plainly: "-mtime n File's data was last modified less than, more than or exactly n24 hours ago."* ⁹ +365 means "older than a year." The query takes no setup, no plugin, no index, no account — it works on macOS, Linux, and Windows Subsystem for Linux against any folder of files. A reproducible demo, with deliberately back-dated mtimes, confirms the contract:

$ mkdir -p /tmp/demo/Archive
$ touch -d "2 years ago" /tmp/demo/Archive/old-project-notes.md
$ touch -d "2 days ago"  /tmp/demo/Archive/recent-archived.md
$ find /tmp/demo/Archive -mtime +365 -name "*.md"
/tmp/demo/Archive/old-project-notes.md

One file appears. The recent one does not. The same recipe runs unchanged on every Unix-shaped operating system, against any folder of Markdown, against any author's vault layout.

The thirty-minute version — wiring the folder into your vault

A weekend version of the workflow makes the move repeatable for the next decade. Pick five conventions once — the path, the depth, the cadence, the filename, and an optional frontmatter — then stop deciding. The whole point of a primitive is that the choices around it become the kind you do not have to renegotiate at every archive.

Pick a path. The folder can be Archive/ at the vault root (the PARA convention), 04 - Archives/ (the numbered-PARA convention used by several community guides), or _archive/ (the leading-underscore convention some users prefer so the folder sorts first or last in their file tree). The label is preference; the primitive is mv. The post you are reading uses Archive/ for examples.

Pick a depth. Two reasonable patterns: flat (Archive/old-project.md) and year-month (Archive/2024/11/old-project.md). The Obsidian Note Archiver plugin's signature feature is the year-month grouping — its README states: "It can also group the archived files based on the year and month the file was archived." ⁴ That same grouping is one mkdir -p ~/notes/Archive/$(date +%Y/%m) away from being app-independent. Daily-note vaults graduate naturally into Archive/YYYY/ once the year closes.

Pick a cadence. A monthly archive review — fifteen minutes, the first of the month — is enough to keep Projects/ honest. Bruno Paz's "I might prune this folder periodically" is the operative phrase ⁵. The cadence is yours; the recipe is mv.

Pick a name discipline. Filenames that survive the move stay queryable. YYYY-MM-DD-slug.md filenames sort by date, grep by keyword, and remain unambiguous after a year in the bin. Pair the archive folder with a durable filename convention so find and grep still answer questions long after the human context is gone.

Pick a frontmatter, if you want one. A status: archived line at the top of each archived file is a valid alternative — searchable with grep -l "status: archived" -r ~/notes, durable in any frontmatter-aware tool, and a strict improvement only if you have a tool that reads YAML. It is not better than the folder; it is the second key on the same door. The folder is the on-disk noun; the frontmatter is the in-file label. Use one, the other, or both.

How to ask the question a plugin cannot answer

The single argument for a folder over an in-app archive flag is the query you can run a year later, without opening the app. A flag inside a note app is invisible to find, grep, every backup tool, and every future agent. A folder is none of those — it is a noun the operating system already knows.

A year from now, the durable questions sound like this. Which finished projects from last year are still around? find ~/notes/Archive -mtime +365 -name "*.md". Which archived notes mention "redesign"? grep -lr "redesign" ~/notes/Archive. What did I close out in November 2024? ls -lt ~/notes/Archive/2024/11/. How much of the vault is closed business? du -sh ~/notes/Archive. Every one of those answers comes from utilities that have outlived a generation of note apps. An app-only archive flag answers exactly none of them — until you re-open the app that knows what the flag means.

This is also where the Obsidian plugins prove the spine, not contradict it. Mike Farr's Simple Archiver README is direct: "Simple Archiver moves files or an entire folder to an archive folder that you configure. The items are moved to the same relative path in the archive folder." ³ His project tagline is funnier: "Move old, stinky notes and folders to an archive, where they belong!" ¹⁰ The plugin saves two clicks. The plugin's output is a folder. When the plugin is gone, the folder is still there. The button is a convenience over the primitive; the primitive is the contract.

Common mistakes

Five anti-patterns will eat the workflow if you let them through. The first three confuse archive with adjacent jobs the operating system already does well; the last two confuse "filed" with "finished." Each one is easy to name and easier to avoid once named.

1. Treating archive as backup. Moving a file from Projects/ to Archive/ keeps it on the same disk. A failing drive kills both folders at once. Archive is housekeeping; backup is survival. For the second job, use the 3-2-1 rule — three copies, two media, one off-site.
2. Treating archive as delete. A move to Archive/ is permanent-until-you-decide. The operating-system trash, in contrast, is a reversible drawer the OS owns for you, with its own recovery window. The two have different intents. The diptych is trash for oops, archive for done.
3. Trusting a vendor's "archive flag" outside its app. A flag inside a note app is invisible to find, grep, every backup, every future LLM, and every future you who opens the file in a plain editor. The flag may travel with the file in a vendor export; very often it does not.
4. Forgetting that cloud-sync can strip mtime. POSIX mv preserves modification time on the local filesystem ². Dropbox, iCloud, and OneDrive sync-back routinely re-stamp the file's creation timestamp to the sync time on the receiving device. Date the file inside its frontmatter or its filename too, so the durable copy of "when" travels with the bytes.
5. Archiving as procrastination. The Archive folder is for finished work, not for ducked decisions. If a note is unfinished, the right move is to finish it or delete it — not to slide it sideways into permanent storage so future-you inherits the call.

The capture graveyard underneath that fifth mistake is real and current. A January 2026 Ask-HN — "Do you also 'hoard' notes/links but struggle to turn them into actions?" — reached 235 points and 217 comments ¹¹, renewing the older 598-point thread that triggered the deletion wave ¹². The Archive folder is the answer that sits one click earlier than nuking the vault: a place to put the finished work, a place to put the work you are willing to lose track of, and a habit that keeps Projects/ honest without burning down the rest. If the deletion question is the one you are sitting with, "I deleted my second brain" is the longer read.

How this works without a special app

The same Archive folder works in every editor that opens Markdown. Open it in VS Code, in MacDown, in Vim, in a plain file manager, in a future tool you have not heard of yet — the files are still files, the move is still a move, the query is still find. Nothing depends on an app being alive.

Steph Ango, the Obsidian CEO writing on his personal site, framed the underlying principle as a one-line philosophy: "File over app is a philosophy: if you want to create digital artifacts that last, they must be files you can control, in formats that are easy to retrieve and read." ¹³ The follow-on line is the part you tape to your monitor: "Apps are ephemeral, but your files have a chance to last." ¹⁴

That is the calmer message under the workflow. The button inside a note app is a UI affordance over the OS primitive. The OS primitive is mv. Choose the affordance that vanishes when the app does, or choose the one that doesn't. Both lead to the same folder; one of them needs the app to know what to do next.

How this fits MNMNOTE

MNMNOTE keeps notes as plain Markdown on your own device. Archive in MNMNOTE is the same mv from one folder to another inside the same vault — the same on-disk file, the same modification time, the same shell-queryable bytes. That is the whole integration story.

A vault that is a folder of .md files inherits everything else this post described for free. The folder is mountable in any backup tool, scannable by any future agent, and openable in any other Markdown editor you have installed. The Archive folder you build today still answers find -mtime +365 next year, whether or not the app you started in still exists.

What changes after thirty days

Three things change after a month of moving instead of flagging. Projects/ gets shorter, because finished work stops crowding the active work. Archive/ becomes a useful index of what got done — a folder you can grep, find, and ls -lt like any folder of bytes you own. The question of leaving the app stops being open for finished notes.

The third effect is the quiet one. A note that lives in a folder named Archive/ does not need anyone's permission to be archived next decade, because "archived" is no longer a flag inside a particular app — it is a location on a disk you own, in a format the operating system has been able to read since long before the app existed. The button inside an app is a UI affordance over that primitive. The folder is the primitive itself.

Frequently Asked Questions

Should I delete or archive old notes?

Archive is the gentler answer to "I don't want this in my way but I'm not ready to lose it." Move it to Archive/. Delete only after the file has aged past a threshold you decide — for example, anything in Archive/ older than two years (find ~/notes/Archive -mtime +730 -name "*.md") goes to the OS trash, where the recovery window covers any second thoughts.

How should I archive notes in Obsidian without a plugin?

Drag the file from its current folder to a folder named Archive/ in your vault sidebar — every drag is a mv underneath. Or run mv ~/notes/Projects/old.md ~/notes/Archive/ in a terminal. Wikilinks resolve vault-wide in Obsidian, so existing [[old]] references continue to point at the file after the move. The folder is the workflow; no plugin is required.

Where do I put completed projects in my vault?

In a folder named Archive/ at your vault root, or 04 - Archives/ if you follow numbered PARA, or Archive/YYYY/MM/ if you want grouped retrieval later. The path is convention. The primitive is mv. Studio Obsidian's PARA walk-through calls the bin "📁 Archives — Inactive items" and tells you to "move it to Archives when done" ⁷.

Do I need an archive plugin for Obsidian?

No. The two community plugins — Simple Archiver and Note Archiver — save two or three clicks and add an optional year-month grouping pattern. Both archive to a real folder underneath, and both fall back to a plain folder cleanly when uninstalled. They are conveniences over mv; the convenience may be worth two clicks to you.

How do I find notes in my archive that are older than a year?

find ~/notes/Archive -mtime +365 -name "*.md". The GNU find man page documents -mtime n as "File's data was last modified less than, more than or exactly n24 hours ago"* ⁹. The same command works on macOS, Linux, and Windows Subsystem for Linux against any folder of Markdown — which is why the folder beats the in-app flag for everything except the click count.

Is moving to the Archive folder the same as deleting?

No. Archive is permanent-until-you-decide — the file stays on disk, in your vault, indefinitely. Delete drops the file into the OS trash, which is a separate reversible drawer with its own (operating-system-defined) recovery window. Pair the two: trash for oops, archive for done.

Will an Archive/ folder break wikilinks or backlinks?

In Obsidian, [[NoteName]] is path-independent and resolves vault-wide, so moving a note to Archive/ keeps its backlinks live — moving the file does not silently break references. That convenience is an app feature, not a guarantee of the Markdown spec; CommonMark and GFM links are path-relative and will not auto-resolve across a move.

References

If you want the archive folder to outlast every note app you ever try, write the kind of files that live in folders. When you archive a note in mnmnote.com, the file moves from one folder to another in your own vault — a plain Markdown file the rest of your operating system already knows what to do with.