The payoff of fixing this is concrete. You get notes you can still open in twenty or thirty years with whatever software exists then. You avoid lock-in to one company and its pricing changes. And you hold files you own outright, stored where you decide, readable by any editor and by your own local AI. Some writers call a collection like this a “second brain”, a term popularized by Tiago Forte’s productivity book. This article uses plainer words: notes, notes library, and personal knowledge base.

Why a Single App Is a Weak Home for Lifelong Notes

Software companies are businesses, and businesses change. Evernote offers a clear example. Bending Spoons agreed to acquire it in November 2022, closed the deal in January 2023, and laid off 129 employees the following month. In December 2023, the free plan dropped to a maximum of fifty notes and one notebook per account, down from limits that had allowed up to 100,000 notes.

Evernote is one case among many. Google shut down Google Reader in 2013, and many smaller tools have closed or pivoted since. Apps still have value, but an app should be treated as a lens for viewing your notes, while the notes themselves live somewhere you control. When the lens breaks, you swap it for another one and keep your eyes.

Five Layers of a Long-Lasting Notes Library

A useful way to think about durability is as a stack of five layers: format, identity, links, copies, and publication. Each layer answers one question, from whether future software can read the file to whether a note should be public and permanent.

You can adopt the layers one at a time. Fixing the first two layers alone makes a large difference.

Layer One: Format

The most durable everyday format for personal notes is plain text, and Markdown is the most popular way to add light structure to it. A Markdown file is readable by a person even with no special software. The CommonMark specification gives the syntax a stable public definition, which reduces the risk of one tool interpreting your files differently from another.

For finished documents meant for long term preservation, institutions often prefer richer formats. The Library of Congress Recommended Formats Statement lists XML based markup, EPUB3, and PDF/A among its preferred formats for textual works, with plain text as an acceptable format. A sensible personal rule follows from this: keep working notes in Markdown, and when a piece becomes finished, export a PDF/A or HTML copy alongside it.

Layer Two: Identity

Every note needs a stable identity that does not depend on a database. The simplest method is a file name that combines a date stamp with a short title, such as 20261009-durable-notes.md. Date stamps sort naturally and rarely collide.

Identity also includes metadata. A small block of key and value lines at the top of each file, often called front matter, can record tags, a source URL, and a created date. Because front matter is plain text, any future tool or script can read it. Avoid storing important facts only in a colored label or proprietary field, since those rarely survive an export.

A Folder Layout You Can Copy

A simple structure keeps identity and privacy clear from the first day. The layout below uses one top folder, a few subfolders, and date-stamped file names:

• notes/ as the top folder for everything
• notes/inbox/ for quick captures, such as 20261009-podcast-idea.md
• notes/library/ for lasting notes, such as 20261009-durable-notes.md and 20250314-reading-habits.md
• notes/index/ for one map per topic, such as index-writing.md and index-health.md
• notes/attachments/ for images and PDFs, named to match their note, such as 20261009-durable-notes-diagram.png
• notes/public/ for finished pieces you are happy to publish
• notes/archive/ for PDF/A or HTML exports of finished work

Lowercase names with hyphens instead of spaces work on every operating system and in web addresses. Keep the tree shallow so links survive reorganizing.

Layer Three: Links

Links are what turn a pile of notes into a personal knowledge base, and they are also the first thing to break during a migration. The wiki style double bracket link, which places a note title inside two pairs of square brackets, is now supported by many tools, including Obsidian and Logseq. Standard Markdown links that point to a relative file path are even more portable, since nearly every Markdown renderer understands them.

Two habits protect links over time. First, link to the stable file name rather than to a heading or a block identifier that only one app understands. Second, keep a plain index note for each major topic that lists its key notes in order. If every automatic backlink feature vanished tomorrow, these index notes would still give you a readable map of your own thinking.

Layer Four: Copies

Format and links mean nothing if the only copy sits on one laptop. The widely used 3-2-1 backup rule, a phrase coined by photographer Peter Krogh in his book on digital asset management, calls for three copies of your data, on two different types of media, with one copy kept off-site. For a notes folder, that might mean the working copy on your computer, a second copy on an external drive or home server, and a third copy in an encrypted cloud backup.

Sync is helpful, but sync is a different thing from backup. A sync service faithfully copies deletions and corruption to every device within seconds. A true backup keeps older versions you can roll back to. Git works well here, since every commit is a snapshot that can be pushed to more than one remote. Schedule it to run automatically.

Layer Five: Publication

Some notes are meant to be shared: reading summaries, glossaries, or public essays. For these, decentralized storage adds a layer that no single host controls. IPFS identifies files by a content identifier derived from the data itself, so the same file has the same address wherever it is stored. Content on IPFS stays available only while at least one node keeps it pinned, which means you either run a node yourself or rely on a pinning service.

