Real-time collaboration in Obsidian with Peerdraft
Based on Nicole van der Hoeven's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Peerdraft enables true simultaneous editing of Obsidian notes by pairing an Obsidian plugin with a Peerdraft web app that mediates session setup.
Briefing
Real-time collaboration in Obsidian is finally getting a practical answer: Peerdraft adds live, simultaneous editing to Obsidian notes with low latency and minimal setup, using a peer-to-peer connection mediated by a web app. The core pitch is simple—stop bouncing ideas into Google Docs just to brainstorm together. Instead, collaborators can open the same Obsidian note, start a shared session, and type at the same time with changes appearing instantly.
Peerdraft works through two components: an Obsidian community plugin and a Peerdraft web app. In Obsidian, a user starts a “sharing session” from the command palette, which copies a session link to the clipboard. That link is sent to a collaborator, who joins via the web app; the actual document edits then travel peer-to-peer between the participants using WebRTC, with end-to-end encryption. The web app mainly acts as the rendezvous/middle layer that helps peers find each other and establish the connection.
Setup is straightforward but not entirely invisible. After installing the plugin, Obsidian may need a restart. The plugin then asks for a name, and users can connect an existing subscription or begin on a free tier. Peerdraft offers a “Forever Free” plan that allows 2.5 hours of use per month; the pro plan costs $30 per year and removes the time limit. During testing, the collaboration behaved like a true live editor: one person on Obsidian and another in the browser could both type, and the note updated quickly enough to support real brainstorming rather than delayed copy/paste workflows.
The experience also comes with clear tradeoffs. There are no read-only permissions—anyone with the link can edit. Collaboration is asymmetric: at least one participant must be using the browser, and the other must be using Obsidian; both can’t be in the browser, and “Obsidian-to-Obsidian” simultaneous editing isn’t available yet. Once the shared session ends, edits and session activity don’t persist on Peerdraft, and there’s no post-session record of who typed what. A particularly practical drawback surfaced during testing: there’s no notification when someone joins, so collaborators can effectively “lurk” without being obvious—unlike Google Docs, where presence is visible.
Peerdraft’s limitations also reflect its security posture. The service is closed source and not self-hostable, so confidential notes may not be a fit. The developer, Dominik Schlund, says the server’s role is limited to session setup and peer discovery; it doesn’t see the document content. He also notes that usage metadata like session duration is stored to support the free-tier gating.
Compared with alternatives, Peerdraft is positioned as the most seamless option for true simultaneous editing. Obsidian Sync is the official syncing/collaboration route, but it can require both parties to pay and still produced conflicts during shared typing tests. Etherpad Lite, while workable, was described as less real-time because it involves pushing note content out to a hosted editor and pulling it back.
Peerdraft isn’t perfect, but it targets the one weakness that pushes many writers back to Google Docs: editing the same note at the same time. If that’s the goal—fast, low-latency co-writing without a complicated workflow—Peerdraft is built to deliver it now, with future requests focused on better editing and Obsidian-to-Obsidian collaboration.
Cornell Notes
Peerdraft brings real-time, simultaneous editing to Obsidian notes by combining an Obsidian community plugin with a Peerdraft web app. A user starts a shared session in Obsidian, copies a link, and collaborators join via the web app; edits then sync peer-to-peer using WebRTC with end-to-end encryption. The free tier allows 2.5 hours per month, while Pro costs $30 per year for unlimited time. Collaboration is live but not permissioned (anyone can edit), and it’s asymmetric: one person must be in Obsidian while the other uses the browser. Session activity doesn’t persist after the session ends, and there’s no “someone joined” notification, so presence can be easy to miss.
How does Peerdraft establish real-time collaboration between an Obsidian user and a collaborator?
What are the practical limits of collaboration—who can edit, and where must each person be?
What happens when the shared session ends, and what evidence remains afterward?
Why might Peerdraft feel different from Google Docs during a live session?
How does Peerdraft compare with Obsidian Sync and Etherpad Lite for real-time co-editing?
What security and privacy constraints should users consider before sharing confidential notes?
Review Questions
- What technical mechanism does Peerdraft use to exchange edits, and what role does the Peerdraft web app play?
- List at least three limitations of Peerdraft collaboration (permissions, platform pairing, session persistence, notifications, or privacy).
- Compare the failure modes of Obsidian Sync and Etherpad Lite described in the transcript with Peerdraft’s real-time behavior.
Key Points
- 1
Peerdraft enables true simultaneous editing of Obsidian notes by pairing an Obsidian plugin with a Peerdraft web app that mediates session setup.
- 2
Shared sessions start in Obsidian via a command palette action that copies a link; collaborators join through the web app.
- 3
Edits sync peer-to-peer using WebRTC with end-to-end encryption, keeping the mediator server out of the document content path.
- 4
Collaboration is not permissioned: anyone with the link can edit, and there’s no read-only mode.
- 5
The workflow is asymmetric for now: one participant must use Obsidian while the other uses the browser; full Obsidian-to-Obsidian real-time collaboration isn’t available yet.
- 6
Session activity doesn’t persist after stopping, and there’s no post-session record of who typed what.
- 7
Peerdraft’s closed-source, non-self-hostable design and stored usage metadata make it less suitable for highly confidential notes.