Format, prettify, and minify Azure Resource Manager (ARM) template JSON.
Last verified: May 2026
Output will appear here...The formatter parses the input as JSON, then re-serializes it with configurable indentation (2 spaces, 4 spaces, or tabs) and a stable key order that matches Azure's documentation conventions: $schema first, then contentVersion, parameters, variables, resources, outputs. Minify mode strips all whitespace using a compact JSON.stringify call.
The ARM JSON Formatter lets you format, prettify, and minify Azure Resource Manager template JSON directly in your browser. ARM templates can grow to hundreds or thousands of lines, and consistent formatting is essential for readability and code reviews. This tool auto-detects common ARM template structures and applies proper indentation, making nested resources, parameters, and outputs easy to scan. You can also minify templates for compact storage or inline use in deployment scripts.
Your team exported a complex ARM template from the Azure portal for a 30-resource deployment. The export is one giant single-line JSON blob that's impossible to review. You paste it into the formatter, get readable indented output, and immediately spot two resources missing dependsOn references that would cause race conditions on first deploy. You add the missing dependencies before committing — saving the team a Monday-morning incident.
ARM templates are valid JSON, so any JSON formatter works — but ARM-specific structure (resources array, dependsOn references, parameter/variable expressions) is best preserved by formatters that understand the schema. The output of `az group export` in particular is notoriously hard to read without proper formatting.
When committing ARM templates to git, decide on tabs vs spaces and stick with it project-wide. Mixed indentation makes diffs noisy and triggers unnecessary merge conflicts. Most Azure docs use 2-space indentation; match that for consistency with examples.
Minified ARM templates can be embedded in PowerShell or Bash scripts via heredoc, but you lose readability. Better practice: keep templates as separate .json files and reference them via parameter files at deploy time. Templates aren't the place to optimize file size.
This tool focuses on JSON formatting and syntax. For structural validation and best-practice checks, use the ARM Template Linter tool which analyzes your template for missing fields, deprecated API versions, and common issues.
No. All formatting happens entirely in your browser using client-side JavaScript. Your template content never leaves your machine.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.