Folder sync — local folder ↔ Wiki, both ways
Link a local folder to a project in the desktop app and .md files and wiki pages stay in sync both ways.
Who this helps
- An Obsidian folder — link the existing folder as it is and two-way sync starts
- A meeting-notes folder in iCloud Drive — notes written on mobile or Mac land in the Tabple Wiki automatically
- A shared Dropbox folder — an .md a teammate drops in shows up as a wiki page right away
- Local backup — wiki content is always kept on disk as .md files, so there is no vendor lock-in
If you already keep .md notes in a cloud folder such as iCloud Drive, Dropbox, or Google Drive, folder sync connects that whole folder to your Tabple Wiki. Obsidian users can point it at their existing folder as it is. Create a file in the folder and a page appears in the Wiki; edit the body in the Wiki and it is written back to the .md file. Whichever side you work on, both stay in the same state.
Getting started (3 steps)
Install the desktop app
Folder sync is a desktop-only feature. It does not run on web or mobile, so install the macOS or Windows desktop app first.
Open the project you want to map
Go to the project you want to map the folder to. One folder maps to exactly one project, so creating a fresh empty project for it is also a good approach.
Project settings → Folder sync section
Click the ⚙ Project settings icon at the top right of the project sidebar, then click Link folder in the Folder sync section at the bottom of the page and choose a folder.
Four scenarios, detected for you
- Both empty — sync starts right away. Create an .md in the folder or a page in the Wiki and it appears on the other side automatically.
- Only the folder has .md files — the .md files are imported into the Wiki. Folders deeper than 4 levels are flagged in advance and left out of sync.
- Only the Wiki has pages — downloading the wiki into the folder is recommended (two-way sync can then start immediately). You can also choose to use the local folder only and ignore the existing Wiki.
- Both sides have content — you have to pick the source of truth. Either the local folder wins (its .md files go to the Wiki) or the Wiki wins (wiki content is written to .md, and existing .md files are backed up automatically as .conflict-<date>.md).
When you choose a folder, Tabple inspects the state of both the folder and the Wiki and tells you which start is safe. To prevent data loss, neither side is overwritten without your confirmation.
Day to day — what is automatic
Frontmatter metadata is preserved
Mapping information is written automatically on the first lines of each .md file. You never need to edit it, but it does have to stay (without it the file is treated as a new page).
---
tabple_id: 1234
title: 회의록 2026-05-08
icon: 📄
---
# 회의록 본문…- Create an .md file in Finder or Explorer and it usually appears as a wiki page within 1–2 seconds
- Edit the body in the Wiki and the same .md file is updated within 5 seconds
- A folder maps to a parent page, and subfolders map to a tree of child pages
- [[Page name]] wiki links become PageMention chips automatically
- Text in T-123 form becomes a TaskMention chip automatically
- Checklists (- [ ]), tables, code blocks, and image links are round-trip safe (nothing is lost going from local folder to Wiki and back)
When a conflict happens
When the conflict dialog opens by itself
If the same page was edited in the local folder and in the Wiki and neither side can be merged automatically, the conflict dialog opens on its own and asks you to choose.
Push local to the Wiki
Takes what you wrote in the .md file as the source of truth. Changes made on the wiki side are dropped.
Pull the Wiki to local
Applies the wiki content to the .md file. Local changes are dropped.
Later
Closes the dialog and keeps both sides until the next conflict cycle. The dialog returns the next time sync is triggered.
Cautions & limits
- The Tabple wiki tree only goes 4 levels deep — files in folders 5 levels or deeper are left out of sync (the dialog warns you first). Flattening example: meetings/2026/05/08.md → meetings/2026-05-08.md
- Deleting an .md file from the local folder does not delete the wiki page. It is only recorded in the local trash (.tabple/trash.json). To remove a wiki page for good, delete it in the Wiki UI.
- Rich blocks such as callouts, toggles, columns, and Mermaid are preserved in .md as HTML comment metadata — less readable, but the original block is restored when pushed back to the Wiki.
- Downloading image attachments (images uploaded to R2) into the local folder is planned — for now the absolute URL goes into the .md as it is.
- One folder maps to one project only. To move it to another project, use Settings → Unlink and link it again.
Multiple devices + FAQ
The same folder on several desktops
Each device has its own instance id and ignores only its own push as an echo. Changes from other devices are pulled normally.
Working offline
You can keep editing .md files with no internet. Pushes queue up and drain automatically once you are back online. Changes made in the Wiki while you were offline are caught up through changes-since.
Q. How do I move the folder?
Go to Project settings → the Folder sync section → change folder, and pick a new location for the same mapping.
Q. What if .tabple/manifest.json is damaged?
It repairs itself. The mapping is rebuilt from the tabple_id in each .md file's frontmatter, so the same page is never duplicated in the Wiki.
Q. How do I flatten folders deeper than 4 levels?
Use the advance warning list in the folder link dialog as your guide and reorganize the folders yourself. Reduce the depth, link again, and they are included in sync automatically.