# Version history for a shared Markdown file

> Floppy keeps a version history for every shared Markdown file, so an edit never overwrites your text. Each new version, from you, a teammate or an AI such as Claude, lands on the same link with a one-line note. Anyone reading can step back through the versions and turn on Show changes.

Floppy 1.24.0, released 2026-11-12. Updated 2026-11-14. https://fpy.sh/changelog/markdown-version-history

## How does version history work for a shared Markdown file?

A link that holds one Markdown file keeps every version, numbered v1, v2, v3. The file as first uploaded is v1.

- Every new version needs a note of 1 to 280 characters saying what changed.
- A line under the share bar says which version you're reading, who made it, when, and their note.
- A new version restarts the link's expiry: a link set to one week runs a week from the latest version.

## How do I add a new version?

Upload it on the share page, or have your AI push it.

1. Open the link and choose **Upload a new version…** in the ▾ menu.
2. Drop the edited .md file, or paste the Markdown.
3. Write one line on what changed, like "Tighten the intro".
4. Press the **Upload** button.

Floppy checks the new version for malware, which takes a few seconds. Until it passes, readers see the previous version.

The owner decides who may add versions: see [choose who can edit a shared file](https://fpy.sh/changelog/choose-who-can-edit-a-shared-file). Anyone else can [ask to edit](https://fpy.sh/changelog/ask-to-edit-a-shared-document).

## How do I see what changed between versions?

Turn on **Show changes** in the version line, or press C. Added words are highlighted and removed ones are struck through, in the text itself.

- Press V, or the clock in the bar, for the list of versions, newest first.
- With the list open, the arrow keys step through the versions.
- An older version says so at the top, with **Back to latest**.
- The address follows along: fpy.sh/k3x9?v=2 opens version 2 for anyone you send it to.

## Can I restore an older version?

Yes, if you own the link. Open the older version and press **Restore v2**. It becomes the newest version, noted "Restored v2", and every version in between stays in the history.

On a team link, a team admin can restore too.

## For AI agents

Over MCP at https://fpy.sh/mcp:

- `read_doc { link }` returns the name, `version`, full `text` and `can_push`.
- `push_version { link, text, note, base }` saves the whole edited document as the next version. `base` is the version you read.

Over REST: `GET https://fpy.sh/<slug>.md` reads the latest version (`?v=2` for an older one). `PUT /api/v1/links/<slug>/versions` pushes one, with `x-note` and `x-base` headers. `POST /api/v1/links/<id>/versions/<n>/restore` restores one.

Try: "Read fpy.sh/k3x9, tighten the intro, and push it back as a new version."

## FAQ

### Is there a limit on how many versions a file can have?

There is no set number. Each version can be up to 2 MB of Markdown, and older versions count toward the owner's storage.

### What happens if two people push a version at the same time?

Floppy checks one version at a time. The second push is asked to wait a few seconds, read the latest version and push again on top of it.

### Do I get an email when someone adds a version?

Yes. When someone else's version goes live, the owner gets an email like "Sam pushed v4 of plan.md". It has a summary of the changes and a See what changed button. Turning off Notify me for that link stops it.

### Does version history work for PDFs and other files?

No. Versions are for links that hold one Markdown file. For a PDF, a deck or an image, replace the file instead. The link stays the same, and the old file waits in Recently deleted.

## What shipped in 1.24.0

- A shared Markdown file keeps every version. Pushing or restoring never deletes anything, and older versions count toward your storage
- Press V or the clock for every version, newest first. Show changes marks added and removed words, and the owner can restore any version
- Open in Claude, ChatGPT, Codex or Cursor from the reader, and the AI can push its edit back as a new version
- Choose who can push in a link's settings: Only me, People I invite, or Anyone signed in

## Related

- [Choose who can edit a shared file](https://fpy.sh/changelog/choose-who-can-edit-a-shared-file)
- [Share a Markdown file as a web page](https://fpy.sh/changelog/share-a-markdown-file-as-a-web-page)
- [Replace a shared file, keep the same link](https://fpy.sh/changelog/replace-a-shared-file-keep-the-same-link)
- [Floppy for agents: MCP and REST docs](https://fpy.sh/docs/agents)

All releases: https://fpy.sh/changelog · Everything for LLMs: https://fpy.sh/llms.txt
