The Laravel vs Symfony comparison on OctoCounts shows side-by-side source line counts for laravel/laravel and symfony/symfony, 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 laravel/laravel and symfony/symfony 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-13, laravel/laravel contains 2,188 total lines (1,149 code) across 34 files, while symfony/symfony contains 1,167,546 total lines (948,899 code) across 6,594 files as of 2026-11-16. symfony/symfony has about 826x the counted code lines of laravel/laravel 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 | laravel/laravel | symfony/symfony |
|---|---|---|
| Files | 34 | 6,594 |
| Total lines | 2,188 | 1,167,546 |
| Code lines | 1,149 | 948,899 |
| Comment lines | 738 | 134,904 |
| Blank lines | 301 | 83,743 |
| Languages counted | 8 | 12 |
Top languages in laravel/laravel: PHP (66.1% of code), Blade (19.0% of code), JSON (9.1% of code). Top languages in symfony/symfony: PHP (97.6% of code), Twig (1.4% of code), JSON (0.6% of code). PHP, JSON, JavaScript appear in both top language lists; Blade, XML appear only in laravel/laravel's top languages; Twig, CSS appear only in symfony/symfony's top languages.
Methodology: both counts come from cached OctoCounts reports generated with tokei. laravel/laravel was counted at ref 13.x (commit a255d7688770) on 2026-11-13; symfony/symfony was counted at ref 8.2 (commit 7da438612e60) on 2026-11-16. 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. laravel/laravel: 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. symfony/symfony: 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: laravel/laravel is the Laravel application skeleton — the starter repository a new application is created from: default configuration, bootstrap files, and declared dependencies — not the framework implementation itself. symfony/symfony is the Symfony framework monorepo: component and bundle sources maintained together across many packages. These two repositories therefore do not describe the same kind of repository, which is the first thing to know when reading this page.
The totals reflect that asymmetry directly: the Laravel skeleton is intentionally minimal, an empty starting point whose framework code arrives as a Composer dependency, while the Symfony monorepo counts the full framework source across dozens of components.
The per-language tables confirm both projects live in the same language ecosystem, but one number measures a starter template and the other measures a maintained framework monorepo — this page is best read as an illustration of how repository selection shapes a count.
Do not conclude from this page that Laravel is a smaller or simpler framework: the framework code lives in laravel/framework, which is not what is counted here. This comparison measures repository selection, not framework size.
Sources: laravel/laravel repository (application skeleton) · symfony/symfony repository (framework monorepo). 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-13, laravel/laravel contains 2,188 total lines (1,149 code) across 34 files, while symfony/symfony contains 1,167,546 total lines (948,899 code) across 6,594 files as of 2026-11-16. symfony/symfony has about 826x the counted code lines of laravel/laravel 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 laravel/laravel, symfony/symfony, or any repository.
Methodology: both counts come from cached OctoCounts reports generated with tokei. laravel/laravel was counted at ref 13.x (commit a255d7688770) on 2026-11-13; symfony/symfony was counted at ref 8.2 (commit 7da438612e60) on 2026-11-16. 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.