Convert AWS CloudFormation to Terraform Online Free

Transform AWS CloudFormation JSON/YAML templates into Terraform HCL configuration instantly in your browser. No server upload, no signup, no limits.

By ChangeThisFile Team · Last updated: March 2026

Quick Answer

ChangeThisFile converts your AWS CloudFormation templates to Terraform HCL configuration directly in your browser. Terraform's multi-cloud support and declarative syntax provide better vendor neutrality and infrastructure portability. Your infrastructure code stays on your device for complete privacy. Free, instant, no signup.

Free No signup required Files stay on your device Instant conversion Updated March 2026

Convert CloudFormation to Terraform

Drop your CloudFormation file here to convert it instantly

Drag & drop your .cloudformation file here, or click to browse

Convert to Terraform instantly

CloudFormation vs Terraform: Format Comparison

Key differences between the two formats

FeatureCloudFormationTerraform
Cloud provider supportAWS onlyMulti-cloud (AWS, Azure, GCP, 3000+ providers)
Configuration formatJSON or YAML templatesHCL (HashiCorp Configuration Language)
State managementManaged by AWS CloudFormation serviceLocal or remote state files (S3, Consul, etc.)
Resource lifecycleStack-based deployment and updatesResource-based planning and application
ModularityNested stacks and transformsModules with versioning and registries
Planning and previewChange sets (limited preview)terraform plan (detailed diff and impact analysis)
Community ecosystemAWS-specific resources and examplesLarge multi-cloud community and module library
Learning curveEasier for AWS-only infrastructureSteeper initially, but more transferable skills

When to Convert

Common scenarios where this conversion is useful

Multi-cloud infrastructure migration

Move from AWS-only CloudFormation to Terraform for deploying the same infrastructure patterns across AWS, Azure, and Google Cloud Platform.

Vendor lock-in reduction

Convert CloudFormation templates to Terraform to reduce dependency on AWS-specific tooling and enable infrastructure portability.

Advanced infrastructure automation

Leverage Terraform's superior planning, state management, and module ecosystem for complex infrastructure deployments and GitOps workflows.

Team standardization on Terraform

Migrate existing CloudFormation infrastructure to Terraform when standardizing infrastructure-as-code tooling across development teams.

Who Uses This Conversion

Tailored guidance for different workflows

DevOps Engineers

  • Migrate existing AWS CloudFormation infrastructure to Terraform for multi-cloud deployment capabilities
  • Convert CloudFormation templates to Terraform when standardizing on HashiCorp tooling across the organization
Use terraform import to map existing AWS resources to the converted Terraform configuration before applying changes
Review the converted HCL for best practices like proper resource naming, variable usage, and module structure

Cloud Architects

  • Convert AWS-specific CloudFormation templates to Terraform for vendor-neutral infrastructure designs
  • Transform CloudFormation stacks to Terraform modules for better reusability across projects and environments
Plan the state management strategy (remote state, workspaces) before importing converted infrastructure
Consider breaking large CloudFormation stacks into smaller Terraform modules for better maintainability

Platform Engineers

  • Convert CloudFormation infrastructure to Terraform when building internal developer platforms with multi-cloud support
  • Migrate CloudFormation-based CI/CD pipelines to Terraform for consistent infrastructure deployment across environments
Test the converted Terraform configuration in a development environment before applying to production infrastructure
Document any manual changes needed after conversion for future template migrations

How to Convert CloudFormation to Terraform

  1. 1

    Upload your CloudFormation template

    Drag and drop your .json or .yaml CloudFormation template onto the converter, or click to browse your files. Both template formats are supported.

  2. 2

    Automatic HCL conversion

    Your CloudFormation resources, parameters, and outputs are parsed and converted to Terraform HCL syntax instantly in your browser. No data is sent to any server.

  3. 3

    Download the Terraform configuration

    Click Download to save your converted .tf file. The output uses standard HCL formatting and Terraform best practices for resource naming.

Frequently Asked Questions

The converter handles most common CloudFormation resources, parameters, and outputs. However, some AWS-specific intrinsic functions and advanced features may require manual adjustment in the resulting Terraform configuration.

Common functions like Ref, GetAtt, and Join are converted to Terraform interpolation syntax. Complex functions like Transform or Condition may need manual conversion after the initial automated conversion.

Yes. CloudFormation Parameters are converted to Terraform variables with appropriate types and default values. You may need to adjust variable descriptions and validation rules manually.

No. The entire conversion happens in your browser using JavaScript. Your CloudFormation templates never leave your device, making it safe for sensitive infrastructure configurations.

The converter handles individual CloudFormation templates. Nested stacks should be converted separately and then restructured using Terraform modules for similar organizational benefits.

CloudFormation Outputs are converted to Terraform output blocks with appropriate value references. Cross-stack references may need adjustment to use Terraform remote state data sources.

Yes. The converter adds appropriate AWS provider configuration blocks. You may need to adjust provider versions, regions, and authentication settings for your specific deployment requirements.

Basic conditions are converted to Terraform count or for_each expressions where possible. Complex conditional logic may require manual refactoring using Terraform's conditional expressions.

Custom resources (AWS::CloudFormation::CustomResource) are noted in the output but require manual conversion to equivalent Terraform resources or external data sources.

After conversion, run 'terraform init', then 'terraform plan' to review the proposed infrastructure changes. Import existing AWS resources using 'terraform import' to avoid recreating infrastructure.

SAM transforms and other CloudFormation transforms are not automatically converted. You'll need to manually convert SAM resources to equivalent Terraform resources or use Terraform's serverless modules.

Yes, completely free with no limits on template size or number of conversions. No account required.

Related Conversions

Related Tools

Free tools to edit, optimize, and manage your files.

Need to convert programmatically?

Use the ChangeThisFile API to convert CloudFormation to Terraform in your app. No rate limits, up to 500MB files, simple REST endpoint.

View API Docs
Read our guides on file formats and conversion

Ready to convert your file?

Convert CloudFormation to Terraform instantly — free, no signup required.

Start Converting