Repository navigation
Feature Local Models
The Local Models tab is where your installed library lives. It has its own state, filters, pagination, and download progress bar, fully independent from the Browser tab — a download started here never drives the Browser's progress bar, and a selection made here never leaks into the Browser's batch download.
Update Models used to be a separate tab. It is now merged into this one, so scanning for updates, batch updating, renaming, and deleting all happen in one place. Bulk maintenance (metadata refresh, previews, organization) moved to the Organization tab.
- Pick the Content type (Checkpoint, LORA, …) and optionally a Base model filter
- Click 📋 Load local models
- Cards render with colour-coded borders — aquamarine = installed and current, orange = a newer version exists
Sort by offers Name (A-Z), Name (Z-A), Recently downloaded, and Oldest downloaded. Per page switches between 25 / 50 / 100 cards, with Prev/Next buttons and a page slider. Paging is a server-side slice of the already-sorted list held in memory, so it is instant and never re-queries the API.
🧹 Clear empties the grid and resets the tab's state without touching the Browser.
Resolving a whole local library against the CivitAI API is where this tab used to break. The fetch is now hybrid:
-
Batched first — models are resolved in grouped
/modelsrequests, one call per batch. - Per-id fallback — if a single model poisons a batch (some large models make the endpoint return HTTP 500), that batch is retried id by id, so one bad model no longer costs you the whole page.
-
Version-endpoint recovery — models that still fail are resolved through
/model-versions/{id}instead. -
Domain fallback — a request that fails on
civitai.comis retried oncivitai.red(and vice versa depending on the SFW setting). - Local-only cards — anything the API still cannot resolve renders from its local sidecar instead of disappearing from the grid. Delisted, renamed, and hash-less files stay visible.
Click a card to open it. From there you can:
- Switch Version — the panel refreshes to that version's images, description, and files
- Switch File — when a version ships multiple files (fp16/fp8, pruned, different formats), the filename and SHA256 follow your selection
-
➕ Add to prompt — appends the model's trained tags, inserting
<lora:filename:1>syntax automatically for LoRAs - ✏️ Rename — renames the model and everything attached to it
- ⬇️ Download selected version — grabs a version you don't have installed
- ⬆️ Update to latest — downloads the newest version within the installed base-model family, so a Pony LoRA never silently updates into an Illustrious one
- 🗑️ Delete — sends the model and its sidecars to the system recycle bin by default
Outdated models get an orange border. ⬆️ Only models with updates is a pure client-side view filter — it hides everything else instantly, without re-scanning.
To update in batch: tick the checkboxes on the cards you want, pick a retention policy under When updating:, then click ⬆️ Update selected.
| Retention | What happens to the old file |
|---|---|
| Replace installed | Old version is removed after the new one downloads successfully |
| Keep installed (download alongside) | Both versions stay on disk |
The retention default is also configurable as civitai_neo_update_retention — see Settings Reference. Deletions go through send2trash, so a replaced version lands in the recycle bin rather than being erased.
Version resolution is hybrid: the extension matches by model family first and falls back to baseModel, which is what keeps "latest" meaningful for models whose version names don't sort cleanly.
A model counts as installed when any of these match: its SHA256, its filename stem, or the modelVersionId cached in its sidecar. The modelVersionId path is what keeps renamed or hash-less files marked as installed — before it existed, renaming a file made its card go grey.
Card action buttons resolve the exact file by stem rather than by prefix, so model.safetensors and model_v2.safetensors are never confused for one another.
Related: LoraDex · Auto-Organization · Metadata Maintenance · Downloads & Previews