
By default, exporting produces a ZIP archive that mirrors your Confluence page hierarchy as a folder structure.
my-space-export-2026-04-08.zip
├── Parent Page.md
├── Parent Page/
│ ├── Child Page One.md
│ ├── Child Page Two.md
│ └── Nested Section/
│ └── Deep Page.md
└── attachments/
├── Child Page One/
│ └── screenshot.png
└── Deep Page/
└── diagram.pdf
Each .md file's name is determined by your Filename Pattern setting. Attachment files are placed in a per-page subfolder under attachments/.
Links between pages in the export are converted to relative paths — for example:
See [Child Page One](./Parent%20Page/child-page-one.md) for details.
This means the exported ZIP is self-contained and links work correctly when rendered locally or published as a static site.
When Include attachments is checked (ZIP mode only), all files attached to each exported page are downloaded and included in the ZIP under the attachments/ folder.
Each attachment is referenced in the markdown with a relative path:

Attachment downloading happens in small parallel batches with rate limiting to avoid hitting Confluence API limits.
While the export is running, a progress bar shows:
Once complete, the file downloads automatically and the progress panel shows a Download again button if you need it.