Arweave takes a different approach. Uploaders pay a one time fee that, according to its documentation, is intended to cover storage for 200 years at present costs, with the remainder held in an endowment for later years. That makes it attractive for notes you want to keep public indefinitely. Never upload anything private, since removal is designed to be impractical. Treat permanent storage as a printing press for finished public work, never as a backup for a personal journal. This is educational information and should not be read as financial advice.

A Yearly Restore Test for Your Notes

A durability plan is only proven when you test it. Once a year, pick a quiet afternoon and pretend your main note app is gone. Restore your notes from the off-site copy onto a different computer, open them in a basic text editor, and try to answer a few questions using only the files, such as where a favorite quote came from or how two ideas connect.

If any answer requires the original app, you have found a weak layer. Perhaps an important tag existed only in the app database, or a group of attachments never made it into the backup. Fix that gap and record what you changed. Over a few years, these small repairs add up to a truly portable notes library.

A Weekend Checklist

The following list condenses the framework into steps you can complete over a single weekend. All of them work with free software.

• Export everything from your current app into Markdown or the closest open format it offers.
• Rename files with a date stamp and short title so each note has a stable identity.
• Add front matter for tags, sources, and created dates.
• Convert app specific links into file name links and build one index note per major topic.
• Set up three copies on two kinds of media with one kept off-site, and confirm that older versions are retained.
• Choose a public folder for notes you are happy to publish, and keep it separate from private material.

Once these steps are done, the choice of the app becomes a matter of taste. You can try a new editor, return to an old one, or use two at once, because the notes belong to you.

Owning Your Records in an Age of Local AI

A plain text notes library has a benefit that few people expected a decade ago. Local AI models running on your own hardware can read, search, and summarize a folder of Markdown files directly, with no need to upload your private thinking to a remote service. A folder that is open, well named, and richly linked is close to an ideal input for a personal research assistant that answers to you alone.

There is also a broader point about ownership and freedom. When personal records live in open formats on storage you control, people decide who can read them, how long they last, and which tools touch them. No platform can raise a price, change a policy, or close an account and take your thinking with it. Durable notes are a small, practical piece of a future where knowledge tools serve many people instead of concentrating control in a few companies.

Keeping notes readable for decades comes down to a handful of deliberate choices: open formats, stable names, a simple folder layout, portable links, real backups, and a clear line between private notes and public, permanent work. Together they turn years of reading and reflection into an archive you truly own. Start with one layer this week, run your first restore test within the year, and your future self will inherit a library instead of a locked box.

What is Pandoc?

Pandoc is a universal document converter that allows you to convert files from one markup format to another. It supports numerous input and output formats, making it an essential tool for anyone working with documents in different formats. Some of the key features of Pandoc include:

• Multiple Input Formats: Pandoc can read Markdown, HTML, LaTeX, reStructuredText, and many more.
• Multiple Output Formats: It can convert documents into formats such as HTML, PDF, DOCX, ODT, EPUB, and more.
• Customization: Offers extensive customization options, including templates, filters, and scripting to fine-tune the output.

Using Pandoc for Markdown Files

Markdown is a lightweight markup language with plain text formatting syntax. Pandoc excels in converting Markdown files to various other formats while preserving the document structure and styling.

Common Use Cases for Pandoc with Markdown

1. Converting Markdown to HTML: You can convert a Markdown file to HTML for web publishing.

   pandoc input.md -o output.html

2. Converting Markdown to PDF: Generate a PDF from a Markdown file, often using LaTeX as an intermediate format.

   pandoc input.md -o output.pdf

3. Converting Markdown to DOCX: Create a Word document from a Markdown file.

   pandoc input.md -o output.docx

4. Converting Markdown to EPUB: Convert a Markdown file to an EPUB eBook.

   pandoc input.md -o output.epub

Advanced Features

• Templates: Use custom templates to control the appearance of the output document.
• Filters: Apply filters to manipulate the document structure and content programmatically.
• Bibliographies: Manage citations and bibliographies in scholarly documents.

Installation and Basic Commands

Installation

You can install Pandoc on various operating systems:

• Windows: Download the installer from the Pandoc website.
• macOS: Use Homebrew:

  brew install pandoc

• Linux: Install via package managers like apt:

  sudo apt-get install pandoc

Basic Commands

• Convert Markdown to HTML:

  pandoc input.md -o output.html

• Convert Markdown to PDF:

  pandoc input.md -o output.pdf

• Convert Markdown to DOCX:

  pandoc input.md -o output.docx

Conclusion

Pandoc is an indispensable tool for anyone dealing with Markdown files and other text formats. Its ability to convert documents across a wide range of formats, combined with its customization options, makes it ideal for creating consistent, well-formatted documents for various purposes. Whether you need to publish a blog post, create a PDF report, or prepare an eBook, Pandoc provides the flexibility and power to handle your document conversion needs efficiently.