Are heredocs supported?

Yes. Heredoc strings (<<EOF...EOF) are converted to regular JSON strings with embedded newlines.

HCL to JSON Converter - Terraform Config Parser

Convert HashiCorp Configuration Language to JSON. Parse Terraform, Vault, Consul configs. No internet needed, 100% local.

Drop HCL/Terraform file here or click to browse

.tf, .hcl, .tfvars files

HCL Input

JSON Output

Cron Expression Parser - Validate Schedu…

REG to JSON - Windows Registry Parser

Apache .htaccess to Nginx Converter - Se…

Nginx Config to JSON - Parse Configurati…

COBOL Copybook Parser - Data Layout Anal…

View all Config parsers →

Frequently Asked Questions

HCL (HashiCorp Configuration Language) is used by Terraform, Vault, Consul, Nomad, and other HashiCorp tools. It's designed to be both human-readable and machine-parseable.

JSON is easier to process programmatically, works with more tools, and can be validated with JSON Schema. Useful for CI/CD pipelines and infrastructure analysis.

Blocks, attributes, strings, numbers, booleans, lists, maps, and heredocs. Comments are stripped. Variable interpolation syntax is preserved as strings.

Yes. Terraform .tf files use HCL syntax. Resource blocks, variables, outputs, and other Terraform constructs are converted to JSON objects.

Yes. All processing happens locally in your browser. Your infrastructure code never leaves your device, ensuring complete privacy.

HCL blocks become nested objects. Block labels become keys. Multiple blocks of the same type become arrays of objects.

Expressions like ${var.name} or local.value are preserved as literal strings. The converter doesn't evaluate expressions.

Yes. Heredoc strings (<

Not with this tool. JSON to HCL conversion requires understanding block structure semantics. Use terraform fmt for that.

The JSON mirrors the HCL structure. Root blocks become top-level objects. Nested blocks become nested objects. It's a direct structural translation.

Related Tools