How to Export and Share Your Unreal Engine Project Documentation

The problem: docs that never leave the editor

You have spent weeks writing useful notes against your Blueprints, but they only live inside one editor window on one machine. When a contractor joins, when you archive a finished milestone, or when you simply want a readable record outside Unreal, the obvious question is how to export Unreal Engine project documentation as a folder you can actually share.

Markdown 4 Blueprints is built for exactly this. It is an editor-only WYSIWYG documentation tool that lets you write rich notes attached to a specific Blueprint or asset, or as standalone notes, and saves them as plain .md files inside your project. Because the underlying format is ordinary Markdown, getting your documentation out is a single deliberate action rather than a copy-paste marathon.

This tutorial walks through the one-click Export Notes workflow, explains the folder structure you get back, and shows how to use that export for team handoff and long-term archival.

Where your notes live before you export

Understanding the export first means knowing how Markdown 4 Blueprints stores notes day to day. Per-asset notes are written to Documentation/Blueprints inside your project, mirroring the content hierarchy so a note for a given asset sits at a path that matches the asset's own path. Standalone notes that are not tied to any Blueprint go under Documentation/Blueprints/Standalone.

Notes auto-save 500ms after you stop typing, and the tool auto-detects the active Blueprint so the right document loads as you move between assets. You write everything through a visual editor, with toolbar controls for tables, a native file picker for images you can resize inline, and Ctrl+B, Ctrl+I and Ctrl+U for bold, italic and underline. Nothing about the editing experience requires you to hand-write Markdown syntax.

If you want the in-project storage location somewhere other than the default, the storage path is configurable in Project Settings under Blueprint Markdown. That setting governs where notes are kept inside the project, which is separate from the export destination you choose in the next step.

One-click Export Notes, step by step

1. Open the documentation tab. Use Window then Blueprint Documentation, or the button the plugin adds to the Level Editor toolbar and the Blueprint Editor toolbar. Confirm your notes are present in the sidebar; the Expand-all-folders toggle helps you see the full tree at a glance.

2. Make sure the notes you care about are saved. Because auto-save fires shortly after you stop typing, you usually do not need to do anything, but it is worth pausing for a moment after your last edit so the final change is written to disk.

3. Trigger Export Notes. This is the one-click action that copies your documentation out to an external folder named '{ProjectName} Documentation', preserving the same file structure your notes use inside the project.

4. Choose a destination outside the project. The export targets a folder external to the Unreal project itself, so pick somewhere convenient for sharing or storage rather than a path inside your project tree.

5. Verify the result. Open the exported '{ProjectName} Documentation' folder and confirm the per-asset .md files and the Standalone folder are present and readable. Every file is plain Markdown, so any text editor, Git host, or static-site generator can render it.

What the exported folder looks like

The export is intentionally boring in the best way: it is a folder of Markdown files that mirrors how your notes were organised in the editor. Per-asset notes keep their hierarchical paths so a reader can navigate documentation the same way they navigate your content, and standalone notes land in their own Standalone subfolder.

Because the files are standard Markdown, they slot straight into the tools your team already uses. You can drop the folder into a repository and let your Git host render the .md previews, feed it to a documentation site generator, or simply open it in any Markdown-aware editor. There are no proprietary containers, no database, and no internet dependency anywhere in the loop; the tool is fully offline.

Keep in mind what Export Notes is and is not. It produces a documentation bundle of Markdown files for people to read; it does not render your notes into your game's UI at runtime. Markdown 4 Blueprints is an editor-only authoring tool, so the export is a developer-facing deliverable, not an in-game content feature.

Using the export for handoff and archival

For handoff, the exported folder is the cleanest thing you can put in a new collaborator's hands. Because per-asset notes mirror your content hierarchy, a contractor or new hire can read the documentation for a system and immediately know which Blueprint it describes. Pair the export with the source project and the recipient has both the assets and the human context behind them.

For archival, exporting at the end of a milestone gives you a frozen, human-readable snapshot of design intent that does not depend on having the exact editor and plugin installed to read it later. Even years on, a folder of Markdown opens anywhere. If you also keep the in-project notes under source control, you get both a living copy that evolves with the project and a clean exported bundle you can attach to a release.

A practical next step: after your next significant feature lands, write or tidy the per-Blueprint notes for it, then run Export Notes into a versioned folder name so each archived bundle is easy to tell apart. From there, share the folder with your team or commit it, and you have turned in-editor knowledge into something durable and portable. If you want runtime documents to sit alongside your developer docs, Simple PDF Viewer can render PDF manuals in-world, while EasyHTTP and Fast Chart Widgets cover the connectivity and dashboards many of the same projects end up needing.

FAQ