The Godot vs Bevy comparison on OctoCounts shows side-by-side source line counts for godotengine/godot and bevyengine/bevy, counted under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.
This page compares the source lines of code (SLOC) of godotengine/godot and bevyengine/bevy using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.
As of 2026-11-14, godotengine/godot contains 5,954,752 total lines (4,237,573 code) across 11,441 files, while bevyengine/bevy contains 617,936 total lines (518,523 code) across 2,284 files as of 2026-11-15. godotengine/godot has about 8.2x the counted code lines of bevyengine/bevy under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.
| Metric | godotengine/godot | bevyengine/bevy |
|---|---|---|
| Files | 11,441 | 2,284 |
| Total lines | 5,954,752 | 617,936 |
| Code lines | 4,237,573 | 518,523 |
| Comment lines | 740,638 | 28,927 |
| Blank lines | 976,541 | 70,486 |
| Languages counted | 36 | 13 |
Top languages in godotengine/godot: C++ (33.7% of code), C Header (19.5% of code), PO File (17.0% of code). Top languages in bevyengine/bevy: Rust (97.7% of code), TOML (1.9% 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, Pan, Shell 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 master (commit 4d0d43b77dd2) on 2026-11-14; bevyengine/bevy was counted at ref main (commit ef5312a29994) on 2026-11-15. See the counting methodology for ignored directories and analysis options.
Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. godotengine/godot: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed. bevyengine/bevy: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.
Background observations recorded on 2026-09-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: godotengine/godot is 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 is 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 · bevyengine/bevy repository. Statements verified 2026-09-16.
Evidence and next steps:
Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.
Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.
As of 2026-11-14, godotengine/godot contains 5,954,752 total lines (4,237,573 code) across 11,441 files, while bevyengine/bevy contains 617,936 total lines (518,523 code) across 2,284 files as of 2026-11-15. godotengine/godot has about 8.2x the counted code lines of bevyengine/bevy under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.
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.
Methodology: both counts come from cached OctoCounts reports generated with tokei. godotengine/godot was counted at ref master (commit 4d0d43b77dd2) on 2026-11-14; bevyengine/bevy was counted at ref main (commit ef5312a29994) on 2026-11-15. See the counting methodology for ignored directories and analysis options.
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.