3D code visualization: walk through a codebase as a city
A file tree tells you where code is; it never tells you what matters. RepoVerse renders a repository as a 3D city in the browser, so the files everything depends on, the ones changing this week and the ones nobody has touched in a year are things you see from across the skyline.
How code becomes a city
Every source file is parsed into a syntax tree and its imports are resolved, which gives a graph of what depends on what. That graph is laid out as a city: a folder becomes a district, a file becomes a building whose height follows its line count, and every resolved import becomes a road between two buildings. Git history is read at the same time — files changed this week carry construction cranes, untouched code weathers grey.
What you can do in it
The city is a working tool, not a screenshot.
- Fly over it in orbit or drone mode, or walk the streets at ground level
- Click a building to see its functions, classes, imports and recent commits
- Light up the blast radius of a file: what imports it and what would break if it changed
- Open the security review for findings tied to the exact file and line they were found in
- Share a link to the city, embed a badge in your README, or fly over the shared metropolis of every scanned repository
Why a city
Software-city visualisation is a long-standing research idea because people are good at reading cities: size, density, distance and age are things we judge at a glance. Mapping lines of code to height, folders to districts and dependencies to roads lets that instinct work on code. RepoVerse runs it in the browser with Three.js, with no install and no signup for public repositories.
Questions
- Is the 3D code visualization free?
- Yes. Scanning any public GitHub repository, exploring its city, sharing it and reading its written summary are free and need no account.
- Which languages can be visualised?
- Python, JavaScript, TypeScript and TSX are parsed for functions, classes and imports. Go, Rust, Java, Kotlin, C#, PHP, Ruby, C++ and Swift are mapped as files and districts.
- Does it work for large repositories?
- Yes. Large repositories are laid out as dense districts and the scene is tuned to stay smooth in a browser; the size of a building always reflects the code it holds.
Related
- GitHub repository visualizer for architecture and dependenciesPaste a GitHub URL and get an interactive map of the repository: modules, dependency graph, hotspots, cycles and change history — rendered as a 3D city, free for public repos.
- GitHub security scanner for code, secrets and dependenciesScan a GitHub repository for injection flaws, leaked secrets and vulnerable dependencies. Data-flow traces from request to sink, lockfile-aware, with fixes.
Updated 2026-10-11