Importing Content - Marble Documentation
Skip to main content
You can bring your existing .md and .mdx files into Marble as draft posts. Marble imports happen asynchronously: you upload a file, Marble queues a job, a worker parses the content in the background, and the created drafts show up in your posts list when the job completes.

​
Starting an import

  1. Open Settings → Data in your workspace.
  2. Find the Import Content section.
  3. Click Import.
  4. Upload a single Markdown file or a ZIP archive (see Supported uploads).
Marble queues the import and starts processing it in the background. You can leave the page while it runs — the status updates automatically when you return.
Imports are capped at 4 MB per upload. Each ZIP archive may contain up to 100 Markdown files and 20 MB of extracted content. Entries that are not .md or .mdx are skipped.

​
Supported uploads

Imported posts are always created as drafts so you can review them before publishing.

​
Frontmatter

Marble reads standard YAML frontmatter keys from each file. When a key is missing, the post falls back to a sensible default: Categories and tags are matched to existing ones by slug, so category: Coding lands in your Coding category. Any that don’t exist yet are created for you.
URL-based imports are not supported. You must upload a file or ZIP archive.

​
Job lifecycle

Each import moves through these states: The most recent imports are listed under Import Content, with a View posts link once a job completes.

​
Supported Markdown syntax

The following core Markdown features are preserved on import: Importing unsupported syntax might not display properly.

​
MDX and components

If your content uses MDX, Marble will keep JSX-style components and custom MDX syntax in the source:
  • MDX elements like <MyComponent prop="value" />
  • Shortcodes or layout wrappers used in .mdx files
However:
  • ❌ Custom components will not render inside the Marble editor preview.
  • ❌ Marble does not execute or parse your components for you. You need to parse the imported MDX inside your own codebase (for example, using your framework’s MDX pipeline) for those components to work at runtime.
You can safely import your existing Markdown (.md) and MDX (.mdx) files into Marble. Each file becomes a draft post you can review before publishing, and any MDX components remain in the source so they continue to work when parsed in your own application.