
Compute various size metrics for a Git repository, flagging those that might cause problems - github/git-sizer

AICostNest
LLM Cost Calculator
Tokenflood
Count LLM tokens and estimate API cost from text, PDF, DOCX, code, data files, and images with privacy-first browser-based processing.
Which is more popular?
Based on our record, git-sizer seems to be more popular. It has been mentioned 1 time since March 2021.
Website, pricing, platforms and company facts side by side.
|
|
|
|
|---|---|---|
| Website | github.com | tokencalculator.dev |
| Pricing | — | |
| Platforms | — | |
| Company | — | Startup from India · 1 - 9 employees · 2026 |
| Listed in |
In their own words, as submitted to SaaSHub.


No description of git-sizer yet.
TokenCalculator.dev is a privacy-first, 100% browser-based LLM token counter and API cost estimator designed for AI engineers, developers, and product teams. Unlike conventional text-only calculators that require uploading sensitive prompts to third-party servers, TokenCalculator.dev processes...
What each product offers, as listed by its team.


Possible disadvantages
An editorial look at what each product does well and who it suits.


Overall verdict
Why this product is good
Recommended for
No analysis of TokenCalculator.dev yet.
How often each product is chosen within a category, 0–100% relative to the other.


As answered by people managing git-sizer and TokenCalculator.dev.
TokenCalculator.dev's answer:
TokenCalculator.dev is a 100% browser-based, privacy-first token counter and API cost estimator that handles multimodal payloads without sending data to a server. Unlike conventional text-only counters, it processes pasted text, local documents (PDF, DOCX, and code in 20+ languages up to 12 MB), and image files (PNG, JPEG, WebP, GIF) entirely on the client side across OpenAI, Claude, Gemini, and DeepSeek.
TokenCalculator.dev's answer:
Most token counters either require pasting text into third-party cloud servers or only support basic text inputs for a single provider. TokenCalculator.dev guarantees zero prompt or document retention, supports direct document parsing (PDF/Word/code) and visual tile/patch token calculations, and lets you compare live input costs and context-window fits across four major frontier providers simultaneously.
TokenCalculator.dev's answer:
AI engineers, software developers, technical product managers, and researchers who build LLM-powered applications, design RAG pipelines, or manage API token budgets and context window limits.
TokenCalculator.dev's answer:
Developers frequently face unexpected API costs, context overflow errors, and privacy concerns when testing prompts and document payloads with online token tools. TokenCalculator.dev was created to provide a fast, transparent, and completely offline-capable developer utility that reliably measures realistic production payloads—including codebases, documents, and images—without compromising sensitive data.
TokenCalculator.dev's answer:
Built with modern web technologies using TypeScript and WebAssembly/JavaScript for client-side BPE tokenization (o200k_base), browser-native text extraction parsers for PDF and DOCX, client-side Canvas APIs for image dimension inspection, and integrated model pricing metadata.
TokenCalculator.dev's answer:
Independent AI Engineers & Full-Stack Developers RAG & Agentic Workflow Builders Open-Source Software Contributors Tech Startups budgeting multi-model API deployments
Share your experience with using git-sizer and TokenCalculator.dev. For example, how are they different and which one is better?
Recommendations tracked on public social media and blogs since March 2021.


Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago
Tracking TokenCalculator.dev since Sep 2026.