Terraform Compare — Compare Terraform Files Online Free
Infrastructure as code means infrastructure as diffable text. Compare Terraform .tf files — resources, variables, and provider blocks highlighted before you plan. Free, no account.
How to Compare Terraform Files Online
To check two .tf files for differences in Terraform Compare:
- Add the original .tf file in the left editor.
- Then upload the updated .tf file in the changed pane.
- Click Compare and every difference is highlighted instantly.
Tip: read the config diff before terraform plan — knowing what changed in the .tf files tells you what the plan should show. Runs in any modern browser — Firefox, Edge, Safari, or Chrome — on Windows, Mac, Linux, and phones, and no usage limits apply. The default side-by-side mode is free — no login needed; the line-by-line and unified views come with Premium.
Understanding the Terraform File Format
Terraform (.tf) files declare cloud infrastructure in HCL — resources, modules, variables, and providers that Terraform reconciles against real infrastructure. Because applying a changed configuration creates, modifies, or destroys real resources, comparing .tf versions before plan and apply is a core infrastructure-as-code safety practice. Every block here maps to a real resource with a real bill, so Terraform file comparison is cloud-change review — the highlighted line is the firewall rule, instance size, or access policy about to change.
Common Uses of Terraform Files
Where teams actually use it, day to day:
- Platform engineers diff production and staging configs to verify parity claims.
- Reviewers read the config diff before terraform plan to predict the plan.
- Teams audit module-version bumps before applying them.
- Engineers compare state-file exports when drift is suspected.
- Security reviews IAM and firewall block changes before merge.
- SREs document infrastructure changes between release tags.
Diffing production's and staging's .tf files turns the claim that the environments match from a hope into a checked fact.
Differences Detected in Terraform Files
The tool highlights HCL structure precisely: Terraform resource diff for changed arguments and blocks, module version comparison (source and version pins), provider changes including version constraints, variable definition diff covering defaults and validation, and Terraform state comparison workflows for drift investigation.
Examples of Changes Found in Terraform Files
Infrastructure-code changes the block-level diff typically flags:
- An aws_instance where instance_type changed from t3.medium to t3.xlarge and a new ebs_block_device appeared — cost and capacity changes flagged before apply.
- A module pin bumped from version = "~> 3.0" to "~> 4.0" — a major-version adoption needing changelog review.
- A security group rule where cidr_blocks changed from a VPN range to 0.0.0.0/0 — a security-critical edit surfaced instantly.
- Prod vs staging variable files differing in six values, two of them unexpected.
- An aws_security_group where cidr_blocks = ["10.0.0.0/8"] became ["0.0.0.0/0"] — one rule opened to the world, flagged in review instead of in an audit.
Why Use FileDiffs for Terraform Comparison
Every block in a .tf file maps to real infrastructure with a real bill, so reading the config diff before terraform plan tells you what the plan should show, and what it shouldn't. FileDiffs compares Terraform configs in the browser. The page is built for cloud-change review rather than a generic diff, with examples like a security group's cidr_blocks widening from a private range to 0.0.0.0/0, one rule opening a resource to the entire internet, flagged in review instead of in a breach report.
Frequently Asked Questions About Compare Terraform Files Online
Upload both .tf files and the tool highlights every changed resource, argument, module, and variable side by side. Resource block highlights map to real infrastructure with real billing — review them like change requests, not text.
Compare the module source between versions; changed resources, inputs, and outputs are flagged — review them before bumping the version pin. Pin module versions and diff before bumping; an upstream module edit is an infrastructure change you didn't write.
Diff it against the previous version; resource-level highlights show exactly what infrastructure will be affected before you ever run terraform plan. Provider and variable highlights explain most plan surprises — read them before running terraform plan.
Save plan outputs (terraform show on each plan file) and diff the text — differences between planned changes across runs or branches become explicit. Diff the saved plan outputs of two runs to see how the same config resolves differently across workspaces.
Compare configurations between releases and keep the diff reports as change records; pair with plan output review for a complete pre-apply audit trail. Diffing production's and staging's configs turns the-environments-match from a hope into a checked fact.
Yes. Your .tf files are processed locally in the browser, so infrastructure definitions and provider settings never leave your device. Nothing is uploaded or retained afterward. You can verify this yourself in your browser's network tab.