Skip to content

FitLLM

Estimates whether a chosen model, quantisation and context length fit in a GPU's VRAM or a Mac's unified memory.

Actively maintained

At a glanceswept Oct 14, 2026

689 installs/mo

Established

For
people checking whether a local LLM fits their NVIDIA, AMD or Mac memory before downloading
Activity
Actively maintainedrelease 4 weeks ago · site updated 4 weeks ago
Used for
  • check whether a model fits in GPU VRAM
  • compare KV cache quantization and context length settings
  • estimate memory left after loading a Hugging Face model config
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 15, 2026
  • MCP serverrun.fitllm/fitllmverified in the MCP registry
  • Stateanswers, 3 toolschecked 2026-10-15
  • Address to connectfitllm.run/api/mcp
  • OpenAPI spec2 pathsthe spec ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Most used in Commerceby use, among tools still maintained — this tool shares no tags yet

Figure and bar: visits/mo, estimate · year: online since

Compare FitLLM with

Pick up to two.

All 10 alternatives to FitLLM →

All Commerce tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use FitLLM for?

Sign in to leave a note
Questions this page answers
  • What is FitLLM?

    Estimates whether a chosen model, quantisation and context length fit in a GPU's VRAM or a Mac's unified memory. It is listed in the Atlas under Commerce.

  • Who is FitLLM for?

    people checking whether a local LLM fits their NVIDIA, AMD or Mac memory before downloading

  • Do people use FitLLM?

    Established: 689 installs/mo (npm).

  • Is FitLLM still maintained?

    Actively maintained: release 4 weeks ago · site updated 4 weeks ago.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk