Offline export

Offline exports require an Enterprise plan.

Use mint export to package your entire documentation site into a zip archive of pre-rendered pages. Recipients can unzip and view the docs in their browser without a Mintlify account or any build tools. They only need Node.js installed. This is useful when you need to distribute documentation to users who can’t access your live site, such as for on-premise customers or internal compliance reviews. Exports are not fully self-contained. Some assets load from external hosts at runtime, and exports must be served from the root of a domain. Air-gapped environments, and hosting an export inside another application or under a subpath, are not fully supported. Review the limitations before you deploy an export to an environment without internet access.

Prerequisites

The CLI installed and up to date
Node.js v20.17.0+ installed

Limitations

Offline exports do not support search. To add offline search, index the exported HTML with a static search tool.
Offline exports do not support the Mintlify assistant.
Offline exports must be served from the root of a domain, such as http://localhost:3000/. Serving an export under a subpath, such as /docs, is not supported.
Some assets load from external hosts at runtime. Without internet access, or behind a Content Security Policy that blocks these hosts, they fail to load.

Assets that load from external hosts

Asset	How to avoid the external request
Icons referenced by name, such as Font Awesome and Lucide icons	Use custom image icons stored in your project.
Code block language icons and language selector flags	None. These always load from Mintlify’s CDN.
LaTeX stylesheets	If your content doesn’t use math expressions, set `styling.latex` to `false`.
Google Fonts and externally hosted fonts	Use local fonts stored in your project.

Export your site

Navigate to your documentation directory containing your docs.json file and run:

mint export

The CLI builds your site, crawls every page defined in your navigation, and packages the output into a zip file in your current directory.

Options

Flag	Description	Default
`--output <path>`	Set the output zip file path.	`export.zip`
`--groups <group>`	Mock user groups for the export. Useful when your docs use group-based access control and you want the archive to include restricted pages.	—
`--disable-openapi`	Skip OpenAPI file generation during the export. Use this if you have many OpenAPI specs and want faster builds.	—

For example, to export your site to a custom filename with a specific user group:

mint export --output customer-docs.zip --groups enterprise

The export only includes pages listed in your navigation. Hidden pages are not included in the archive.

Security considerations

The exported archive is a static, unauthenticated bundle. Anyone with the zip file can view every page it contains.

The --groups flag controls which group-restricted pages Mintlify includes in the archive at export time. It does not enforce authentication after export.
Only share archives with recipients who are allowed to see the content they contain.
Regenerate and redistribute the archive to publish new changes. Anyone running an older zip continues to see the older content.

What’s in the zip

The exported archive contains your pre-rendered pages, their bundled assets, and a server to view them:

File	Purpose
HTML pages	Pre-rendered version of every page in your navigation
`_next/static/`	Bundled CSS, JavaScript, and other static assets
`serve.js`	Zero-dependency Node.js HTTP server that serves the site
`Start Docs.command`	macOS launcher. Double-click to open the docs.
`Start Docs.bat`	Windows launcher. Double-click to open the docs.

View the exported docs

Share the zip file with anyone who has Node.js installed. To view the docs:

Manual
macOS
Windows

Unzip the archive.
Open a terminal in the unzipped directory.
Run node serve.js.
Open http://localhost:3000 in your browser.

Unzip the archive.
Double-click Start Docs.command.
The docs open in your default browser at http://localhost:3000.

macOS may block the file because it was downloaded from the internet. If you see a security warning, go to System Settings > Privacy & Security and click Open Anyway. See Apple’s guide to overriding security settings for details.

Unzip the archive.
Double-click Start Docs.bat.
The docs open in your default browser at http://localhost:3000.

Windows may show a “Windows protected your PC” warning because the file was downloaded from the internet. Click More info, then click Run anyway.

Get started

Create content

Manage your site

Agent

Assistant

Agent-ready content

Search and SEO

Document APIs

Integrations

Reference

Prerequisites

Limitations

Assets that load from external hosts

Export your site

Options

Security considerations

What’s in the zip

View the exported docs

​Prerequisites

​Limitations

​Assets that load from external hosts

​Export your site

​Options

​Security considerations

​What’s in the zip

​View the exported docs

Prerequisites

Limitations

Assets that load from external hosts

Export your site

Options

Security considerations

What’s in the zip

View the exported docs