# Electron vs Tauri: source lines of code compared

As of 2026-09-07, electron/electron contains 258,450 total lines (201,816 code) across 1,245 files, while tauri-apps/tauri contains 152,856 total lines (107,843 code) across 669 files as of 2026-09-07. electron/electron is about 1.9x the size of tauri-apps/tauri by code lines. Code size is not code quality: a larger count only means more source material, not a better or worse project.

| Metric | [electron/electron](https://octocounts.com/github/electron/electron) | [tauri-apps/tauri](https://octocounts.com/github/tauri-apps/tauri) |
| --- | ---: | ---: |
| Files | 1,245 | 669 |
| Total lines | 258,450 | 152,856 |
| Code lines | 201,816 | 107,843 |
| Comment lines | 19,974 | 23,632 |
| Blank lines | 36,660 | 21,381 |
| Languages counted | 12 | 12 |

Top languages in electron/electron: C++ (39.3% of code), TypeScript (38.1% of code), C Header (11.4% of code). Top languages in tauri-apps/tauri: Rust (67.6% of code), JSON (15.8% of code), YAML (4.0% of code). TypeScript appears in both top language lists; C++, C Header, Objective-C++, JavaScript appear only in electron/electron's top languages; Rust, JSON, YAML, TOML appear only in tauri-apps/tauri's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. electron/electron was counted at ref main (commit c4755b50b412) on 2026-09-07; tauri-apps/tauri was counted at ref dev (commit 10541070c14e) on 2026-09-07. See the [counting methodology](https://octocounts.com/docs/methodology) for ignored directories and analysis options.
## About this comparison

electron/electron counts the Electron repository: the embedded Chromium and Node.js integration layer, native shell code, API implementation, and documentation — but not Chromium's or Node's own source, which are consumed as prebuilt binaries. tauri-apps/tauri counts the Tauri core repository: the Rust runtime, the process and IPC layer, and the CLI tooling; it equally does not count the system webview it delegates to. Both counts therefore measure the glue layer each project maintains, not the browser engines involved.

The language tables tell the architectural story directly: Electron's counted code is dominated by C++ for the native integration layer with a sizeable TypeScript/JavaScript API surface, while Tauri core is predominantly Rust — each project's chosen systems language for the same job of connecting web content to the OS.

The engine asymmetry matters when reading the totals: Electron bundles (and updates) a full Chromium with each app, while Tauri relies on the operating system's webview, so neither repository's SLOC represents what ships inside a finished desktop app.

_Repository size is not install size and not memory footprint. A finished app's weight depends on the engine strategy above, not on how many source lines the framework repository contains._

Sources: [electron/electron repository](https://github.com/electron/electron) · [tauri-apps/tauri repository](https://github.com/tauri-apps/tauri). Statements verified 2026-09-08.

Evidence and next steps:

- [electron/electron SLOC report](https://octocounts.com/github/electron/electron)
- [tauri-apps/tauri SLOC report](https://octocounts.com/github/tauri-apps/tauri)
- [Compare electron/electron and tauri-apps/tauri interactively](https://octocounts.com/compare?left=https%3A%2F%2Fgithub.com%2Felectron%2Felectron&right=https%3A%2F%2Fgithub.com%2Ftauri-apps%2Ftauri)

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, electron/electron or tauri-apps/tauri?

electron/electron has more code: 201,816 code lines versus 107,843 for tauri-apps/tauri, about 1.9x as much, based on cached OctoCounts reports as of 2026-09-07.

### 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 electron/electron, tauri-apps/tauri, or any repository.

### How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. electron/electron was counted at ref main (commit c4755b50b412) on 2026-09-07; tauri-apps/tauri was counted at ref dev (commit 10541070c14e) on 2026-09-07. 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)
- [GitHub SLOC counter guide](https://octocounts.com/docs/github-sloc-counter)
- [Counting methodology](https://octocounts.com/docs/methodology)
- [OctoCounts API docs](https://octocounts.com/docs/api)