Tablizer

Convert IIF to JSON Online

Paste an IIF 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 IIF is

IIF is QuickBooks Desktop's import and export format: tab-separated, with several tables interleaved in one file. A line starting with an exclamation mark defines the columns for a record type, and the data lines that follow begin with that type's keyword.

QuickBooks Desktop users, and the bookkeepers who have to move data into and out of it.

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 IIF to JSON

The largest table in the file is used, which is almost always the transactions. A typical export holds TRNS rows for the transactions and SPL rows for their split lines; those are two tables, not one, and combining them would produce a column layout that fits neither.

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 IIF to JSON

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

JSON wants a type for each column, and IIF 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.

IIF can be read one record at a time. JSON has to be complete before it means anything, so the whole table is held in memory while it is written and a file that gets cut off part way through is not partly usable - it is unusable.

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.

IIF in
!TRNS	TRNSTYPE	DATE	ACCNT	NAME	AMOUNT	MEMO
!SPL	TRNSTYPE	DATE	ACCNT	NAME	AMOUNT	MEMO
!ENDTRNS
TRNS	CHECK	01/15/2026	Checking	Greenfield Grocers	-42.50	Weekly shop
SPL	CHECK	01/15/2026	Groceries	Greenfield Grocers	42.50	Weekly shop
ENDTRNS
TRNS	DEPOSIT	01/16/2026	Checking	Acme Ltd	1850.00	January salary
SPL	DEPOSIT	01/16/2026	Salary	Acme Ltd	-1850.00	January salary
ENDTRNS
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 IIF to JSON?

Paste your IIF 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 does my IIF file have two sets of headers?

Because it holds two tables. TRNS lines are transactions and SPL lines are the splits belonging to them, and each has its own column definition. They are separate exports that happen to share a file.

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