deep-dive

enable_builtins() vs enable_plugins() in MarkItDown: Core Differences Explained

April 11, 2026 microsoft/markitdown ↗

MarkItDown's enable_builtins() automatically registers the package's built-in file converters during initialization, while enable_plugins() discovers and loads optional third-party extensions via Python entry points, with the former enabled by default and the latter requiring explicit opt-in.

The Microsoft MarkItDown library provides two distinct mechanisms for registering file converters: built-in capabilities that ship with the core package, and an extensible plugin system for third-party formats. Understanding the difference between enable_builtins() and enable_plugins() is essential for controlling which

Have a question about this repo?

These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:

Share the following with your agent to get started:

curl -s "https://instagit.com/install.md"

Add to your MCP client configuration:

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}

Ask your agent:

"Use Instagit MCP to understand how microsoft/markitdown works."

Works with

Claude Codex Cursor VS Code OpenClaw Any MCP Client

Maintain an open-source project? Get it listed too →