# Godot vs Bevy: source lines of code compared

The Godot vs Bevy comparison on OctoCounts shows side-by-side source line counts for godotengine/godot and bevyengine/bevy, counted with the same engine and analysis options on the dates shown in the methodology line: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.

As of 2026-09-16, godotengine/godot contains 5,773,837 total lines (4,110,443 code) across 11,360 files, while bevyengine/bevy contains 557,967 total lines (464,531 code) across 2,174 files as of 2026-09-17. godotengine/godot is about 8.8x the size of bevyengine/bevy by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.

| Metric | [godotengine/godot](https://octocounts.com/github/godotengine/godot) | [bevyengine/bevy](https://octocounts.com/github/bevyengine/bevy) |
| --- | ---: | ---: |
| Files | 11,360 | 2,174 |
| Total lines | 5,773,837 | 557,967 |
| Code lines | 4,110,443 | 464,531 |
| Comment lines | 734,838 | 28,267 |
| Blank lines | 928,556 | 65,169 |
| Languages counted | 12 | 12 |

Top languages in godotengine/godot: C++ (34.4% of code), C Header (20.0% of code), PO File (15.2% of code). Top languages in bevyengine/bevy: Rust (97.6% of code), TOML (2.0% of code), SVG (0.2% of code). C++, C Header, PO File, C, C++ Header appear only in godotengine/godot's top languages; Rust, TOML, SVG, Shell, Pan appear only in bevyengine/bevy's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. godotengine/godot was counted at ref dfa06cafb4546eac47d863dfa12aec54e4efa586 (commit dfa06cafb454) on 2026-09-16; bevyengine/bevy was counted at ref f3b53464513111374089cfcc724ab448e8479dd1 (commit f3b534645131) on 2026-09-17. See the [counting methodology](https://octocounts.com/docs/methodology) for ignored directories and analysis options.
## About this comparison

godotengine/godot counts the Godot engine repository: the C++ engine core, editor, built-in scripting-language support, and documentation, together with its test and template material. bevyengine/bevy counts the Bevy engine repository: a collection of Rust crates forming the engine and its examples. Both are full game-engine source trees, counted on the dates in the methodology line.

The per-language tables state the architectural contrast plainly: Godot's counted code is dominated by C++, while Bevy's is Rust — each project's chosen systems language for the same role of engine core.

Godot's repository includes the editor and its user-facing tooling, whereas Bevy's repository is organized as modular crates with examples, so the two counts are distributed differently across engine subsystems even where their scope overlaps.

_Engine repository size is not a measure of what a finished game ships, and not a measure of editor features: both engines are typically used with additional assets, plugins, and — in Bevy's case — an external editor workflow._

Sources: [godotengine/godot repository](https://github.com/godotengine/godot) · [bevyengine/bevy repository](https://github.com/bevyengine/bevy). Statements verified 2026-09-16.

Evidence and next steps:

- [godotengine/godot SLOC report](https://octocounts.com/github/godotengine/godot)
- [bevyengine/bevy SLOC report](https://octocounts.com/github/bevyengine/bevy)
- [Compare godotengine/godot and bevyengine/bevy interactively](https://octocounts.com/compare?left=https%3A%2F%2Fgithub.com%2Fgodotengine%2Fgodot&right=https%3A%2F%2Fgithub.com%2Fbevyengine%2Fbevy)

Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.

## Compare FAQ

### Which has more lines of code, godotengine/godot or bevyengine/bevy?

godotengine/godot has more code: 4,110,443 code lines versus 464,531 for bevyengine/bevy, about 8.8x as much, based on cached OctoCounts reports as of 2026-09-17.

### Does more source lines of code mean more complexity?

Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for godotengine/godot, bevyengine/bevy, or any repository.

### How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. godotengine/godot was counted at ref dfa06cafb4546eac47d863dfa12aec54e4efa586 (commit dfa06cafb454) on 2026-09-16; bevyengine/bevy was counted at ref f3b53464513111374089cfcc724ab448e8479dd1 (commit f3b534645131) on 2026-09-17. See the counting methodology for ignored directories and analysis options.

### Can I compare a different branch, tag, or commit?

Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.

## Related OctoCounts pages

- [Interactive repository comparison](https://octocounts.com/compare)
- [Recently analyzed repositories](https://octocounts.com/recent)
- [Popular SLOC reports](https://octocounts.com/popular)
- [Trending GitHub repositories](https://octocounts.com/trending)
- [Hall of Monoliths](https://octocounts.com/hall-of-monoliths)
- [Original research: how filtering changes SLOC counts](https://octocounts.com/research)
- [GitHub SLOC counter guide](https://octocounts.com/docs/github-sloc-counter)
- [Counting methodology](https://octocounts.com/docs/methodology)
- [SLOC and code metrics glossary](https://octocounts.com/docs/glossary)
- [OctoCounts API docs](https://octocounts.com/docs/api)