Back to guides
GuideChecked November 20265 min read

Your files stay on disk

Local Markdown files stay on disk. There is no Ferrite account. You sync the folder yourself.

Ferrite 0.3.1 does not keep a copy of your notes. There is no Ferrite account and no Ferrite server. You open a folder, and the files in it are ordinary Markdown. The FAQ says your data does not leave the machine.

Open a folder

File → Open, or the folder command you already use, points Ferrite at a directory on disk. Everything you save is written there as .md, next to whatever else you put in that folder. You can open the same files in another editor. Ferrite is not a library you have to export from.

Local Markdown notes is the page about using that folder as a note system, including wikilinks. This page is about where the bytes live.

Sync is a tool you run

Ferrite has no built-in sync. Real-time collaboration is not in this version either. Both are v0.5.0 on the roadmap.

Until then, use a folder sync you already trust. Syncthing, Dropbox, OneDrive, and iCloud are the usual ones. They are not features inside Ferrite. Ferrite does not sign you in, and it does not see their accounts. You aim them at the folder. Ferrite keeps editing the files.

If two computers write the same note at once, the conflict is the sync tool's conflict. Ferrite does not merge it for you.

Moving computers

Copy the folder, or let the sync tool copy it. Install Ferrite on the other machine from the download page, and open that folder. Settings may differ per machine. The notes do not. They are the files.

There is no graph and no plugin state to migrate, because the current version has neither. If you are leaving an app that does have those, read Ferrite vs Obsidian so the gap is explicit.

Wikilinks inside the folder keep working as long as the relative files come along. See wikilinks. The broader editor is on features.

Questions