Tablizer

Convert MediaWiki to JSON Online

Paste a MediaWiki table below, edit it if you need to, and get JSON back. The conversion runs in your browser, so nothing is uploaded, there is no size limit and there is no signup.

From

The only part of this site that uses a server. The address is sent to it so the page can be fetched, because a browser is not allowed to fetch someone else's page itself. Your own files are never involved.

Nothing here is uploaded. The parsing happens on this page.
Edit
Paste or upload something above and it will appear here.
ToDataMarkupDocumentsCodeSchemasImages

The output will appear here once there is a table to convert.

What MediaWiki is

MediaWiki table markup opens with {| and a class, marks headers with an exclamation mark and rows with |-.

Wikipedia editors and anyone running a MediaWiki install.

What JSON is

JSON is a text format for nested data: objects with named keys, arrays, strings, numbers, booleans and null. It has no date type and no comments.

Every web API, most configuration files and anything that talks to JavaScript.

What changes when you convert MediaWiki to JSON

Both cell styles are read: one cell per line, and several on a line separated by exclamation marks or double pipes, which is the form most Wikipedia tables use. Cell attributes before a single pipe are dropped, since style="text-align:right" is presentation rather than data. Wiki links come through as their display text, so [[France|the French Republic]] arrives as the French Republic, and reference markers are removed.

You choose the shape. An array of objects is the default and the one most code expects. A 2D array is smaller. Column arrays suit charting libraries. A keyed object suits lookups by id.

What carries over from MediaWiki to JSON

MediaWiki records 2 things about a table that JSON has no way to hold.

JSON wants a type for each column, and MediaWiki does not record one, so each column is typed from what its values look like. A column of digits that should stay text - a zip code, a phone number, a leading-zero id - is the usual thing to check afterwards.

JSON has no header row. The column names are repeated as keys on every record instead, which is why the result is bigger on disk than the table it came from.

Anything visual in the MediaWiki - weight, alignment, colour, column widths - has no counterpart in JSON and is dropped. The values are what survives.

The identifier 007 comes out of the JSON as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.

The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a JSON file goes wrong.

The quotes around Jonah "Jo" Pryce are escaped with a backslash in the JSON.

A worked example

Three rows of staff data, with an identifier that has a leading zero, a value containing a comma, a value containing quotes and one blank cell. Those are the four places formats disagree, so they are the four places to look.

MediaWiki in
{| class="wikitable"
|-
! id !! name !! role !! started !! hours
|-
| 007 || Halima Yusuf || Analyst, data || 2024-03-15 || 38.5
|-
| 012 || Jonah "Jo" Pryce || Engineer || 2025-11-02 ||
|-
| 104 || Wei Chen || Manager || 2023-06-30 || 40
|}
JSON out
{
  "staff": [
    {
      "id": "007",
      "name": "Halima Yusuf",
      "role": "Analyst, data",
      "started": "2024-03-15",
      "hours": "38.5"
    },
    {
      "id": "012",
      "name": "Jonah \"Jo\" Pryce",
      "role": "Engineer",
      "started": "2025-11-02",
      "hours": ""
    },
    {
      "id": "104",
      "name": "Wei Chen",
      "role": "Manager",
      "started": "2023-06-30",
      "hours": "40"
    }
  ]
}

Questions

How do I convert MediaWiki to JSON?

Paste your MediaWiki into the box above or drop the file onto it. Check the table in the grid, then copy or download the JSON from the output panel. It takes one step and the data never leaves your browser.

Why did my zip code lose its leading zero?

Type inference turned the text 07030 into the number 7030. Tablizer leaves inference off by default for exactly this reason, and refuses to convert any value starting with a zero followed by a digit even when it is on.

Is there a limit on file size?

No. The work happens on your own machine, so the limit is your machine's memory rather than an upload cap. A file with tens of thousands of rows converts in a second or two.

Is my data uploaded anywhere?

No. The parsing and generating are done by JavaScript running on this page. You can watch the network tab while you convert and see that nothing is sent.

Related conversions