Get AI summaries of any video or article — Sign up free
Real-time collaboration in Obsidian with Peerdraft thumbnail

Real-time collaboration in Obsidian with Peerdraft

Nicole van der Hoeven·
5 min read

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.

TL;DR

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?

Peerdraft uses two parts: an Obsidian community plugin and a Peerdraft web app. In Obsidian, the user starts a “sharing session” from the command palette, which copies a session link. The collaborator opens that link in the web app, and the connection is peer-to-peer. The Peerdraft web app mainly mediates session setup—helping peers find each other—while the document changes are exchanged directly via WebRTC. The developer describes the content as end-to-end encrypted and not visible to the mediator server.

What are the practical limits of collaboration—who can edit, and where must each person be?

Peerdraft doesn’t offer read-only sharing; anyone with the session link can edit the note. It also isn’t fully Obsidian-to-Obsidian yet: one participant must start the session from Obsidian, and the other must join through the browser. During testing, both sides could not be in the browser simultaneously, and the workflow depended on one person using Obsidian while the other used the web editor.

What happens when the shared session ends, and what evidence remains afterward?

Edits and session context are real-time only. Once the session stops, the note doesn’t keep a persistent collaboration record on Peerdraft, and there’s no way to review who typed what after the session ends. During the session, there may be visibility into activity, but after stopping, that attribution isn’t retained in the way some collaborative tools do.

Why might Peerdraft feel different from Google Docs during a live session?

Presence and joining aren’t clearly signaled. Testers reported no obvious indicator that another collaborator joined the session, which can make someone feel like a “creepy lurker” until they start typing or communicate afterward. Google Docs typically makes it clear when others are in the document, so Peerdraft’s join behavior can surprise users who expect visible presence cues.

How does Peerdraft compare with Obsidian Sync and Etherpad Lite for real-time co-editing?

Obsidian Sync can support collaboration but may require both parties to pay and still produced conflicts in simultaneous typing tests (one user’s changes could be overwritten or not visible until later). Etherpad Lite required pushing content to an external editor, editing there, then pulling changes back—more like a round-trip workflow than true live co-editing. Peerdraft’s advantage in the tests was instant, low-latency synchronization that supported brainstorming on the same note at the same time.

What security and privacy constraints should users consider before sharing confidential notes?

Peerdraft is closed source and can’t be self-hosted, which limits control over where data runs. The developer says the mediator server doesn’t see document content, but it does observe session metadata like when a session starts and ends, and it stores usage duration to enforce the free-tier limits. That combination—no self-hosting plus some stored metadata—may matter for sensitive work.

Review Questions

  1. What technical mechanism does Peerdraft use to exchange edits, and what role does the Peerdraft web app play?
  2. List at least three limitations of Peerdraft collaboration (permissions, platform pairing, session persistence, notifications, or privacy).
  3. Compare the failure modes of Obsidian Sync and Etherpad Lite described in the transcript with Peerdraft’s real-time behavior.

Key Points

  1. 1

    Peerdraft enables true simultaneous editing of Obsidian notes by pairing an Obsidian plugin with a Peerdraft web app that mediates session setup.

  2. 2

    Shared sessions start in Obsidian via a command palette action that copies a link; collaborators join through the web app.

  3. 3

    Edits sync peer-to-peer using WebRTC with end-to-end encryption, keeping the mediator server out of the document content path.

  4. 4

    Collaboration is not permissioned: anyone with the link can edit, and there’s no read-only mode.

  5. 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. 6

    Session activity doesn’t persist after stopping, and there’s no post-session record of who typed what.

  7. 7

    Peerdraft’s closed-source, non-self-hostable design and stored usage metadata make it less suitable for highly confidential notes.

Highlights

Peerdraft’s core value is instant, low-latency co-editing inside Obsidian—without the copy/paste loop that pushes many users back to Google Docs.
The mediator server helps establish the connection, but the developer describes document content as end-to-end encrypted and not visible to the server.
A notable UX gap: there’s no clear notification when someone joins, so presence can be easy to miss compared with tools like Google Docs.
Unlike Obsidian Sync and Etherpad Lite, Peerdraft is built for real-time collaboration rather than syncing or round-tripping edits.

Topics

  • Obsidian Collaboration
  • Peerdraft Plugin
  • WebRTC
  • Real-Time Editing
  • Obsidian Sync