Skip to main content
Preview deployments are available on Pro and Custom plans.
Preview deployments let you see how changes to your docs will look before merging to production. Each preview creates a shareable URL that updates automatically as you push new changes. Preview URLs are publicly viewable by default. Share a preview link with anyone who needs to review your changes.

​
Create preview deployments

Preview deployments are created automatically through pull requests or manually from your dashboard.

​
Automatic previews

Automatic previews are only created for pull requests targeting your deployment branch.
When you create a pull request, the Mintlify bot automatically adds a link to view the preview deployment in your pull request. The preview updates each time you push new commits to the branch.
Link to view deployment in the pull request timeline

​
Manual previews

You can manually create a preview for any branch.
  1. Go to your dashboard.
  2. Select Previews.
  3. Select Create custom preview.
  4. Enter the name of the branch you want to preview.
  5. Select Create deployment.

​
Redeploy a preview

Redeploy a preview to refresh content or retry after a failed deployment.
  1. Select the preview from your dashboard.
  2. Select Redeploy.
The Previews menu with the deploy button emphasized by an orange rectangle.

​
Restrict access to preview deployments

By default, preview deployments are publicly accessible to anyone with the URL. You can restrict access to authenticated members of your Mintlify organization.
  1. Navigate to the Previews section in the Add-ons page of your dashboard.
  2. Click the Preview authentication toggle to enable or disable preview authentication.
The preview authentication toggle in the Add-ons page

​
Troubleshooting preview deployments

If your preview deployment fails, try these troubleshooting steps.
  • View the build logs: In your dashboard, go to Previews and click the failed preview. The deployment logs show errors that caused failures.
  • Check your configuration:
    • Invalid docs.json syntax
    • Missing or incorrect file paths referenced in your navigation
    • Invalid frontmatter in MDX files
    • Broken image links or missing image files
  • Validate locally: Run mint dev locally to catch build errors before pushing to the repository.
  • Check recent changes: Review the most recent commits in your branch to identify what changes caused the build to fail.