JSON Formatter
JSON is how almost everything in the Power Platform talks to everything else. An HTTP action returns it, Parse JSON expects it, a custom connector sends it and a Power Apps collection can be turned into it. When that JSON arrives as one long unreadable line, finding a single value is slow work. This free online JSON formatter for Power Automate and Power Apps turns the mess into clean, indented text, and tells you exactly where the syntax breaks if something is wrong.
Also known as: free online json formatter for power automate, json formatter for power apps, json beautifier, json pretty print, format json online.
Your data is processed locally in your browser and is not uploaded to our servers.
Features
- Clean, indented output in one click
- Line and column for the first syntax error
- Minify and Validate buttons on the same page
- Open a .json file, then copy or download the result
- Runs in your browser, nothing is uploaded
How to use the JSON Formatter
- Copy the JSON. In Power Automate, open a flow run, expand the action and copy its Outputs or Body. In Power Apps, copy the text returned by the JSON() function.
- Paste it into the input box, or click Open file to load a .json file from your computer.
- Click Format JSON. Use Minify to compress the text instead, or Validate if you only want to know whether the syntax is correct.
- If an error appears, read the line and column. Typical causes are a trailing comma, single quotes instead of double quotes, or a missing bracket.
- Copy the result, or download it as a file.
Real-world use case: debugging an HTTP action in Power Automate
Imagine a flow that calls a REST API every morning to fetch open tickets, then creates a Planner task for each one. One day the run fails on the Parse JSON action with a message that the schema does not match. The run history shows the HTTP action's body as one dense block of text, so you cannot see what changed.
Copy that body, paste it here and click Format JSON. Now the structure is visible. Maybe the API returns the list under value, one record has assignee set to null instead of an object, or a number now arrives as text. Once you see the shape, you can fix the Parse JSON schema or write the right expression, for example first(body('Parse_JSON')?['value'])?['assignee']?['email']. The question mark operators stop the flow from failing when a property is missing.
The same habit helps in Power Apps. The JSON() function turns a collection into text, and ParseJSON() reads JSON text from a flow or an API into an untyped object. Because the result is untyped, you convert each value yourself, for example Text(ParseJSON(varResponse).customer.name) or Value(...) for numbers. Formatting the response first shows you the exact property names and which fields are numbers, so you do not have to guess.
A few habits that save time: keep a sample payload from a successful run so you can compare it with a failed one, minify JSON before you paste it into a Compose action, and validate any JSON you edited by hand before you save it.
Example input and output
Input: one-line JSON from an HTTP action
{"value":[{"id":101,"title":"Pump check","status":"Open","assignee":{"name":"Sara","email":"sara@contoso.com"}}],"count":1}Output after clicking Format JSON
{
"value": [
{
"id": 101,
"title": "Pump check",
"status": "Open",
"assignee": {
"name": "Sara",
"email": "sara@contoso.com"
}
}
],
"count": 1
}Expression you can now write in Power Automate
first(body('Parse_JSON')?['value'])?['assignee']?['email']
// returns sara@contoso.comFrequently asked questions
How do I format JSON in Power Automate?
Copy the JSON from the action's outputs in the run history, paste it into a JSON formatter and click Format. The formatted text shows every property and nesting level, which makes it easy to build the schema for Parse JSON or an expression with body() and the ?[] operator.
Why does the Parse JSON action fail?
Most often the data no longer matches the schema. A property is missing, a value is null where the schema expects text, or a number arrives as a string. Format the real response, compare it with your schema, then regenerate the schema with Use sample payload to generate schema.
Is it safe to paste API responses into this formatter?
Formatting happens in your browser and the text is not uploaded to our servers. Even so, avoid pasting secrets such as passwords or live access tokens into any website.
Why use PowerApps Ninja?
Some online formatters process your text on their servers. PowerApps Ninja does all the work in your browser, so API responses, customer records and tokens from your flows stay on your device. There is no sign-up, and the page explains the Power Platform side of the job, such as Parse JSON and ParseJSON, which general formatters leave out.