Your notes should be files you can keep

A note is more useful when it outlives the screen where you wrote it. You should be able to find it, read it, move it, and keep it without asking the original app for permission.

That does not make every file-based notes app better. It gives you a simpler test: if the app disappeared tomorrow, would the important part of your note still make sense?

The short answer

Your notes should be ordinary, readable files when you want long-term access and freedom to choose your tools.

A file gives you practical control. You can copy it, move it, back it up, open it in another editor, or process it with a tool you choose. Markdown is useful because its core remains readable plain text even without a special renderer. That is the format's design goal, not a promise that every app-specific extension will work everywhere. CommonMark describes that boundary clearly.

Files are not magic. They are not automatically private, encrypted, backed up, synced, or safe from conflicts. Ownership gives you more agency and more responsibility.

Question	File-first note	Export-based note
Where is the everyday primary copy?	In a normal file you can see	Inside the app or service
Can you read it without the app?	Usually, at least the core text	After a supported export
Can you choose another editor?	Often, if the format is supported	After export or migration
Does it include automatic backup or sync?	Not necessarily	Depends on the service
Can rich features move perfectly?	Not always	Not always

Neither model is automatically dishonest. The useful question is what you can do when you want to leave, change tools, or keep the work for a long time.

A file is different from an export

Export is a doorway. A file-first system starts on the other side of that doorway.

In an export-based app, the primary note lives inside the app's own storage model. When you want to leave, you ask the app to produce a PDF, Markdown file, archive, or another supported format.

That can be a good experience. Apple's current Notes guide, for example, documents Markdown import and per-note Markdown export on supported macOS versions. That is real portability and should not be dismissed. Apple’s import and export instructions.

A file-first app makes a different choice: the normal working copy is already a file. Export is not the moment when the note becomes yours to move. It was movable from the start.

The difference matters most when:

you want to change editors;
you want to keep your own backup;
you want to search with ordinary file tools;
you want to version selected work;
you want to give a chosen tool access to a folder;
the original app changes, becomes unavailable, or no longer fits.

The Ink and Switch local-first paper calls this practical agency over data. It also makes the tradeoff plain: when you control the files, you take on more responsibility for backup, protection, and organization. Read the local-first paper.

Use this five-part test

Do not stop at “uses Markdown.” Check what that means in practice.

1. Is the primary copy a normal file?

Look for an actual path and filename.

If the app says it uses plain text internally but the notes only exist inside an opaque database, that may still be portable through export. It is not the same as a folder of ordinary files.

2. Is the important part readable without the app?

Open one note in a plain-text editor.

You should be able to understand the title, paragraphs, headings, lists, and links that matter. The note does not need to look beautiful. It needs to remain intelligible.

3. Does the whole note move?

Text is only part of some notes.

Check where images, audio, PDFs, canvases, databases, and sidecar metadata live. A Markdown file may remain readable while losing the rich view, embedded media, or plugin behavior that made it useful in the original app.

4. Can you use tools you choose?

A normal file can participate in ordinary workflows.

You might copy the folder to another drive, include selected notes in a version-control system, search it with local tools, or open it with another editor. You do not have to do any of those things. The value is that the app does not need to be the only path.

5. Are the remaining dependencies clear?

File-first does not mean app-free.

The original app may still provide the index, backlinks, search, collaboration, conflict handling, attachments, AI, or sync. A good product should explain which part is the readable source and which part is an optional layer around it.

A concrete Cue workflow

Cue Notes stores saved notes as Markdown in a visible folder. The default vault is under Documents/Cue, and you can choose another location in Settings. The vault settings show the path and a Reveal in Finder action.

Try the ownership test with one low-stakes note:

Open Cue Notes and write or dictate a short project update.
Give it a clear title and remove anything you do not want to keep.
In Cue Settings, find the vault location and reveal the folder in Finder.
Open the matching .md file in a plain-text editor.
Confirm that the important text still makes sense without Cue.
Copy that one file to a temporary folder, then open the copy.

The point is not to leave Cue. The point is to prove that staying is a choice.

Cue's live Notes page describes the same product boundary: local Markdown, a folder the user owns, and files that remain ordinary outside the app. Read about Cue’s files and agent connections.

If you later connect an agent, treat that as a separate permission decision. A readable folder does not mean every tool should receive it automatically. Cue's MCP page describes a connection the user chooses.

The tradeoffs are real

File ownership solves one class of problem. It does not solve every notes problem.

Files need care

A local file can still be lost.

Use a backup system that fits the importance of the work. If the notes are sensitive, decide how the disk and backups are protected. If several tools edit the same file, understand how they handle concurrent changes.

Rich features can create soft lock-in

The main text may be portable while the experience is not.

Plugin blocks, queries, canvases, proprietary links, custom frontmatter, and separate attachment stores can make a note less useful elsewhere. Prefer a readable core and treat richer layers as optional.

Collaboration may be easier elsewhere

Real-time shared documents are excellent for work that many people edit together.

A folder of Markdown files can support collaboration, but conflict handling and permissions may require more setup. Choose the model that fits the job.

Local files do not make every action local

A note can live on your Mac while a chosen AI model processes selected text in the cloud.

Storage, sync, processing, and agent access are different boundaries. Check each one. If you want the current Cue product surface, start with Cue Notes. If you only need system-wide capture, the Mac dictation guide is the better starting point.

When files are not the right priority

Choose a collaboration-first or database-first notes tool when the shared live experience matters more than independent files.

That may be true when:

many people edit the same page at once;
permissions must be managed centrally;
the note depends on relational tables or embedded applications;
your team has a required system of record;
you do not want to manage storage and backups.

The honest goal is not “everything must be Markdown.” It is knowing what you can keep, what you can move, and what still depends on the app.

Frequently asked questions

Does Markdown mean I own my notes?

Not by itself.

Check whether the everyday primary copy is a normal file, whether you can access the folder, and whether important content remains readable without the app. Also check attachments and app-specific extensions.

Are local Markdown files automatically private?

No.

A local file may still be included in cloud backup, sent to a model, shared with another tool, or exposed by weak device security. Storage location is only one part of the data boundary.

Is export the same as file-first storage?

No, but export can still provide useful portability.

In a file-first system, the normal working copy is already an external file. In an export-based system, the app creates that file when you ask. Judge the quality, completeness, and repeatability of the export.

Can every Markdown app open the same note?

Most can read the core plain text. They may render extensions, wiki links, frontmatter, callouts, attachments, or plugin blocks differently.

Test one real note instead of trusting a format label.

Do I need Git for file-based notes?

No.

Version control is optional. A simple, tested backup is more important than adding a complex system you will not maintain.

Does file-first mean local-only?

No.

The primary note can remain a local file while optional services provide sync, collaboration, transcription, or AI processing. What matters is whether those connections are visible and chosen.

For the next step, read why Markdown is useful memory for AI work and how local notes and cloud models can work together.

Sources

Sources checked October 4, 2026.

Try the test

Try Cue Notes with one note you do not mind experimenting with. Save it, reveal the folder, open the Markdown outside Cue, and make sure the important part is still yours to read.