Last updated: 22 Apr 26 02:17:12 (UTC)

Portable.exe on Onedrive

Technically, you can do this, but from a technical and data-safety standpoint, it is highly discouraged. When you use Joplin Portable, it stores its entire database (database.sqlite) and all your resources (images, PDFs) in a folder called JoplinProfile right next to the .exe. Putting this folder in OneDrive might seem like a clever way to sync, but it creates a specific set of risks that “regular” sync avoids. Here are the primary arguments against doing it this way:

1. Database Corruption (The “Race Condition”)

Joplin uses a SQLite database. This is a single, complex file that is constantly being written to while the app is open.

  • The Problem: OneDrive is designed to sync files as soon as they change. If OneDrive tries to upload/lock the database file while Joplin is still writing a new note to it, you can end up with a locked database or, worse, a corrupted file that won’t open at all.
  • The Regular Sync Advantage: Joplin’s built-in OneDrive sync doesn’t move the database. Instead, it “exports” individual notes as small, separate text files to the cloud. If one sync fails, only one note is affected—not your entire library.

2. Conflict “Hell”

If you accidentally leave Joplin open on your Desktop and then open the portable version on your Laptop, both instances will try to write to the same database.sqlite file.

  • The Result: OneDrive won’t know how to merge the two versions of the database. It will likely create a “Conflict File” (e.g., database-ComputerName-Conflict.sqlite).
  • The Headache: Joplin will only see the original file, meaning the notes you wrote on the second computer will appear to “disappear” until you manually rename and swap the database files.

3. Performance Lag

Every time you type a character, Joplin updates the database. OneDrive will see these constant changes and try to re-upload the entire database file (which could be hundreds of MBs) over and over. This wastes bandwidth and can cause your computer to lag or run hot as it constantly calculates file hashes.

Summary Table: Portable in OneDrive vs. Built-in Sync

Feature Portable Folder in OneDrive Built-in OneDrive Sync
Data Safety High Risk of total database loss. Low Risk; individual files are synced.
Conflicts Creates duplicate database files. Merges notes intelligently.
Speed Slow (uploads whole DB file). Fast (uploads only changed notes).
Offline Use Requires full sync before opening. Works offline; syncs when ready.

If you still want to do it…

If you are determined to try this, follow these “Golden Rules” to minimize the risk:

  1. Strict “One-at-a-time” Rule: Never, ever have Joplin open on two computers at the same time.
  2. Wait for the Green Check: Before opening Joplin, wait for the OneDrive icon in your taskbar to show the green “Synced” checkmark. Before shutting down your PC, wait for it to finish uploading.
  3. Back up your JEX: Frequently export your notes to a .jex file as a “lifeboat” in case the SQLite database gets corrupted. My Peer Advice: Use the built-in sync. It was designed specifically to handle the “quirks” of cloud storage that a standard database file just wasn’t built for.