diff --git a/src/frontend/src/content/docs/reference/cli/commands/aspire-export.mdx b/src/frontend/src/content/docs/reference/cli/commands/aspire-export.mdx
index 44f36196f..6d43e50bd 100644
--- a/src/frontend/src/content/docs/reference/cli/commands/aspire-export.mdx
+++ b/src/frontend/src/content/docs/reference/cli/commands/aspire-export.mdx
@@ -61,6 +61,21 @@ The following options are available:
 
 - <Include relativePath="reference/cli/includes/option-wait.md" />
 
+## Zip file contents
+
+The exported zip archive (default name `aspire-export-<timestamp>.zip`) can contain up to four directories, depending on available data:
+
+- **`resources/`** — One JSON file per resource containing resource details such as name, type, state, endpoints, and environment variables.
+- **`consolelogs/`** — One plain-text `*.txt` file per resource with raw console output lines.
+- **`structuredlogs/`** — One JSON file per resource with structured log entries serialized in [OTLP format](https://opentelemetry.io/docs/specs/otlp/).
+- **`traces/`** — One JSON file per resource with distributed traces and spans serialized in [OTLP format](https://opentelemetry.io/docs/specs/otlp/).
+
+When a resource name is provided, only data for that resource is included in the archive. When no resource is specified, data for all visible resources is exported.
+
+:::tip
+When analyzing an export, start with the `resources/` directory for an overview of resource state, then drill into `consolelogs/`, `structuredlogs/`, and `traces/` for detailed diagnostics.
+:::
+
 ## Examples
 
 - Export diagnostics for the current AppHost: