Free tools Windows power users keep installed
One-click scans. No signup required.
For a repeatable conversion you can clean and refresh, use Excel Power Query: choose Data > Get Data > From File > From JSON, inspect the result, expand any nested records or lists you need, then load it to a worksheet. For a one-off conversion without setting up a query, an online converter such as Aspose can accept an uploaded JSON file and return a spreadsheet. The right choice depends on where the JSON is coming from, whether it is nested, and whether you are comfortable uploading it to a third party.
These are ten approaches, not ten interchangeable upload websites: they range from Excel’s built-in import tools to browser conversion, APIs, and desktop automation. Excel’s exact features and labels can vary by edition, Microsoft 365 plan, platform, and tenant, so check availability in your installation.
Choose the right JSON-to-Excel method
| What you need | Best starting point | Why |
|---|---|---|
| Import a local JSON file and inspect or transform it | Excel Power Query: From File > From JSON | It lets you review and shape the data before loading it. |
| Turn JSON text already in a worksheet into columns | Power Query Parse > JSON | It parses each text value into a structured record that you can expand. |
| Import an API response or JSON URL | Power Query From Web | It can connect to a web endpoint, subject to its authentication and response behavior. |
| Convert one file in a browser | A browser converter such as Aspose | It avoids configuring Excel, but requires uploading the file to the service. |
| Repeat conversions in code or a workflow | Aspose.Cells Cloud API, .NET, or Power Automate Desktop | These routes suit recurring jobs better than repeated manual uploads. |
Before choosing, check the input form (file, text, URL, or API), the shape of the JSON, the desired output (XLS or XLSX, one or several sheets), repeatability, privacy, and whether the source requires credentials.
1. Import a JSON file with Excel Power Query
For a local file, Excel’s documented route is Data > Get Data > From File > From JSON. Power Query opens the data for inspection and transformation; it does not require you to paste the entire file into a worksheet first.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute#1 Best Overall
- Open the workbook and select Data > Get Data > From File > From JSON.
- Choose the JSON file and open it. Power Query displays the detected structure.
- Inspect the preview. If the result contains a Record or List rather than the columns you want, select or expand the relevant values.
- Apply any needed transformations, such as choosing fields, expanding nested data, or removing columns.
- Choose Close & Load to place the result in Excel.
Microsoft documents the file-import path; its Power Query JSON connector uses automatic table detection to flatten JSON into a table. That detection is a useful starting point, not a guarantee that every data shape will become the final table you want. A flat array of similar objects is usually easier to use than records containing arrays, inconsistent fields, or several levels of nesting.
What happens to nested objects and arrays?
A JSON object embedded in a record may appear as a structured value that you can expand to select its fields. A list or array may need to be expanded or transformed separately. Decide what one spreadsheet row should represent before expanding: one row per parent object, one row per child item, or a combined row with repeated parent values. Expanding a list can create multiple rows for one parent record; that may be correct, but it changes the relationship between source records and worksheet rows.
For example, an order record with a customer object and an array of line items has at least two reasonable layouts: one row per order, or one row per line item with order details repeated. Choose deliberately rather than treating a visually wide table as automatically correct.
2. Use the Power Query JSON connector and expand records
The JSON connector is the engine behind file import and other Power Query workflows. Its automatic table detection can flatten data, after which you can refine the result by expanding only the fields relevant to your spreadsheet. This is useful when the source has nested records and you want a controlled set of columns instead of accepting every detected field.
Recommended Free Tools
- Open the JSON source in Power Query through the appropriate connector.
- Review the detected structure and identify fields represented as Record or List values.
- Expand a Record and select the fields that belong in the table.
- For a List, decide whether its items should become rows or whether a different transformation is needed.
- Check the resulting column names, data types, and row count before loading.
Do not assume that flattening preserves every relationship in a useful way. If the JSON contains several arrays, expanding more than one can multiply rows or make the resulting table difficult to interpret. In those cases, separate related data into different queries or sheets rather than forcing all levels into one worksheet.
3. Parse JSON stored as text in a worksheet
If a worksheet column already contains JSON strings, use Power Query’s Transform > Parse > JSON workflow. Parsing turns a text value into a structured Record that you can inspect and expand. This is different from importing a JSON file: the input is already in a table column.
- Load the worksheet data into Power Query.
- Select the column containing JSON text.
- Choose Transform > Parse > JSON.
- Inspect the resulting Record values and expand the fields you need.
- Load the transformed table back into Excel.
This route is useful for exported logs or API responses that have been collected as text in a column. Each row needs to contain valid JSON for parsing. If some values are malformed or use a different structure, identify and handle those rows rather than assuming the entire column can be expanded uniformly.
4. Connect to a JSON URL or API with From Web
When JSON is available at a URL, Power Query’s From Web connector can retrieve it without a separate manual download. This includes API endpoints, but the connection depends on the endpoint’s behavior and authentication requirements.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Choose the Power Query web connector in Excel and enter the JSON URL or API endpoint.
- When prompted, select the credential type appropriate for that endpoint, if required.
- Inspect the response in Power Query and expand records or lists as needed.
- Load the finished query to Excel, then test a refresh if you need the data to stay current.
A URL that works in a browser may still require credentials, headers, or a particular request method that the connector cannot supply in your setup. Endpoints can also return an error page, a login response, or JSON whose structure changes between requests. Confirm that Power Query received the expected JSON before treating a failed or unusual import as a conversion problem.
5. Use Power Query Online or Excel for the web
Power Query Online can use a JSON data source where the needed credentials and, for on-premises sources, an on-premises data gateway are available. Microsoft also documents JSON among Power Query data sources for supported Microsoft 365 web plans. Availability is plan- and tenant-dependent; check your organization’s current service and connector access rather than assuming the same options appear in every browser session.
These are useful choices when the data and workbook already belong to an online Microsoft workflow. They are not a universal browser-based replacement for desktop Excel: access to a connector, gateway configuration, and authentication can determine whether the query can run.
6. Automate workbook creation with Power Automate Desktop
Power Automate Desktop is an automation route rather than a simple file-upload converter. A Microsoft tutorial demonstrates extracting JSON keys, looping through records, writing rows to Excel, and saving a workbook. It makes sense when JSON conversion is one step in a larger desktop process—for example, processing a file as part of a repeatable sequence—not when you simply need to convert one file quickly.
Rank #3
Because automation depends on the current application interface, installed software, and flow configuration, treat the tutorial as a pattern to adapt and verify in your environment. Check that loops handle empty or differently shaped records and that the workbook is saved where the next step expects it.
7. Convert a file online with Aspose
A browser converter is the most direct option when you have a one-off file and do not want to build a Power Query transformation. Aspose’s JSON-to-Excel workflow is to upload the JSON, set a table style if wanted, select Convert, then download the resulting file. The service states that uploaded files are deleted from its servers after 24 hours; that is a vendor-stated retention policy, not a substitute for checking the current terms or your own data-handling requirements.
- Open the Aspose JSON to Excel converter.
- Upload the JSON file and choose any available table or output options.
- Convert, then download and open the workbook.
- Inspect the output for missing fields, nested values, row expansion, and the intended XLSX layout.
Use this approach only if uploading the file is acceptable. For confidential, regulated, or otherwise sensitive data, prefer an approved local workflow unless your organization has reviewed the service and its terms.
8. Use Aspose.Cells Cloud API for recurring conversions
A cloud API is a better fit than repeated browser uploads when a program needs to import JSON into a workbook and save a result at a specified location. Aspose.Cells Cloud documents JSON import into a workbook and REST/API parameters including worksheet position and output path. Consult the Aspose.Cells Cloud JSON import documentation for the current request details and authentication requirements; the exact call depends on the service configuration.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Before putting a cloud conversion into a production pipeline, decide where source and output files are stored, how credentials are protected, what happens when the source schema changes, and how failed jobs are surfaced. An API makes the process repeatable, but does not remove the need to validate the workbook’s structure.
9. Convert JSON with Aspose.Cells for .NET
For a .NET application, Aspose.Cells documents loading JSON into a workbook and saving it as XLSX. Its example uses Workbook wb = new Workbook("sample.json"); followed by wb.Save("sample_out.xlsx");. The documented options include MultipleWorksheets and ArrayAsTable, which can affect how data is arranged in the workbook. See the Aspose.Cells for .NET reference for the relevant current API details.
Options that place arrays into tables or split content across worksheets can be useful when the source contains several logical collections. Review the generated sheets and columns against the source: a successful save only establishes that a workbook was written, not that its layout matches your intended analysis.
10. Export an API response through a repeatable pipeline
For recurring API-to-Excel work, treat retrieval, transformation, and workbook output as separate stages. Power Query’s web connector is the lowest-code option when the endpoint and authentication are supported in your Excel setup. A cloud API or .NET library is more appropriate when conversion belongs inside an application or scheduled process. Power Automate Desktop can coordinate desktop tasks, but is less suited to unattended server-side processing.
- Confirm the response is valid JSON and identify whether it is a single object, an array, or nested data.
- Define how each source object maps to worksheet rows and columns.
- Decide how to handle missing fields, new fields, empty arrays, and malformed records.
- Use credentials through the method supported by the chosen connector or service; do not place secrets in a workbook shared broadly.
- Validate the output workbook after a schema change or failed refresh.
JSON Lines (one JSON value per line) is not necessarily the same input shape as one JSON document containing an array. If a tool does not accept the file as supplied, verify its expected format before changing the data.
How to decide whether the result is correct
- Rows: compare the number and meaning of rows with the source objects. Expanding a list may intentionally create several rows per parent object.
- Fields: check that the fields needed for the task appear and that nested values have not been silently left as records or lists.
- Types: verify dates, numbers, identifiers, and values with leading zeroes. Automatic type detection may not reflect how you intend to use a value.
- Workbook format: confirm whether you need XLSX, an older XLS format, one sheet, or several sheets. Do not infer the output format solely from a file name.
- Refresh: for a query or API connection, refresh after loading and confirm that credentials and endpoint access still work.
Privacy, reliability, and cost considerations
Excel Power Query processes data within your Excel workflow, while a browser converter requires sending the file to a vendor. For Aspose’s browser converter, the vendor states uploaded files are deleted after 24 hours; review its current terms and decide whether that retention window meets your requirements. For a cloud API, assess where data is sent and stored under the service’s terms before using real records.
For one file, a browser converter can save setup time. For repeated conversions, a refreshable query or API-based workflow avoids manually repeating the upload and download. No conversion route can guarantee a useful single table for arbitrary nested JSON: planning the row structure and checking the output are part of the job. The sources cited here do not establish comparable conversion speeds, file-size limits, or accuracy rates, so those should not be assumed.
Or skip the browser setup
ScreenshotNeo is a website screenshot API, not a JSON-to-Excel converter. If your task also needs a clean screenshot of a public API page or other web page, one GET request can return an image or PDF. Its capture options remove cookie/consent banners, newsletter popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are not billed. It also offers an MCP server for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
This captures a screenshot; it does not parse JSON or create an Excel workbook. For JSON-to-Excel conversion, use one of the data workflows above. Sign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Common problems and fixes
The JSON imports as a Record or List, not a table
That is a structure to expand, not necessarily an error. Expand the relevant Record fields; for a List, decide whether its items should become rows or be handled separately. If several arrays are involved, avoid expanding them blindly because the resulting row count can multiply.
Some rows fail to parse
Check whether every text value is valid JSON and whether the outlier uses a different structure. A column with mixed shapes may need conditional handling or a separate query for the exceptional records.
An API URL returns an error, login page, or unexpected data
Verify the endpoint, authentication choice, and response content in Power Query. A browser-accessible URL can still require credentials or behavior that the connector does not support in your configuration.
The Excel menu item is missing
Power Query features differ by Excel edition, platform, Microsoft 365 plan, and tenant. Check your installed version and available connectors; use a supported desktop or online environment, or choose another method available to you.
The workbook opens but columns or rows look wrong
Revisit how nested records and arrays were expanded, then compare the output with the source structure. Confirm the intended row granularity, field selection, data types, and sheet layout before relying on the workbook.
The online converter is unsuitable for the file
Do not upload data if its sensitivity or your organization’s policy makes third-party processing unacceptable. Use a local Power Query workflow where possible, or an approved, reviewed API or library route.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesFrequently Asked Questions
Can I convert JSON Lines directly to Excel?
JSON Lines stores separate JSON values on separate lines rather than necessarily forming one JSON document. Support depends on the importer; confirm the expected input format or transform the file into the format the selected tool accepts.
Will converting JSON preserve every nested relationship?
Not automatically in a single flat worksheet. Choose how arrays map to rows and how nested records map to columns, then verify the resulting structure against the source.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
