XLS to JSON Converter

How to convert spreadsheet data to JSON

A spreadsheet row can look correct in a sheet but fail in a system that expects named JSON fields. For example, a row with Name, Age, and City becomes one object with those three keys. XLS to JSON runs in your browser, so the conversion suits a single table that needs a structured JSON result.

1. You can paste the sheet. Copy cells or spreadsheet XML. The first row becomes headers when the option is selected.
2. You can check the JSON options. Array Format produces a list of row objects, which matches common API input.
3. You can review and copy the result. A quick check catches shifted columns before another system reads the data.

XLS workbook and JSON have different roles

What an XLS workbook contains

A spreadsheet workbook can contain formulas, styles, and multiple sheets, while a flat table contains values in rows and columns. For example, a workbook with several tabs must be reduced to the table you want to convert. This tool reads the selected table values because JSON represents records, not workbook layout.

What JSON contains

JSON, or JavaScript Object Notation, stores named values inside objects. For example, the headers Name and City can produce {"Name":"Ada","City":"London"}. An array of these objects keeps each spreadsheet row separate and gives the receiving system stable field names.

Sample spreadsheet and JSON

Name,Age,City
Ada,36,London
Lin,29,Taipei

[
  {"Name": "Ada", "Age": 36, "City": "London"},
  {"Name": "Lin", "Age": 29, "City": "Taipei"}
]

Common conversion problems

Will leading zeros disappear?

A value such as "00123" can lose its zeros when a spreadsheet treats it as a number. Keep the value quoted or format the source column as Text, because the converter preserves the value it receives.

Why is everything in one column?

The separator may be a semicolon or tab instead of a comma. Choose the matching Value Separator, because the parser uses that character to find each column.

What about UTF 8 and Windows 1252?

Text can look wrong when the source uses Windows 1252 and the pasted data uses a different encoding. Use UTF 8 when possible, because it preserves accented characters across current data tools.