MediaWiki extension that makes Markdown a native content model: whole pages are stored and edited as Markdown and rendered with real wiki integration (internal links, categories, search, templates, and more), coexisting with wikitext pages on the same wiki.
Because pages are stored as plain Markdown, they are directly consumable and writable by LLMs and agents:
action=raw returns clean Markdown; no wikitext conversion needed.
See For AI agents and LLMs.
- Introduction to the extension
- Usage documentation
- Installation
- Configuration
- Templates and parser functions
- For AI agents and LLMs
- Comparison with other Markdown extensions
- Development
- Release notes
Get professional support for this extension via Professional Wiki, its creators and maintainers. We provide MediaWiki Development, MediaWiki Hosting, and MediaWiki Consulting services.
Platform requirements:
Installation uses Composer with MediaWiki's built-in support for Composer.
On the command line, go to your wiki's root directory. Then run these two commands:
COMPOSER=composer.local.json composer require --no-update professional-wiki/native-markdown:~1.0composer update professional-wiki/native-markdown --no-dev -oThen enable the extension by adding the following to the bottom of your wiki's LocalSettings.php file:
wfLoadExtension( 'NativeMarkdown' );For Markdown syntax highlighting in the editor, also install the CodeEditor extension:
New pages use the Markdown content model where the wiki's configuration says so. Defaults apply to page
creation only; existing pages never change model implicitly. Individual pages can be switched between
wikitext and Markdown (in both directions) via Special:ChangeContentModel.
| Setting | Default | Effect |
|---|---|---|
$wgNativeMarkdownNamespaces |
[] |
Namespace IDs in which new pages default to Markdown, e.g. [ NS_HELP ] |
$wgNativeMarkdownEverywhere |
true |
New pages everywhere default to Markdown, the "Markdown wiki" mode (see exclusions below); set to false to keep wikitext as the default |
$wgNativeMarkdownSuffixDetection |
false |
New pages whose title ends in .md default to Markdown, except in the Template and MediaWiki namespaces |
$wgNativeMarkdownAllowExternalImages |
false |
Embed external  images; when off they render as plain links |
$wgNativeMarkdownWikitextExpansion |
true |
Run {{...}} on Markdown pages through the MediaWiki parser: templates, parser functions, magic words, and Lua modules. Set to false to leave {{...}} as literal text (see Templates and parser functions) |
$wgNativeMarkdownEverywhere covers the whole prose wiki, but deliberately leaves some pages as wikitext: the
discussion (Talk) namespaces, where signatures and threading depend on wikitext; the Template and MediaWiki
namespaces; and any namespace whose content model is explicitly configured elsewhere (for example a Scribunto
or JSON namespace). Titles ending in .css, .js or .json never default to Markdown either, since MediaWiki
reserves those for code pages. External links honor the core $wgNoFollowLinks setting. Input size is bounded
by core's $wgMaxArticleSize.
$wgNativeMarkdownSuffixDetection reads the .md suffix as a deliberate per-page choice, so — unlike the
wiki-wide mode — it also applies inside Talk namespaces, where a Markdown talk page then has no wikitext
signatures or threading. It still skips the Template and MediaWiki namespaces, where Markdown can act as
neither a template nor an interface message; add those to $wgNativeMarkdownNamespaces to opt them in anyway.
Markdown pages can use MediaWiki's {{...}} syntax. Because expansion delegates to the wikitext parser, this
covers the whole double-brace surface: templates (a wiki's shared infoboxes, citations and navboxes), parser
functions ({{#if:}}, {{#switch:}}, and so on), magic words and variables ({{PAGENAME}}, {{CURRENTYEAR}}),
and, where Scribunto is installed, Lua modules via {{#invoke:}}. Set
$wgNativeMarkdownWikitextExpansion = false to turn this off and leave {{...}} as literal text.
{{Infobox person
| name = Ada Lovelace
| born = 1815
}}
Ada Lovelace was an English **mathematician**, regarded as the first computer programmer.Because it is the real parser, the same trust and resource model as wikitext applies: template dependencies are
tracked (editing a template reparses the pages that transclude it), recursion and size limits apply, and output
is sanitized exactly as wikitext is. Enabling {{...}} on a Markdown page grants the same capabilities a
wikitext page has, so on a wiki with untrusted editors, weigh it the same way you weigh wikitext templates,
parser functions and Lua.
Placement follows the split between block and inline content:
- A call on its own line produces block output, so an infobox table renders as a block rather than being wrapped in a paragraph. It may span multiple lines, including blank parameter lines, until the braces balance.
- A call within a line of text renders inline and must stay on a single line; multi-line calls have to start on their own line.
- Template arguments are wikitext, not Markdown. Inside a GFM table cell, escape argument pipes as
\|. Write\{\{to keep braces literal. - A block call with no closing
}}is rendered as literal text through to the end of the page (Markdown parsing cannot backtrack), so a forgotten brace shows up as visible braces to fix rather than a silent error.
Out of scope in this version, by design:
<ref>...</ref>and<references/>in the Markdown body (these are tags, not{{...}}), and citation state is not shared across separate calls on a page.- Transcluding another Markdown page with
{{:Page}}: its source would be reinterpreted as wikitext, so transclude wikitext pages instead.subst:does not substitute on save. - Enabling the setting does not reparse existing pages; they show template output once edited or purged. Run
refreshLinks.phpto populate the template links eagerly.
Markdown is the native read/write format of today's language models, and Native Markdown stores pages as exactly that: plain Markdown, no wikitext wrapper. That makes a Markdown page directly consumable and directly writable by an agent, with no lossy conversion step in either direction:
-
Read the source with
action=raw:GET /index.php?title=Release_Notes.md&action=rawreturns the raw Markdown, front matter and all, exactly the bytes an author typed.
-
Read via the REST API, which also reports the model:
GET /rest.php/v1/page/Release_Notes.md → { "content_model": "markdown", "source": "# Release Notes\n...", ... } -
Read the rendered HTML with
action=parse(?action=parse&page=Release_Notes.md&prop=text), for when an agent wants the resolved links and table of contents rather than the source. -
Write through the ordinary editing APIs (
action=edit, the REST update endpoint) or, more conveniently, through the MediaWiki MCP Server: an agent hands over Markdown and it is stored verbatim, rendered with full wiki integration on read.
Because the round trip is lossless, an agent can fetch a page as Markdown, edit it, and write it back without
the content drifting through a wikitext translation. Full-text search indexes the rendered prose (not the raw
markup), so an agent's keyword lookups match what a reader sees rather than # and ** noise.
Native Markdown exists because no maintained extension makes Markdown a native content model:
- Extension:WikiMarkdown embeds Markdown blocks inside wikitext pages via a tag, plus a shallow
.mdcontent handler on top of Parsedown. Inside the Markdown there are no working[[wiki links]], no category assignment and no MediaWiki table of contents. Native Markdown makes the whole page Markdown, with links, categories, ToC, search and link tables behaving like they do on wikitext pages. - Extension:Markdown is archived and points visitors to WikiMarkdown.
- MarkdownExtraParser has been unmaintained for over a decade.
Related but different: our ExternalContent extension embeds Markdown files from external sources (like GitHub) into wikitext pages, while Native Markdown is for the wiki's own pages being Markdown. They compose nicely.
The Application layer (the whole Markdown pipeline) has no MediaWiki dependencies, so the unit suite runs standalone in the extension directory with no MediaWiki install:
composer install
composer testStyle checks and static analysis, also standalone: composer cs, composer phpstan, composer psalm.
The full suite including integration tests runs inside a MediaWiki install, from the MediaWiki root:
php tests/phpunit/phpunit.php extensions/NativeMarkdown/tests/phpunit/- Redirect pages now render and register the content after the
#REDIRECT [[Target]]line, so redirect categories (and any other trailing links or prose) work the same as on wikitext redirects
Initial release for MediaWiki 1.43+ with these features:
- Markdown content model (
markdown) rendering CommonMark + GitHub Flavored Markdown with footnotes - Wikitext link syntax inside Markdown: internal links, section links, categories, file embeds, interwiki
- MediaWiki integration: table of contents, red/blue links, link tables, WhatLinksHere, WantedPages/Files
- Clean full-text search: rendered prose is indexed, not raw markup; front matter excluded
- YAML front matter parsed, hidden from output and stored as page metadata
- Per-page model switching via
Special:ChangeContentModel, namespace/suffix/wiki-wide activation modes - MediaWiki
{{...}}expansion (on by default): templates, parser functions, magic words and Lua run through the real parser with dependency tracking; opt out with$wgNativeMarkdownWikitextExpansion = false - XSS-safe by construction: raw HTML escaped, unsafe links blocked, external images off by default
action=raw/ REST return the stored Markdown byte for byte, built for AI agents and git round-trips- CodeEditor syntax highlighting on Markdown pages