b2KIT

Git Log Visualizer

Paste git log output and see a visual branch graph with commit history and merge points.

Tested tool guide Tested browser tools Checked August 16, 2026

What Git Log Visualizer does and how it behaves

Git Log Visualizer turns pasted Git history into a node-and-lane view of commits, forks, and merge points. It is intended for output that preserves commit identifiers and topology, especially `git log --graph` output. The pasted text is the complete evidence: the tool does not inspect your repository or recover revisions excluded by the original command, and the text is processed in the browser. The usual surprise is that a drawn lane is not necessarily a named branch. Git records parent relationships; branch names are movable refs shown only when the log includes them.

How the result is produced

1

Preparing topology-rich input

A compact source is `git log --graph --oneline --decorate --all`. Its graph characters express lane connections, abbreviated object names identify commits, subjects describe them, and decorations can expose refs such as branches and tags. A merge must be understood from its multiple-parent relationship, not merely from the word `Merge` in its subject. Plain hashes and subjects may not provide enough topology.

2

Reading the rendered history

Each recognized commit record becomes a point in the displayed history, while connecting lanes represent the ancestry supplied by the log. A multi-parent junction marks a merge commit. The vertical sequence reflects the supplied revision walk; horizontal placement routes connections and is not a permanent branch assignment. Ref decorations label commits but do not create additional commits or change their parent relationships.

Good uses

  • Reviewing a CI failure report that includes Git history and checking whether a feature line merged before the failing commit.
  • Explaining an unfamiliar repository's recent topology when several merges make ordinary one-line output difficult to follow.
  • Comparing release and development history from a pasted log before discussing a merge, rebase, revert, or backport.

Limits and checks

  • The graph cannot show commits omitted by the original revision range, `--max-count`, path filtering, a shallow clone, or unavailable refs. The oldest displayed point may only be where the pasted excerpt stops.
  • Lane position is not branch identity. Branch refs can move or be deleted, while commits and parent links remain. Without decorations, a side lane does not reveal the historical name of that work.
  • Vertical distance is not elapsed time. Author dates and committer dates can differ, clocks can be inaccurate, and revision ordering must accommodate ancestry. Use commit metadata when timing matters.

Common questions

What git log command should I paste?

`git log --graph --oneline --decorate --all` is a compact choice when you want topology, readable subjects, and ref names. Remove `--all` if only history reachable from the current starting point matters. The visualizer cannot compensate for commits excluded before pasting, so use a revision range, path filter, or count limit only when that narrower view is intentional.

Can the graph tell me which branch a commit originally belonged to?

No. A Git commit stores parent links, not an enduring original-branch field, and branch names are movable refs to commits. The visualization can show ancestry and any ref decorations present in the pasted text. A lane may represent a side line of development, but its horizontal position alone cannot establish that line's former branch name.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools