Feature Request: [Obsidian Sync] Native File and Folder Sharing for Obsidian and Non-Obsidian Users

Feature requests
1

Status: New
Priority: High (Core Functionality)

Problem

Obsidian Sync provides excellent end-to-end encrypted (E2EE) synchronization across devices, but lacks native sharing of individual files or folders with collaborators—whether Obsidian users or not. Users must resort to insecure third-party services like Google Drive or Dropbox, exposing E2EE data to non-zero-knowledge providers. This defeats Obsidian’s privacy promise, especially since Sync is paid ($8/month for Plus), making selective sharing a core expected feature [web:19][conversation_history:25].

Use Case

I use Obsidian Sync as my primary E2EE Drive replacement: Markdown files, attachments, and folders for projects, knowledge bases, and documents. Sharing is essential for:

  • Obsidian users: Add shared folders to their vault for seamless collaboration (view/edit/merge).
  • Non-users: Browser-based view or lightweight edit mode (simple Markdown tweaks without full Obsidian).
    Examples: Share project briefs with clients (read-only), co-edit specs with team members, or let family view trip plans—all without compromising E2EE [web:3][conversation_history:25].

Proposed Solution

Add Sync Sharing UI in Settings > Sync:

  • Select file/folder → Generate share link/ID with permissions (View, Edit, Comment).
  • Obsidian users: Paste link/ID into vault → auto-syncs as remote folder (selective merge/conflict resolution).
  • Non-users: Link opens private web viewer (like Publish, but E2EE) with basic Markdown editor.
  • E2EE preserved: Client-side decrypt via recipient’s vault password or temp key.
  • Controls: Expire links, revoke access, version history per share.
Feature Obsidian User Non-User
Access Vault integration Browser viewer
Permissions View/Edit/Comment View/Edit (light)
E2EE Native Client-side decrypt
Limits Sync quota Read-only bandwidth

Existing Workarounds (Insufficient)

  • Cloud alternatives: Breaks E2EE (no sharing via OneDrive without exposing keys) [conversation_history:31].
  • Plugins like “File Share”: Shares single files via links (good start!), but no folders, no collab, no E2EE integration [web:17].
  • Remotely Save/Syncthing: Peer-only, rate-limited, no browser access [conversation_history:31].
    These force vault duplication or insecure exports, unsuitable for paid Sync users [web:1].

Benefits

  • Privacy-first collab: Retains Obsidian’s E2EE edge over Notion/OneNote.
  • Monetization: Upsell via share quotas (e.g., 5 GB free, more on Plus).
  • Adoption: Enables team/business use without vault proliferation.
    Existing requests echo this (view-only mode, selective shares) [web:1][web:6].

Please prioritize—Sync sharing is table stakes for a modern E2EE Drive! :rocket:

2

Update: Additional Details for Feature Request (Edit Locked After 5 Min)

Additional Focus: Bypassing Corporate IT Restrictions

Many companies prohibit software installations on work laptops (e.g., Business Analysts, Product Owners). With native Sync-Sharing via links, employees could:

  • Share entire Vaults/folders → Browser opens Core Obsidian Viewer (no installation needed!)
  • Basic editing: Markdown edits without Community Plugins, only Core Plugins (basic config, no Settings menu required)
  • Seamless workflow: Work in browser → Syncs back to private Obsidian → no duplication

Real Example: I want to take notes on my work laptop where Obsidian installation is blocked. With a Vault/folder share link, I can edit my notes directly in the browser—no copying files and manually merging changes back later.

1 Like
3

Additional Comment:
I also Believe this selective access sharing or link-sharing would be essential for medium to large enterprises, enabling companies to seriously consider Obsidian Sync as a Confluence or SharePoint replacement. Without this, corporate adoption remains limited despite Obsidian’s superior note-linking and folder organization.