> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bymiles.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Files and export

> Inspect generated site files and retrieve HTML or WordPress deliverables.

## `miles site-pages`

```bash theme={"dark"}
miles site-pages [--json]
miles site-pages <path> [--output <file>] [--json]
```

Without a path, lists the built static site's files. The JSON result contains `slug` and `files`; each file has `path`, `mimeType`, `sizeBytes`, and usually a `previewUrl`.

With a path, prints the file content. Add `--output <file>` for binary files or when the agent needs a local copy. Use this to inspect generated HTML or CSS, verify page coverage, or compare a generated file in a normal repository workflow.

## `miles export`

```bash theme={"dark"}
miles export [--type html] [--json]
miles export --type theme [--json]
miles export --type theme --download <file> [--json]
miles export html|theme [--json]
```

`html` is the default and is available once the site build completes. It returns `previewUrl` and `slug`. It is fully headless.

`theme` is available after `convert-theme`. It returns `themeSlug`, `downloadUrl`, `editorUrl`, and `dashboardUrl`. Reading that metadata is headless; `--download <file>` needs the connected browser workspace for design sandboxes and writes the theme ZIP to the chosen file.

Miles does not currently provide a WordPress blueprint, WXR/content export, or other export types.

## Related commands

Use `miles screenshot <preview-url>` to render a stored design or HTML preview. Use `miles screenshot --live` to capture the actual WordPress frontend after conversion; that form needs a browser connection.

Next: [Lifecycle and compatibility](/reference/miles-cli/lifecycle-and-compatibility).