Markdown notes across devices: a practical Vault workflow
Capture reusable Markdown notes, organize files and check offline changes before moving from your phone to another device.
A useful note is quick to write now and still makes sense next month. Markdown gives plain text a little structure, such as headings, lists and links. When your notes sync between devices, you also need to know whether your latest edit has actually reached the next device.
Vault in Mono by Reunified gives you folders, file uploads and a Markdown editor. This guide shows how to organize a small set of notes and check that a change has arrived on your other device, without assuming that every file in the list is already stored on it.
1. Start with three folders
Create an inbox for quick notes, a projects folder for active work and a reference folder for things you’ll reuse. The names are only suggestions. Keep the structure flat at first: deep folder trees make quick capture on a phone harder.
Give each note a clear name, such as 2026-10-08-workshop-plan.md. Put the project or topic in the name so you can tell similar notes apart in a list. Add a date to notes about a specific day, not to every reference note.
In Vault, tap + to create a folder or a new Markdown file. Upload is a separate option for files you already have. Check that you’re in the right folder before you create several notes.
2. Capture a note with enough context
Try this small template in a new Markdown file:
# Workshop plan
Purpose: help beginners complete one small project.
## Decisions
- Use a 30-minute demonstration.
- Share the materials before the session.
## Next action
- Confirm the room with the organizer.
## Sources
- Add the original reference link here.Keep decisions apart from next actions. When you save an idea from somewhere else, add the source link and keep quotes separate from your own thoughts. That way the note still makes sense after you’ve forgotten the conversation behind it.
The CommonMark specification describes common Markdown syntax. Apps can support different extras, so test a small sample before you rely on complex tables, embedded HTML or unusual formatting in another app.
3. Finish the edit and verify the handoff
Vault saves your edits on its own and then uploads them. Saving on your phone and finishing the upload are two separate steps.
Open the file’s details and check its status: “Up to date” means the upload is done, while “Waiting to upload” or “Uploading” means it isn’t yet. Then open the note on your second device and check the last sentence. Use a distinctive, harmless line such as “Room confirmation is still pending” so you can recognize the version you just wrote.
Try this once with a test note before you rely on it while traveling. Seeing a file in the list doesn’t mean its contents are already on that device.
4. Prepare for offline work
Open the notes you’ll need while you’re still online. Files you’ve opened before stay on the device, and notes you create or edit offline wait and upload when you reconnect. A file that was never downloaded to the device can’t be opened until you’re back online.
After you reconnect, look for files that are still waiting or that failed. Fix the problem shown and use Retry upload where it’s offered. Don’t delete a waiting note just to clear a warning, unless you really want to throw away the copy on that device.
Avoid editing the same note on two devices while both are offline. Finish one change and check that it arrived before you continue elsewhere. If two versions differ, copy the useful text from both before you decide which one to keep.
5. Keep the file useful outside its original context
Stick to headings, plain lists and descriptive links. An image or attachment is often a separate file, so copying only the Markdown text can leave it behind. Test one typical note in the other app before you move a larger collection.
Keep a separate copy of important notes, using the file or copy options on your device. Sync puts the same files on all your devices; a backup lets you get them back if something goes wrong. Those are different jobs, so don’t count on sync alone as your backup.
6. Review the inbox and the privacy boundary
Once a week, move useful inbox notes into projects or reference, delete duplicates and update the next action on active work. If you want to keep finished project material, put it in a clearly named archive folder.
A note in Vault doesn’t automatically become an AI memory. To see what is end-to-end encrypted and what gets sent to a model, read AI privacy and encrypted sync before you decide what to store.
Explore Vault and join the Mono waitlist. Start with five useful notes and one checked handoff before you bring in your whole archive.
