ZIP Structure
Example
Exporting a workspace with two top-level docs, a Product Specs folder and an Archive sub-folder inside it gives you:
monday_docs_export_2026-09-27.zip
├── team_handbook.md
├── meeting_notes.md
├── product_specs/
│ ├── q3_roadmap.md
│ ├── api_design_v2.md
│ └── archive/
│ └── old_spec_2025.md
└── attachments/
├── architecture.png
└── roadmap_timeline.jpg
Archive Name
| Export | ZIP name |
|---|---|
| Several docs | monday_docs_export_<YYYY-MM-DD>.zip, using your local date |
| A single doc | <doc_name>.zip, or just <doc_name>.md when attachments are off |
Inside Each File
Each file holds the doc's content, starting with its first block. The doc's name isn't repeated inside the file; it's used for the file name. An empty doc gives an empty file.
File Names
Each doc becomes one .md file named after the doc:
- Letters and numbers are kept, in any language
- Any run of spaces, punctuation or symbols becomes a single
_ - The name is lowercased
| Doc name | File name |
|---|---|
Q3 Roadmap |
q3_roadmap.md |
API Design (v2) |
api_design_v2.md |
Café & Résumé |
café_résumé.md |
日本語ドキュメント |
日本語ドキュメント.md |
Docs With the Same Name
Nothing is overwritten. If two docs would get the same file name in the same folder, the second gets _2, the third _3, and so on. That includes names that only differ in case or punctuation, like Plan A and plan-a:
plan_a.md
plan_a_2.md
Folders
- Docs that aren't in a folder go at the top level of the ZIP
- Docs in a workspace folder go in a matching folder in the ZIP
- Sub-folders nest inside their parent folder, as they do in monday.com
- Two different folders that would get the same name are kept apart with
_2 - Empty folders are not created
Images and Attachments
This section applies when Include attachments is on, which is the default. With it off there's no attachments/ folder, and every image keeps its original link.
Images embedded in your docs are downloaded once and stored in one shared attachments/ folder at the root of the ZIP. The image links in each file point there, relative to where the file is, so they work in any Markdown viewer:
<!-- a doc at the top level -->

<!-- a doc inside product_specs/ -->

- The same image used in several docs is stored once
- Different images with the same file name are kept apart with
_2 - If an image can't be downloaded, for example because the site hosting it blocks downloads, the Markdown keeps its original URL so nothing is lost silently