Peryton Design
Peryton Lab / Product case study

3D Model DB

A local-first visual archive built to make a sprawling 3D model collection feel immediate, searchable, and worth exploring.

1,504
models cataloged
28,660
visual assets indexed
22
model types
Personal Model Archive Local
3D Model DB showing a searchable grid of 3D models
Library state Watched live
ArchitectureLocal by design

A personal archive that works like a product.

Model folders are fine—until the collection becomes the size of a small museum. Generic filenames, deep directories, and thousands of renders make discovery harder than collecting.

3D Model DB turns that file system into a visual catalog. The originals stay on the owner's machine while the app adds fast previews, structured metadata, and a focused interface for finding the right asset without breaking creative momentum.

The experience

Browse at the speed of recognition.

Every interaction is designed around the way a visual collector actually remembers: by the image first, then the metadata.

Collection view1,504 models
Virtualized model collection grid with search and filters
01 / CollectionA dense library, kept visually calm.

01

Find, don't hunt

Search by name and narrow the collection by type, universe, date, favorites, or pinned selections.

02

See the whole set

Hover previews reveal more of a model before opening it, with favorite images promoted and pinned covers held in place.

03

Inspect every detail

A dedicated viewer loads the active image on demand, then supports deep zoom and pan when precision matters.

Model detail
Model detail page with image strip and structured character information

From asset to artifact

Context lives beside the image.

Each entry brings its renders and reference details into one workspace: character, universe, model type, alignment, abilities, origin story, notes, source links, and custom fields.

  • Choose a cover image and favorite multiple views
  • Edit structured metadata without leaving the record
  • Use optional Gemini assistance to suggest character details
  • Open high-resolution originals only when requested

From folder chaos to a living collection.

The application respects the existing library instead of forcing it into a cloud service or proprietary storage system.

  1. 01

    Connect

    Point the app at the existing model library. The first scan builds a visual index without relocating original files.

  2. 02

    Watch

    Folder changes are monitored in the background, so the collection can update as new models and renders arrive.

  3. 03

    Curate

    Search, filter, favorite, pin, annotate, and import ZIP packages from one focused workspace.

  4. 04

    Protect

    Back up SQLite, move metadata through CSV, or export a safe derivative snapshot for mobile and sync workflows.

Under the hood

Local-first, performance-minded.

Original artwork stays local. Lightweight derivatives and a strict process boundary keep a large image library responsive and predictable.

01 / SourceModel libraryOriginal renders on disk
02 / CoreElectron mainScan · watch · import · repair
03 / DataSQLite + cacheMetadata · thumbnails · previews
04 / InterfaceReact workspaceSecure preload bridge
OptionalGemini lookup
PortableSnapshot export

A

Virtualized by default

react-window only renders the cards in view. The interface stays light even when the archive does not.

B

Derivatives on demand

Sharp generates WebP thumbnails and previews in a low-concurrency background queue, preserving originals for deep viewing.

C

Resilient over time

Changed or missing images are detected, stale derivatives are repaired, and asset identities survive common file moves.

D

Ready to travel

Deterministic snapshots package metadata and display derivatives without putting the live SQLite database in a sync folder.

Measured on the working archive

1.5kmodels
28.6kassets
10universes
100%local originals

The portfolio isn't describing a hypothetical scale test. These figures come from the collection the application manages today.

The outcome

The collection became an experience.

3D Model DB began as a practical answer to folder fatigue. It has grown into a local-first product system: desktop catalog, resilient image pipeline, portable snapshot format, and a path to a companion mobile experience.