How to Sync Markdown Notes with iCloud Without Lock-in (2026)

To sync Markdown notes with iCloud, keep your .md files in an iCloud Drive folder and use an editor that opens that folder. You need an Apple Account, iCloud Drive enabled on each device, and enough iCloud storage. The files remain portable; the sync service transfers them to iCloud.

Set up a folder safely

1. Back up existing notes before moving them. Keep that backup outside the folder you are about to sync.
2. In Finder, open iCloud Drive and create a Notes folder.
3. Copy a few test .md files into it. In current Apple Notes, you can export individual notes using File > Export as > Markdown. Check any attachments and formatting after export.
4. Open the folder in your editor. In Obsidian, use Open folder as vault. Other editors may call this a location or working folder.
5. Wait for the files to finish uploading before opening them on another device signed into the same Apple Account.

Apple documents iCloud Drive setup and Markdown export from Notes. Menu names can differ between macOS versions.

Syncing Stik notes

Stik 0.8.0 saves notes in ~/Documents/Stik/. Its release README documents enabling iCloud Drive for the Documents folder as a sync option. This includes other files in Documents, so review Apple's setup instructions and your available storage before enabling it.

You do not need to move Stik notes into a separate Notes folder or create symbolic links. Once Documents is syncing, check the Stik folder from another Mac. Stik itself is a Mac app; on an iPhone or iPad you need a compatible editor to open the synced Markdown files.

Stik's semantic search runs locally. Choosing iCloud or Git sync is a separate decision that sends your files to the provider you select. Full disclosure: I build Stik. Its code and release history are available on GitHub.

Verify before moving your whole library

Use disposable test notes for these checks:

• Create a note on one Mac and confirm it appears on the other.
• Edit a line, wait for sync, and confirm both devices show the same text.
• Check that images and linked files open on both devices.
• Disconnect one device, edit a test note on both, reconnect, and inspect the result. Do not assume the service or editor will preserve both versions or merge text the way you expect.

iCloud is a sync service, not a substitute for a separate backup. Deletions and mistakes can propagate too. Keep a recoverable copy before testing conflicts or changing sync settings.

Common problems

Files are not available offline. Storage optimization can leave files in iCloud without a local copy. Download the folder in Finder before relying on offline editing, and check its availability on every Mac.

Edits do not appear immediately. Sync timing depends on connectivity, storage, device state, and the editor. Check iCloud status and finish syncing before editing the same file elsewhere.

Conflicting edits. Conflict presentation varies. Compare the files and any versions the app or service exposes, recover from backup if necessary, and avoid simultaneous edits to the same note until you understand the behavior.

Two sync services manage one folder. Pick one method for a given folder. Combining iCloud with another active sync engine can make conflict behavior harder to predict.

Frequently asked questions

Do I need an account?

Yes. iCloud Drive requires an Apple Account. Stik does not require its own account for local note-taking.

Does iCloud merge Markdown text automatically?

Do not rely on automatic text merging or a particular conflict-copy filename. Test your editor and devices with disposable files, and keep backups.

Can I stop using iCloud later?

Yes. Download and back up the complete folder first, then follow Apple's instructions for disabling sync. Confirm that the local files and attachments are present before deleting cloud copies.

Which setup should I choose?

Use the editor's documented folder and sync support. For Stik 0.8.0, that means the Documents-folder workflow above. For a general Markdown folder, Obsidian and other folder-based editors offer their own documented options. See plain Markdown files and portability for the storage trade-offs.