> 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/pdf-converter-for-notes/getting-started/pdf-converter-terminology/flat-vs.-structured-document-export.md).
# Flat vs. structured document export
A ‘**flat document export**’ means that the selected Notes documents or emails will be converted to separate PDF files which will be saved in a selected location (in a flat document view).
The structured export however also allows you to save the structure of your Notes views (e.g. parent-child relationships, view categories, folders etc.) in the export. The structure of the Notes views, folders or categories is saved in one of two ways:
1. By exporting the selected Notes documents into a **Single PDF File with a Bookmarks View** (which resembles the original Notes view)
2. By automatically re-creating the folder structure on your hard drive (and then populating the folders with corresponding PDF files)
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.swingsoftware.com/pdf-converter-for-notes/getting-started/pdf-converter-terminology/flat-vs.-structured-document-export.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.