Auto-generated subnet trees, VPC topology and IP heatmaps. Export to PNG, SVG, Mermaid or draw.io.
The visualizer is for understanding subnet layouts at a glance — and for sharing them with people who don't think in CIDR notation. The same VPC and subnet inputs render five different ways depending on what you want to communicate:
Use the tree view when explaining subnet containment to someone new to CIDR. The VPC topology view is what you want for architecture reviews and runbooks. Bitmap is the right pick when teaching subnetting fundamentals — it makes prefix length concrete. The heatmap is for IPAM audits, paired with the IPAM tool to see which subnets are near capacity. Mermaid is for documentation that lives in version control alongside code.
If you spotted a problem in the visualization — overlapping subnets, mis-sized blocks — fix it with the main calculator for single networks or the VLSM planner for multi-size designs.
For when overlapping CIDRs show up in production and how to find them, see troubleshooting overlapping CIDRs.
Use a tree view when explaining subnet containment to someone learning CIDR — it shows how subnets nest inside a parent block. Use a VPC topology diagram for architecture documentation and runbooks — it shows public and private subnets across availability zones in the layout your cloud provider actually uses.
The heatmap renders subnet utilization, with brighter cells indicating subnets that are more densely allocated. It is most useful for IPAM audits — paired with the IPAM tool, the heatmap surfaces subnets approaching capacity before they become a problem.
Yes. Tree and VPC views export as SVG or PNG. The Mermaid view exports as Mermaid text, which renders in any documentation platform that supports Mermaid (GitHub, GitLab, Notion, Confluence, plain markdown viewers). The bitmap and heatmap views export as PNG.