Tokei vs cloc: catalog facts
Tokei | cloc |
|
Best for: Getting a quick, accurate breakdown of what languages a codebase is actually made of |
Best for: Developers measuring the size and language mix of a codebase |
|
Free Free and open source, dual licensed under Apache 2.0 or MIT. |
Free Free and open source. |
|
Windows, macOS, Linux, Command line |
Windows, macOS, Linux, Command line |
- Correctly handles multi-line comments, nested comments and comment markers inside strings
- Over 150 languages recognised, with their various extensions
All 4 strengths for Tokei- Correctly handles multi-line comments, nested comments and comment markers inside strings
- Over 150 languages recognised, with their various extensions
- Counts millions of lines in seconds
- JSON, YAML and CBOR output so results can be stored and compared over time
|
- Supports many programming languages
- Separates code, comment and blank lines
All 3 strengths for cloc- Supports many programming languages
- Separates code, comment and blank lines
- Actively maintained
|
- Line counts are a crude measure of anything, which is not the tool's fault
- Unusual or very new languages may not be recognised
All 4 limitations for Tokei- Line counts are a crude measure of anything, which is not the tool's fault
- Unusual or very new languages may not be recognised
- No graphical interface
- Generated files are counted like any other unless you exclude them
|
- Line counts say little about code quality or complexity
- Command-line output only
|
|
Downloadable app |
Downloadable app |
|
Open source |
Open source |
|
License: Apache-2.0 |
License: GPL-2.0 |
|
No account needed |
No account needed |
|
Offline features available |
Offline features available |
Sources for TokeiCatalog checked September 21, 2026 |
Sources for clocCatalog checked September 24, 2026 |
“Not stated” means we have not confirmed it. Features can vary by device and plan.
Copy comparison link