# Edit history

- Human documentation: [https://docs.univer.ai/guides/pdfs/features/edit-history](https://docs.univer.ai/guides/pdfs/features/edit-history)

- Agent Markdown: [https://docs.univer.ai/guides/pdfs/features/edit-history.md](https://docs.univer.ai/guides/pdfs/features/edit-history.md)

- Requested language: `en-US`

- Content language: `en-US`

- Documentation version: `1.0.0-rc.0`

- Source: [pdfs/features/edit-history.mdx](https://github.com/dream-num/documentation/blob/dev/content/guides/pdfs/features/edit-history.mdx)

---

PDFs supports undo and redo during editing. It does not currently provide a dedicated version-history panel plugin equivalent to those for Sheets, Docs, Slides, Boards, or Bases. Do not register another product's History UI plugin for PDFs.

## Undo and redo

Undo and redo act on the focused Univer unit:

```ts
await univerAPI.undo()
await univerAPI.redo()
```

These operations do not create a server-side version list or retrieve versions from previous sessions. See [General API](https://docs.univer.ai/guides/pdfs/features/core/general-api.md) for other operations.

## Versions across sessions

Start with [PDFs collaboration](https://docs.univer.ai/guides/pdfs/features/collaboration.md). For long-term version retention, consult the [Office history service](https://docs.univer.ai/server/collaboration/extensions.md), verify PDF data support in your target release, and implement the version list and viewer in your application. Adding the generic History service does not automatically add a PDF history panel.

Restoring content requires document authorization, coordination with the active collaboration session, and retention of associated PDF files. Replacing the data displayed on the page is not sufficient.