Skip to main content
One of the core principles of software development is DRY (Don’t Repeat Yourself), which applies to documentation too. If you find yourself repeating the same content in multiple places, create a custom snippet for that content. Snippets contain content that you can import into other files to reuse. You control where the snippet appears on a page. If you ever need to update the content, you only need to edit the snippet rather than every file where the snippet appears.
Snippets are not currently supported in the web editor. To use snippets, edit your MDX files locally with the CLI or push snippet imports directly to your repository.

How snippets work

Snippets are any .mdx, .md, or .jsx files imported into another file. You can place snippet files anywhere in your project. When you import a snippet into another file, the snippet only appears where you import it and does not render as a standalone page. Any file in the /snippets/ folder is always a snippet even if it is not imported into another file.

Create snippets

Create a file with the content you want to reuse. Snippets can contain all content types supported by Mintlify and they can import other snippets. See Nested snippets for where to declare imports when nesting.

Import snippets into pages

Import snippets into pages using either an absolute or relative path.
  • Absolute imports: Start with / for imports from the root of your project.
  • Relative imports: Use ./ or ../ to import snippets relative to the current file’s location.
Relative imports enable IDE navigation. Press CMD and click a snippet name in your editor to jump directly to the snippet definition.

Import text

1

Add content to your snippet file

Add the content you want to reuse.
shared/my-snippet.mdx
2

Import the snippet into your destination file

Use either an absolute or relative path.

Nested snippets

Snippets can import other snippets. Declare the import in the snippet file that uses the nested snippet, not in the page that imports the parent snippet. Each file resolves its own imports. Imports declared on a page do not apply to the snippets that the page imports. A nested snippet that relies on a page-level import may render as empty content.
1

Import the nested snippet in the parent snippet file

Declare the import where you want to use the nested snippet.
shared/parent-snippet.mdx
2

Import only the parent snippet in your destination file

You do not need to import the nested snippet.
destination-file.mdx

Import variables

Reference variables from a snippet in a page.
1

Export variables from a snippet file

shared/custom-variables.mdx
2

Import the snippet from your destination file and use the variable

destination-file.mdx

Import snippets with variables

Use variables to pass data to a snippet when you import it.
1

Add variables to your snippet

Pass in properties when you import it. In this example, the variable is {word}.
shared/my-snippet.mdx
2

Import the snippet into your destination file with the variable

The passed property replaces the variable in the snippet definition.
destination-file.mdx
Variables also interpolate inside fenced code blocks. This is useful for snippets that include installation commands or other code examples that differ by package name, version, or environment.
shared/install-snippet.mdx
destination-file.mdx

Import React components

1

Create a snippet with a JSX component

See React components for more information.
components/my-jsx-snippet.jsx
When creating JSX snippets, use arrow function syntax (=>) rather than function declarations. The function keyword is not supported in snippets.
2

Import the snippet

destination-file.mdx