Cloud architecture diagrams
Services drawn with official provider icons, nested inside cloud, region, VPC, availability zone and subnet boxes worked out from your references.
Terraform → architecture diagram
TF Diagrams turns .tf files into interactive cloud architecture diagrams and dependency graphs. Everything runs in your browser; your code never leaves your machine.
Free · No sign-up · Nothing uploaded
Product tour
Real screenshots from the app, using the sample projects it ships with. No mock-ups.
Built for reviewing infrastructure, onboarding to a new codebase and explaining a stack to your team.
Services drawn with official provider icons, nested inside cloud, region, VPC, availability zone and subnet boxes worked out from your references.
Every resource, data source, module, variable, local, output and provider, laid out from inputs to outputs.
Open any file with syntax highlighting. A node’s file and line jump straight to the block that defines it.
Select a node to highlight everything it depends on and everything that uses it, with its source and clickable references.
Narrow the graph by block kind and group it by file to focus on the part you care about.
One engine for all three providers, with the details each one does differently handled separately.
Drop a folder, open files or paste code.
Switch between the cloud diagram and the dependency graph, filter and group.
Save the graph as a PNG for docs, pull requests or slides.
No. Files are read and parsed by your browser, and the diagram is drawn on your device. Nothing is sent to a TF Diagrams server.
Yes. There’s no sign-up, no paid tier and no usage limit. If it helps you, you can buy me a coffee.
AWS, Google Cloud and Azure. AWS and Google Cloud services use their official icons; Azure services are drawn as labelled tiles.
No. It reads your .tf files directly, so it needs no Terraform install, state file or credentials.
Expressions aren’t evaluated, so count and for_each aren’t expanded and module internals aren’t followed. Supporting resources such as security groups and route tables are left out of the cloud diagram on purpose; they still appear in the dependency graph.
Parsing and layout happen entirely client-side. Your files are read by your browser and never sent to a server.
Visualize your Terraform