Local version history for Markdown

Write without fear.

Recover.md quietly records changes across your Markdown workspace. Compare versions, search deleted text, and restore any captured file state in seconds.

Local-first·No Git·No cloud account required in the desktop app

Product preview

Local workspace

Notes / product-brief.md

Every captured state, ready when you need it.

  1. Large edit

    Today, 10:42 AM · 28 seconds ago

    +18−4
  2. Autosaved change

    Today, 10:31 AM

    +3−1
  3. File created

    Yesterday, 4:18 PM

    +42
Version from 10:31 AM → 10:42 AM+18 −4
18  18   ## Recovery principles
19   -   Save changes at fixed intervals.
    19 +   Capture meaningful changes automatically.
    20 +   Keep every snapshot on this device.
20  21   Restore without leaving your editor.
privacy-notes.md3 versions ago

All workspace history stays offline by default.

deleted-draft.mdDeleted · Jun 12

The recovery layer should remain offline by default.

Deleted file found

deleted-draft.md

Last captured Jun 12 at 3:14 PM · 6.8 KB · 184 lines

Preview the captured contents before restoring the file.

Version restored to product-brief.md

Works alongside Obsidian, Claude Code,Cursor, VS Code, and any editor that writes Markdown files.

The missing safety layer

Your best line should never disappear by accident.

A rewrite goes too far. An automated edit touches more than you expected. A draft gets replaced, renamed, or deleted. The right version existed a few minutes ago—but finding it becomes a forensic project.

Recover.md adds an independent history layer beneath your Markdown tools. It watches the files, records useful states, and makes the past easy to understand.

Built for real writing workflows

History that feels like part of the editor.

No repository ceremony. No hunting through duplicate files. Just a clear record of what changed and a fast way back.

01

Automatic history

Recover captures meaningful Markdown changes quietly in the background—without asking you to commit, name, or organize each version.

02

Readable comparisons

See exactly what changed between two file states with line-based diffs, timestamps, and clear added or removed counts.

03

Historical search

Find a phrase even when it lived in an older draft or a file that no longer exists in your workspace.

04

One-step restore

Preview any captured state, then restore that version or recover a deleted file without leaving your writing flow.

One local layer, every editor

Keep your tools. Add a memory.

Recover sits at the file layer, so your history stays continuous when you move between editors, terminal tools, and automated workflows.

OObsidian
CClaude Code
Cursor
</>VS Code
Recover.md

Capture · Compare · Search · Restore

On this device

Local-first by design

Your writing stays where it belongs.

History on your device

Captured file states are designed to remain local. Your workspace is not uploaded to create version history.

No account in the desktop app

Opening and using the planned desktop app will not require a cloud account or sign-in.

Your existing setup remains yours

Use Recover as an independent layer alongside sync, backup, Git, or whichever tools already fit your workflow.

How it works

From change to recovery in three quiet steps.

  1. 1

    Choose a workspace

    Point Recover at the folder where your Markdown lives.

  2. 2

    Keep writing normally

    Recover captures useful file states in the background as your work changes.

  3. 3

    Search, compare, restore

    Open a file’s timeline, inspect the difference, and bring back the state you need.

Questions, answered

A calm safety net for plain-text work.

Still curious? Join the private beta and reply to the confirmation email with what you want Recover to protect.

Does Recover.md replace my Markdown editor?

No. Recover.md runs beside the tools you already use and watches the Markdown files you choose. Keep writing in Obsidian, Claude Code, Cursor, VS Code, or any editor that saves Markdown.

Is this the same as Git?

It solves a narrower, more everyday problem. Recover.md captures useful local file history automatically, then makes comparison, search, and restore approachable without commits, branches, or repository setup.

Can it run alongside Obsidian Sync?

Yes. Recover.md is an independent local, cross-editor history layer and can run alongside Obsidian Sync. It does not replace your sync setup.

Does the desktop app require a cloud account?

No. The planned desktop app is local-first and does not require a cloud account. An email address is only needed to join the private beta and receive an invitation.

Which platforms will the beta support?

The first private beta is being scoped around desktop Markdown workflows. Join the list and we will ask which operating system and editor matter most to you before invitations go out.

Private beta

Make every draft recoverable.

Join the private beta for product updates and an invitation when Recover.md is ready for your desktop.

We’ll send one confirmation email. No product spam, and your address never enters analytics.

Recover.md is an independent product and is not affiliated with or endorsed by Obsidian.