GitDepth parses any repository into a live, explorable graph — every function, component, and API route wired exactly the way your code actually calls it. Click one, trace its whole path, ask it questions in plain English.
no signup · no install· free to use
Not a recording — the real app, playing itself. Click anywhere to take over.
Click any function, route, or component and its whole call chain lights up — what uses it, and everything it goes on to use. The rest of the codebase fades back, so the one question you actually have — "what breaks if I change this?" — has an immediate, visual answer.
The chat assistant is grounded in the real parsed code — not a generic model guessing at your project. Ask how a flow works and the relevant code lights up on the map as the answer comes back.
Switch to Story View for the main journeys through the code — what happens when someone uploads a file, logs in, or calls an API route — each told step by step in plain English, with a guided tour anyone on the team can follow.
Runs on your own Groq, OpenAI, or OpenAI-compatible API key, added once in AI Settings — never ours to pay for or see.
Orphan detection flags every function and component with zero incoming callers — the kind of dead weight that survives refactor after refactor because nobody's sure it's safe to remove.
Filters
Orphan functions
A public GitHub URL, a dragged-in folder, or a ZIP upload. Shortcut: swap github.com for gitdepth.com in any repo's address.
GitDepth walks the project file by file, streaming progress while it maps every function, component, route, and call.
Zoom from folders down to functions, trace any call path, filter by type, isolate unused code, or ask the assistant.
GitDepth is a free, web-based code visualization tool. It parses a codebase — from a public GitHub URL, a folder, or a ZIP — and draws it as an interactive code map: folders as regions, files as cards, and every function, class, component, and API route as a symbol inside its file. You can trace what calls what, find unused code, and read plain-English walkthroughs of how the code works.
Open gitdepth.com/app and paste the repository's URL — or replace github.com with gitdepth.com in the repo's address, so github.com/owner/repo becomes gitdepth.com/owner/repo. GitDepth clones the public repository, parses it, and opens the code map; small and medium repos take seconds.
Python, JavaScript, TypeScript, JSX, and TSX. Python is parsed with Python's standard-library ast module; JavaScript and TypeScript files are parsed with a lightweight pattern-based extractor, so no build step or install is needed. Files in other languages are skipped.
A function, class, or component is marked unused when nothing else in the parsed code calls or renders it and it isn't an entry point such as an API route, a main function, or an app entry file. Because this is static analysis, code that is only reached dynamically, by a framework, or from outside the repository can also show up — treat the list as candidates to review, not a delete list.
Story View explains a codebase in plain English. It finds the main journeys through the code — each starting from a place where the code begins doing something, like an API route, a page, or a command — and describes every step in plain language, with a guided tour that walks through them. It uses an AI model on your own API key.
GitDepth is free and needs no account or install. Parsing, the code map, tracing, search, filters, and export work without any key. The AI features — summaries, Story View, and the chat assistant — use your own API key from Groq, OpenAI, or any OpenAI-compatible provider, added once in AI Settings.
Not by URL: GitDepth only clones public repositories and never uses stored Git credentials. To map private code, upload it as a folder or ZIP instead — it's processed the same way and deleted automatically.
Only temporarily. Submitted code is cloned or extracted into a per-analysis folder on the server, used to build the map and answer your questions, and deleted automatically within 24 hours. Your AI API key stays in your browser and is never stored on the server.
Yes. The code map is built to stay readable at any size: zoomed out you see the folder structure, and zooming in reveals files and then individual functions. Files over 512 KB and dependency or build folders such as node_modules, .git, venv, dist, and build are skipped automatically.
Developers onboarding onto an unfamiliar repository, engineers returning to their own code after time away, reviewers checking what a change touches, and non-engineers such as product managers who need to understand how a codebase is put together without reading every file.
More detail — supported frameworks, limits, and how each feature works — is in the GitDepth docs.
Plot your first repo in under a minute.