Syncthing Ignore Rules for an Obsidian Vault on Boox: Plugins That Should Never Reach the Tablet
Caleb Whitmore
September 21, 2026
Mirroring a full Obsidian vault onto a Boox feels like the clean solution until the tablet spends half its battery thrashing plugin folders, workspace JSON, and theme caches you will never open with a stylus. Syncthing ignore rules are how you keep markdown and attachments on the e-ink device while leaving the desktop’s plugin circus at home.
This is not a generic Syncthing tutorial. It is the specific failure mode of “Obsidian on Android e-ink plus Syncthing plus a fat community-plugin list,” and the ignore patterns that stop the tablet from becoming a second, slower, angrier copy of your PC vault.
What actually hurts on a Boox
E-ink Android is storage-tolerant and I/O-sensitive. Thousands of tiny files in .obsidian/plugins wake the radio, delay the sync of the note you care about, and invite conflict copies on JSON that Obsidian rewrites constantly. Themes, icons, and plugin databases change when the desktop vault is merely open—not when you edited a thought.
The tablet usually needs:
- Your
.mdnotes (or a subset of folders) - Attachments you actually open on device
- Maybe a minimal
.obsidianif you run Obsidian Android and want a few core settings
The tablet usually does not need:
- Community plugin binaries and data
- Hot workspace files that churn every session
- Large archival folders you only search on the desktop
- Node-like helper folders some plugins create

Architecture choice before patterns
Decide which Obsidian lives on the Boox.
A. Full Obsidian Android on the tablet. You want some .obsidian config. Ignore plugin folders aggressively, accept that you will enable a tiny plugin set on-device separately, and never expect plugin state to sync both ways.
B. Plain markdown editor / other reader on the tablet. Ignore almost all of .obsidian. Sync notes and attachments only. This is the calmer path for many Boox owners.
C. Selective folder sync. Only Daily/, Inbox/, and Projects/active/ sync to the device. Archives stay desktop-only. Ignore rules become simpler because the share itself is smaller.
If you try to run three dozen desktop plugins and a perfect mirror on e-ink, Syncthing is not the villain. Your symmetry fantasy is.

