> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/seascape-for-notes/archiving-with-seascape/creating-a-disk-archive.md).

# Extract to Disk - Overview

The **"Extract to Disk"** option enables you to export your Notes content to a folder on your disk.

This type of archive includes:

* **PDF files**, which store the content of the Notes forms
* **XML files**, which store the Notes metadata
* **Document attachments**

When creating your archive, you can choose to [**name the PDF files using configurable rules**](/seascape-for-notes/faq/how-to-configure-pdf-file-naming-rules.md) and [**generate a custom folder structure**](/seascape-for-notes/seascape-settings/folder-formulas.md) for storing the files.

The disk archive also **retains links between PDF documents**, preserving the same relationships that existed in Lotus Notes via doclinks.

For additional convenience, a CSV Creator tool is provided which enables you to merge the XML metadata into a single or multple CSV files (one CSV per Notes form). More info: [Save Notes metadata in CSV format](/seascape-for-notes/archiving-with-seascape/metadata-into-csv-format.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.swingsoftware.com/seascape-for-notes/archiving-with-seascape/creating-a-disk-archive.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.