Why convert GSTR-1 JSON to Excel
The return arrives as a single JSON file with nested arrays. You cannot foot it, filter it, or send it to a client in that shape — and opening it in Notepad tells you nothing. Excel is where accountants actually check a return: sort by GSTIN, sum the taxable value per rate, compare HSN quantities against the sales register.
One row per item, not per invoice
A single invoice can carry several tax rates — clothing is the classic case, 5% and 18% under one HSN. Aggregating an invoice into one row loses the rate split, which is exactly what you need during an audit. Every sheet here is item-level: the invoice fields repeat, each item gets its own row, and the rate stays visible.
The Summary is calculated, not copied
A GSTR-1 JSON carries no totals, so the tool computes them: records, taxable value and IGST/CGST/SGST/Cess for every section, plus a TOTAL line. Compare it against the return before you file anything downstream. If a section looks wrong, you can see which sheet it came from.
Where the file goes (nowhere)
Most online GSTR-1 converters upload the file to their own server. For a client's return that means supplier GSTINs, invoice registers and turnover leave your machine — a confidentiality problem you carry, not the website. This tool has no upload step: parsing, section splitting and the XLSX build all happen in the browser tab. You can even switch the network off after the page loads and it keeps working.
What it does not do
It does not generate the JSON that the portal accepts for filing — that file must come from the official GST Offline Tool, because the portal validates its own schema. Use the Excel to JSON for GSTR-1 page if your data is in a spreadsheet and your accounting system needs JSON; use this page when you already have the JSON and need it readable.