Ignore rules that pull their weight
Syncthing’s #include and ignore file live per folder. On the Boox side (or on both sides if you want symmetry of ignores—read the docs carefully about which device owns the ignore file), patterns like these are the usual starting point for Obsidian vaults:
.obsidian/plugins— community plugins should not cross.obsidian/themes— optional; themes are bulky and desktop-specific.obsidian/workspace*— layout thrash.obsidian/graph.json— often rewritten.obsidian/cacheor similar cache paths if present in your version.trash— unless you like syncing deletes as clutter- OS junk:
.DS_Store,Thumbs.db,*.tmp
Keep core settings you do want—app.json, appearance.json carefully—only if both sides run Obsidian and you understand they may still conflict. Many people ignore the entire .obsidian tree on the tablet share and recreate a minimal on-device config once.
Also ignore heavy plugin artifacts by name when they live outside .obsidian: some tools write databases into the vault root. If you see a recurring conflict on a .json or .db you never opened on the Boox, add it to ignores the same day.
Directionality: one-way ideas versus two-way notes
Syncthing is mostly two-way. That is fine for notes. It is dangerous for plugin folders if you ever un-ignore them “just to copy once.” Prefer:
- Two-way for markdown and images you edit on both sides
- Desktop-only for plugins (ignore on tablet receive)
- Occasional manual copy of a single CSS snippet if you truly need it
If you need a true one-way send of a plugin build, use a USB cable once. Do not open a permanent sync hole for convenience.
Folder subsets beat clever ignores
The strongest move is often not a longer ignore list. Share a dedicated “mobile” vault folder that contains only what the Boox should see, and let desktop Obsidian use the full vault. You can still link or periodically copy. Or use Syncthing on a parent folder with ignores that drop Archive/, Attachments/raw-video/, and Excalidraw/ if those are desktop toys.
Boox storage is not the scarce resource as often as Boox patience. Fewer files mean faster first sync after a flight mode weekend and fewer surprises when you unlock the device in a waiting room.
Conflict files and ignores interact
Ignoring plugin paths reduces conflicts on those paths. It does not fix daily-note conflicts. You still need capture habits for hot markdown files. What ignores buy you is quieter sync so the daily note actually arrives before you start writing.
If conflict files already exist under .obsidian, delete them on the desktop after picking a winner, then add ignores so they stop regenerating. Leaving conflict JSON around confuses future you and sometimes confuses Obsidian.
Battery, sleep, and Syncthing on Android
Android battery optimizations kill Syncthing at the worst time. Exempt the app. Expect e-ink deep sleep to pause sync anyway. Ritual: open Syncthing, wait for idle, then open the note. Ignores make that wait shorter; they do not remove the ritual.
Run Syncthing as a limited share, not as a background excuse to keep radios hot all day. Many Boox users sync on Wi‑Fi at home and leave the tablet offline on the train with a clean tree—possible only if the tree is small.
A practical setup sequence
- On desktop, clean obvious junk and decide folder subsets.
- Create the Syncthing share; add ignores for plugins/themes/workspace before the Boox ever connects.
- Connect the Boox; let the first sync finish on power and Wi‑Fi.
- If using Obsidian Android, configure a minimal plugin set locally; do not copy desktop plugins.
- Write a test note on each side; confirm round trip.
- Search the tablet for community plugin folder paths—confirm they are absent.
- After a week, review Syncthing’s recent conflicts; extend ignores for any thrashing path.
Document your ignore file in a note that lives in a synced folder. Future-you will thank present-you when a plugin update invents a new noisy path.
When you should not use Syncthing for this
If both sides must run identical Obsidian plugin configurations, Obsidian Sync (or a single device) is less painful than Syncthing gymnastics. Syncthing wins when the tablet is a markdown satellite, not a clone of your desktop IDE-for-notes.
If the Boox is mostly for reading exports from Supernote or Kindle, skip vault sync entirely. Different problem, different pipe.
Decision guide
Ignore community plugins, themes, and workspace churn on the Boox share by default. Sync notes and needed attachments. Prefer a smaller folder set over a cleverer pattern list.
Treat on-device Obsidian plugins as a separate install, not as a synced artifact.
The point of an e-ink vault is calm capture and reading. Syncthing ignore rules are how you stop desktop power-user Obsidian from turning that calm into a continuous sync storm. Plugins that should never reach the tablet are exactly the ones that make the desktop wonderful—and the Boox miserable—when mirrored blindly.
Start stricter than you think you need. You can always widen the share. Widening is easy. Cleaning ten thousand tiny plugin files off a slow Android e-ink filesystem after a weekend of “just sync everything” is the chore you are trying not to earn.
When a new desktop plugin starts writing a database into the vault root, add that path to ignores the same evening—before the Boox downloads a conflict-prone binary blob you will never open with a stylus. Review the Syncthing ignoring documentation when patterns seem not to apply; a leading slash and folder anchoring change behavior more often than people expect. Keep the mental model simple: the tablet is a satellite for prose, not a clone of your desktop Obsidian power-user profile.
Example ignore block you can adapt
Exact syntax varies with your Syncthing version and whether the ignore file sits at the vault root. The intent looks like this: ignore plugin and theme trees, ignore workspace thrash, ignore OS junk, and optionally ignore large archive paths you never open on the Boox. Do not ignore your Inbox or Daily folders unless you have another capture path. Test with a single throwaway note after each change so you know whether the tablet still receives prose.
If a pattern seems ignored on one device and not the other, confirm which side’s ignore file is authoritative for that folder and whether you accidentally created a second Syncthing share pointed at a nested path. Nested shares with different ignores are a classic way to sync plugins “anyway” through the back door.
Finally, resist the urge to sync Obsidian’s entire configuration because a Reddit comment said it was fine on phones. Phones reconnect often and refresh quickly. Boox devices sleep harder, sync slower, and punish tiny-file storms. Configure ignores for the device you are holding—not for the device you wish it were.
That mismatch is how people accidentally reintroduce the plugin circus they spent an evening removing.
Close the hole; keep the prose.