Is it safe to paste my real Terraform state here?

Yes — but consider the inputs first. Terraform state can contain secrets in resource attributes (database passwords, API keys) if the provider serializes them. The analyzer runs entirely in your browser and never sends the file to a server, but the same state should not be shared casually elsewhere. Read your state's sensitive fields before pasting if you are unsure.

What is the practical size limit for Terraform state?

Terraform can technically handle state files of arbitrary size, but performance degrades steeply past a few thousand resources. Plans slow from seconds to minutes, refresh becomes expensive, and remote state backends start hitting rate limits on the underlying object store. Most teams split state once they cross 1,000–2,000 resources per workspace.

Terraform State Analyzer

MonitoringMulti-Cloud

Paste a Terraform state file to analyze resource counts, provider breakdown, and potential issues.

Last verified: May 2026

Terraform State JSON

Raw Output

Output will appear here...

See It in Action

Plans for your production workspace have crept from 90 seconds to 8 minutes over six months and nobody knows why. You pull the state, paste it into the analyzer, and see 4,800 resources — 2,100 of them in a single module that turned out to be replicating per-customer IAM roles inside one workspace. Splitting that module into its own workspace cuts the main plan back to 2 minutes and lets the per-customer state run in parallel.

What This Tool Does

Terraform state files are the source of truth for what Terraform thinks your infrastructure looks like. They are also large JSON blobs that no one wants to read by hand. The Terraform State Analyzer parses a state file in-browser and surfaces a resource count by provider and resource type, flags suspicious patterns (duplicate names, orphaned modules, stale outputs), and estimates state size against known performance cliffs — all without uploading the file anywhere.

Technical Details

The analyzer parses the state file as JSON and walks the `resources` array, grouping by provider (the prefix before the first dot in `type`) and by resource type. It computes a histogram of resources-per-module, detects duplicate addresses, and reports the state's byte size alongside Terraform's documented performance characteristics for state-file size. No data is transmitted off your device.

Common Use Cases

1Before splitting a monolithic Terraform state into per-environment or per-domain states, getting a resource-by-provider breakdown to plan the split.
2Investigating why a `terraform plan` is suddenly taking 30+ minutes — large state files (5,000+ resources) often need refactoring or backend tuning.
3Auditing a state file for resources that should not be there: forgotten EC2 instances, orphaned NAT gateways, IAM roles from a long-dead module.
4Confirming a state migration completed successfully by comparing resource counts before and after.

Common Questions

Is it safe to paste my real Terraform state here?: Yes — but consider the inputs first. Terraform state can contain secrets in resource attributes (database passwords, API keys) if the provider serializes them. The analyzer runs entirely in your browser and never sends the file to a server, but the same state should not be shared casually elsewhere. Read your state's sensitive fields before pasting if you are unsure.
What is the practical size limit for Terraform state?: Terraform can technically handle state files of arbitrary size, but performance degrades steeply past a few thousand resources. Plans slow from seconds to minutes, refresh becomes expensive, and remote state backends start hitting rate limits on the underlying object store. Most teams split state once they cross 1,000–2,000 resources per workspace.

Expert Tips

TIP

Resources with no `depends_on` and very few attribute references are usually safe to extract into a separate workspace. The analyzer's per-module breakdown helps spot these candidates quickly.

TIP

If your state has resources from provider versions you no longer use (e.g., aws ~> 3.x entries in a state that should be aws ~> 5.x), Terraform will need a `state replace-provider` migration before the next plan succeeds. The provider-version count surfaces this.

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.