Markdown is markup you can read with your own eyes, and the format language models read best. MEDIAWIKI is another one. pandoc sits between the two, and this page says exactly what happens to an MD file on the way to becoming a MEDIAWIKI one.
What runs when an MD file becomes MEDIAWIKI
pandoc in two passes, on a machine we rent and watch. Your MD file is uploaded once, pandoc runs once, the MEDIAWIKI comes back, and neither file is kept. MD to MEDIAWIKI is one of the 3649 pairs that engine was probed on with a real file, which is why it has a page here and why the pairs the probe could not prove do not.
What survives from the MD into the MEDIAWIKI
Lists from the MD file, nesting included, plus code blocks, block quotes and links, all re-expressed in MEDIAWIKI.
Images: pandoc extracts them out of the MD file into a working directory and re-embeds them in the MEDIAWIKI, so nothing ends up pointing at a file that no longer exists.
What MD to MEDIAWIKI costs you
Tables. The MEDIAWIKI writer cannot carry one, and the probe caught this the hard way: a CSV file, which is nothing but a table, came back as a well formed and completely empty MEDIAWIKI with a zero return code. The engine now refuses that case outright rather than handing you the emptiness.
If a model is going to read the MEDIAWIKI
Structure is what survives from the MD file, and structure is what a model needs. MD in, MEDIAWIKI out, with the heading tree intact instead of flattened into one long paragraph.
MD to MEDIAWIKI, measured rather than promised
Running MD to MEDIAWIKI against the real engine with a real file, pandoc wrote 312 bytes of MEDIAWIKI in under a tenth of a second, machine otherwise idle. That is one MD file on one day and not an average, which is why the number is given together with the file that produced it.
The MD to MEDIAWIKI verdict was reached by a pandoc round trip, meaning the output was read back by pandoc and had to still contain a witness word planted in the source, which proves the content travelled and not merely the container. Which check was used matters, because they do not all prove the same thing, and a status code of 200 proves nothing whatsoever about whether the MEDIAWIKI file has anything inside it.
The same MD file, sent somewhere else
Other outputs the probe measured out of an MD file, so the cost of choosing MEDIAWIKI can be read against something. Sizes do not compare across engines, because each family was probed with its own MD witness file.
MD to PDF: 25,764 bytes in 1.9 seconds, verified by a format signature.
MD to DOCX: 10,106 bytes in 0.1 seconds, verified by a pandoc round trip.
MD to EPUB: 5,034 bytes in 0.1 seconds, verified by a pandoc round trip.
MD to TXT: 264 bytes in under a tenth of a second, verified by reading the text back.
MD to HTML: 4,018 bytes in 0.1 seconds, verified by a pandoc round trip.
MD to RTF: 687 bytes in under a tenth of a second, verified by a pandoc round trip.
What we will not pretend about MD to MEDIAWIKI
An MD file over 25 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
An MD to MEDIAWIKI run that passes 60 seconds is killed, and the pandoc process is killed with it. A run left behind would sit on one of the machine's two cores until somebody noticed.
32 of the 935 pairs probed in the family that serves MD to MEDIAWIKI failed, and this pair is not one of them. They fail for reasons worth knowing: a writer that cannot carry what the document is made of, or output the engine could not read back. They are counted here rather than hidden, because a pair that fails quietly is worse than one that fails loudly.
pandoc never writes the MEDIAWIKI through a TeX engine here, and it never writes PDF at all: the eleven engines it would need are not on this machine and a TeX distribution weighs several gigabytes. Anyone who wants a PDF out of an MD file goes through LibreOffice or calibre, both of which genuinely can.
One MD file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
MD to MEDIAWIKI: what people ask
What actually converts my MD file to MEDIAWIKI?
pandoc does it, in two passes, on a machine we rent and watch. Not a browser trick and not somebody else service: the MD file is uploaded once, pandoc runs once, the MEDIAWIKI comes back, and neither file is kept afterwards.
How long does MD to MEDIAWIKI take?
On the file the probe used, pandoc took under a tenth of a second and wrote 312 bytes of MEDIAWIKI. That is one real measurement on one real MD file, not an average and not a promise about yours: a larger MD takes longer, and past 60 seconds the run is stopped.
What do I lose going from MD to MEDIAWIKI?
The one to know about first: Tables. The MEDIAWIKI writer cannot carry one, and the probe caught this the hard way: a CSV file, which is nothing but a table, came back as a well formed and completely empty MEDIAWIKI with a zero return code. The engine now refuses that case outright rather than handing you the emptiness.
Are the tables in my MD file still tables in the MEDIAWIKI?
No, and that is a property of MEDIAWIKI rather than a defect of this path. MEDIAWIKI cannot hold a table, so an MD file built around one is the wrong candidate for this pair.
Is MD to MEDIAWIKI free?
There is a free allowance every month, and one MD to MEDIAWIKI conversion costs half a credit against it. When the allowance runs out the tool says so and stops, rather than quietly handing you a worse MEDIAWIKI.