Labs · Card shelf
Your downloads folder,
finally a shelf.
Twenty half-remembered PNGs named card (3).png — which one had the good lorebook? Drop them all here: your browser reads every card locally, lines them up as covers, and opens each one into a full view — greetings as chat bubbles, token weight per field, every lorebook entry with its trigger flags. The shelf lives in this browser’s local storage and survives a restart. Nothing is uploaded.
Local cache · IndexedDB · Everything stays in this browser: parsing is local, storage is local (IndexedDB), nothing is uploaded — ever.
A viewer, not another checker
The shelf borrows its parsers from the tools next door — the same PNG chunk reader, spec normalizer and token yardstick as the Card Checkup, and the same lorebook attribute reader as the Lore Trigger simulator — but its job is different: it’s for looking. Batch import, covers, search, sort, arrow-key flipping between cards. When a card needs surgery rather than a look, the action row on every card hands you to the checkup, impersonation scan, format converter or prompt-assembly inspector.
FAQ
Are my cards uploaded when I add them to the shelf?
No. Parsing happens in your browser (PNG text chunks, JSON, and charx zip entries are all decoded locally), and the shelf itself is stored in your browser's IndexedDB — a private, per-site storage area on your own machine. Nothing is sent to any server, ever. Clearing your browser's site data also clears the shelf.
What formats can I import, and can I mix them in one batch?
PNG card images (chara / ccv3 chunks, ccv3 preferred — same order as SillyTavern), plain JSON (V1 flat legacy, V2, V3), and .charx zip containers. Mixed batches are fine: each file is parsed independently, failures are listed with their reason, and one broken card never blocks the rest.
Will my shelf survive closing the browser?
Yes — cards live in IndexedDB, so they're still there after a refresh, a restart, or a week away. Two honest caveats: private/incognito windows usually wipe IndexedDB when they close (the tool warns you and falls back to session-only mode), and browsers may evict site data under storage pressure. The shelf shows its current storage usage so you're never guessing.
Where do the cover images come from?
PNG cards are their own covers — the embedded artwork is shown directly. For .charx containers the first bundled image asset (icon or avatar preferred) is extracted locally. Plain JSON cards have no image inside, so they get a generated letterpress cover; remote avatar URLs are deliberately not fetched, to keep the zero-network promise honest.
Does it show everything that's inside the lorebook entries?
Each embedded lorebook entry is shown as its own card: primary and secondary keys, full content, plus badges for constant, insertion position (including @depth), order, trigger probability, secondary-key logic (AND/NOT), regex keys, sticky / cooldown / delay timers, and recursion flags. Entry search filters by key, name, or content. For firing simulations, use the Lore Trigger tool; for cross-platform migration checks, the Lorebook Doctor.