Hugo vs Jekyll: source lines of code compared

The Hugo vs Jekyll comparison on OctoCounts shows side-by-side source line counts for gohugoio/hugo and jekyll/jekyll, 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 gohugoio/hugo and jekyll/jekyll 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, gohugoio/hugo contains 259,973 total lines (185,937 code) across 1,120 files, while jekyll/jekyll contains 24,420 total lines (14,638 code) across 194 files as of 2026-11-04. gohugoio/hugo has about 13x the counted code lines of jekyll/jekyll 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.

Metricgohugoio/hugojekyll/jekyll
Files1,120194
Total lines259,97324,420
Code lines185,93714,638
Comment lines38,3176,475
Blank lines35,7193,307
Languages counted1711

Top languages in gohugoio/hugo: Go (94.7% of code), JavaScript (2.0% of code), C (2.0% of code). Top languages in jekyll/jekyll: Ruby (56.1% of code), Gherkin (Cucumber) (31.3% of code), JavaScript (7.3% of code). JavaScript appears in both top language lists; Go, C, HTML, YAML appear only in gohugoio/hugo's top languages; Ruby, Gherkin (Cucumber), Rakefile, BASH appear only in jekyll/jekyll's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. gohugoio/hugo was counted at ref master (commit 7a15e87270b5) on 2026-11-14; jekyll/jekyll was counted at ref 541d8b2ee75c8907de4744d4b87a7a6f1f997cae (commit 541d8b2ee75c) on 2026-11-04. 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. gohugoio/hugo: 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. jekyll/jekyll: 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.

About this comparison

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: gohugoio/hugo is the Hugo repository: the Go static site generator — its build pipeline, template and content handling, and embedded assets for the tool itself. jekyll/jekyll is the Jekyll repository: the Ruby static site generator, its core, and its documentation and test suites. Both are generator source trees, not sites built with them, and both were counted on the dates in the methodology line above.

The per-language tables show the implementation-language contrast plainly: Hugo's counted code is Go, while Jekyll's is Ruby — two generators addressing the same task in different language ecosystems.

Generator repository size says nothing about build speed, theme availability, or how large a generated site becomes; those depend on configuration, themes, and plugins, not on the tool's own line count.

Sources: gohugoio/hugo repository · jekyll/jekyll 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.

Compare FAQ

Which has more lines of code, gohugoio/hugo or jekyll/jekyll?

As of 2026-11-14, gohugoio/hugo contains 259,973 total lines (185,937 code) across 1,120 files, while jekyll/jekyll contains 24,420 total lines (14,638 code) across 194 files as of 2026-11-04. gohugoio/hugo has about 13x the counted code lines of jekyll/jekyll 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.

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 gohugoio/hugo, jekyll/jekyll, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. gohugoio/hugo was counted at ref master (commit 7a15e87270b5) on 2026-11-14; jekyll/jekyll was counted at ref 541d8b2ee75c8907de4744d4b87a7a6f1f997cae (commit 541d8b2ee75c) on 2026-11-04. 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.