Paste plan JSON or load a local file to examine proposed resource changes. This view reads the plan without running Terraform or applying infrastructure changes.
Runs locally in your browserThis is a read-only review. It never runs Terraform, loads providers, or contacts your cloud account.
Paste the document produced by terraform show -json plan.tfplan, or open the file from disk, and press Analyze plan. Every entry of resource_changes becomes a row: action, address, type, provider and the top-level attributes that differ between before and after.
The plan is parsed in this browser. Nothing is uploaded, no provider is downloaded and Terraform is never executed, so the review also works offline once the page has loaded.
The tool walks the resource_changes array. Each entry becomes one row: action, address, type, provider — the registry.terraform.io/ and registry.opentofu.org/ prefixes are dropped — and the changed field names. format_version and terraform_version are repeated in the copyable report.
Other parts of the same document are not displayed: resource_drift, output_changes, prior_state, planned_values and the configuration snapshot are ignored. A data source that is only re-read is shown as read; a resource that stays untouched is shown as no-op.
Actions are normalised to create, read, update, delete, replace and no-op, where a delete plus create pair counts as a replacement. Every category is counted in the summary, so the action numbers add up to the resource count.
Unknown values are the true leaves inside after_unknown; sensitive markers are the true leaves inside after_sensitive and before_sensitive, nested objects included. A marker means Terraform is not showing that value in the plan — the tool does not mask the JSON you paste, so treat the input itself as confidential.
The changed-field column lists top-level attribute names only: a change inside tags appears as tags, not as each tag. Eight names are shown and the cell states how many are hidden, so a wide diff never looks complete when it is not.
A 2,000-resource plan is analysed in roughly 0.3 s in a desktop browser and every resource is listed. The tool reports only what the plan contains: it does not fetch configuration, does not consult provider schemas and cannot tell whether the plan will apply without errors.