# Laravel vs Django: source lines of code compared

The Laravel vs Django comparison on OctoCounts shows side-by-side source line counts for laravel/laravel and django/django, 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-10-06, laravel/laravel contains 2,188 total lines (1,150 code) across 34 files, while django/django contains 558,996 total lines (405,311 code) across 3,624 files as of 2026-10-11. django/django is about 352x the size of laravel/laravel by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.

| Metric | [laravel/laravel](https://octocounts.com/github/laravel/laravel) | [django/django](https://octocounts.com/github/django/django) |
| --- | ---: | ---: |
| Files | 34 | 3,624 |
| Total lines | 2,188 | 558,996 |
| Code lines | 1,150 | 405,311 |
| Comment lines | 737 | 45,698 |
| Blank lines | 301 | 107,987 |
| Languages counted | 7 | 12 |

Top languages in laravel/laravel: PHP (85.1% of code), JSON (9.1% of code), XML (3.1% of code). Top languages in django/django: PO File (59.4% of code), Python (32.0% of code), Modelica (5.5% of code). JavaScript, CSS appear in both top language lists; PHP, JSON, XML appear only in laravel/laravel's top languages; PO File, Python, Modelica appear only in django/django's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. laravel/laravel was counted at ref 13.x (commit f4000aeb018f) on 2026-10-06; django/django was counted at ref main (commit dab0a5c47f15) on 2026-10-11. See the [counting methodology](https://octocounts.com/docs/methodology) for ignored directories and analysis options.
## About this comparison

laravel/laravel counts the Laravel application skeleton — the starter project a developer installs and builds on — not the framework code itself, which lives in the separate laravel/framework package. django/django counts the Django framework repository in full. The two counts therefore measure different things: a minimal starter template versus a complete web framework, counted on the dates in the methodology line.

The lopsided totals here are a repository-boundary artifact: the Laravel side counts a thin application scaffold while the Django side counts the whole framework, so the gap between the numbers says little about the frameworks themselves.

Both ecosystems' actual framework code is larger than what is shown on the left: Laravel's components ship as dependencies (the laravel/framework package and its Illuminate sub-packages), which this page does not count.

_The most likely misreading is treating this as Laravel-is-tiny: the left number is a starter repo, not the framework. For a framework-to-framework reading, the counted Django tree should be compared against the laravel/framework package, which is not the repository paired on this page._

Sources: [laravel/laravel repository (application skeleton)](https://github.com/laravel/laravel) · [django/django repository](https://github.com/django/django). Statements verified 2026-09-16.

Evidence and next steps:

- [laravel/laravel SLOC report](https://octocounts.com/github/laravel/laravel)
- [django/django SLOC report](https://octocounts.com/github/django/django)
- [Compare laravel/laravel and django/django interactively](https://octocounts.com/compare?left=https%3A%2F%2Fgithub.com%2Flaravel%2Flaravel&right=https%3A%2F%2Fgithub.com%2Fdjango%2Fdjango)

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, laravel/laravel or django/django?

django/django has more code: 405,311 code lines versus 1,150 for laravel/laravel, about 352x as much, based on cached OctoCounts reports as of 2026-10-11.

### 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 laravel/laravel, django/django, or any repository.

### How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. laravel/laravel was counted at ref 13.x (commit f4000aeb018f) on 2026-10-06; django/django was counted at ref main (commit dab0a5c47f15) on 2026-10-11. 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)