Add/Change Obsidian Sync plans

[shefakhoda]

Use case or problem

For people with large, frequently edited files, our version history fills up all our storage space. This makes Sync stop syncing.

(Please note that the purge function does not currently clear the version history of large note files. Also, buying Sync Plus only makes the problem worse, as it extends our version history to a year!)

Proposed solution

Allow a mid-tier Sync subscription, which expands our storage but does not extend our version history.

For example, we could pay $6/month for a 5 GB plan (that maybe allows for 2 vaults), but still has only 1 month of version history. This could be an entirely separate tier, or an expansion option within Sync Standard.

Current workaround

The official workaround is to delete and recreate your vault periodically, as a hard reset on your version history.

I imagine it would also work to buy the 100 GB Sync plan.

Related feature requests (other solutions)

Enable the purge process to also remove old versions of notes and other files

Use case or problem Obsidian Sync’s Purge process currently only purges out old attachments. When dealing with large .json or .markdown files - such as the case for Excalidraw - the purge process does not fulfill the expected goal of removing items from the remote vault to make space. Proposed solution Have Purge also purge the oldest versions of notes and possibly plugin settings as well. For how far back, maybe half the duration of the “plan” version history allowance. So 2 weeks for Standar…

Option to disable version history for large markdown files

Handwritten note plugins such as Excalidraw typically produce large markdown (1-10MB) files. For Sync users, Obsidian keeps a version history of those files, filling up the remote vault storage almost instantly, making the Sync feature unusable for handwritten note-takers. Adding an option to disable version history for large markdown files would solve this problem and save space on the server side.

Determine Sync's storage limits by size of local vaults, not by consumed server space

Use case or problem I want to: choose the right subscription plan for Sync and/or prune an existing vault when the limits of a plan are reached. I find it difficult to: understand how the size of a remote vault can be much larger than the size of the local vault identify what to prune, eg delete a complete remote vault or delete a local file or delete a remote file or … identify where to prune, ie locally or remote understand the timing of the pruning process Proposed solution Determine th…

A comment with a longer list of related threads

Enable the purge process to also remove old versions of notes and other files

This is a common issue that has been raised many times, by many users, over the years! Is this something you plan to fix? Or do affected users need to resign ourselves to a biweekly Vault delete, or else find a different cloud service?