A database you define

A collection database you define yourself

A collection database should describe your collection, not somebody else's catalogue. In KeepsakeGrid you create the collections, and every object becomes a searchable record you can filter, export, and correct.

Open KeepsakeGrid See what it records

Collections you name yourself
Searchable across every field
JSON and CSV in, JSON and CSV out

What KeepsakeGrid actually does

Every point below is a feature the product ships today. Nothing on this page describes a roadmap.

How records are structured

Each collection carries a name, a description, an icon, and a colour. Each record inside it uses one consistent shape, so the whole database stays searchable.

Identity: name, maker or publisher, year, and the collection it belongs to.
State: condition, owned or wishlist status, and an estimated value.
Reference: a serial or reference number, tags, and private notes.
History: up to 24 recorded value changes per item, each with its date and the difference from the previous figure.

Querying the database

There is no query language to learn. One search field reads the whole workspace and the filters narrow it down.

A single search box matches item names, makers, years, notes, serial numbers, tags, and collection names.
Collection and status filters combine with the search text.
Selecting a record opens its full detail, including value history and private photos.

Importing an existing list

Most collections start life in a spreadsheet. The import step shows exactly what would change before it changes anything.

A CSV needs Name and Collection columns; up to 400 rows are inspected from a file under 2 MB.
Missing collections are created for you as part of the import.
The preview reports valid rows, row-level errors, and duplicates that will be skipped.
A KeepsakeGrid JSON backup restores records together with their recorded value history.

What it deliberately does not do

Any tool for this job is only worth choosing once its limits are clear, so here are KeepsakeGrid's before you start typing in records.

Recorded values are your own estimates. KeepsakeGrid never presents them as appraisals, insurance values, or live market prices.
There is no barcode lookup, licensed catalogue data, or automatic pricing. Every record is one you type or import.
Private notes, serial numbers, wishlist items, photos, and valuation history are never included in a shared page.
A workspace holds up to 30 collections and 400 items. It is a personal database, not a multi-user one.

Questions about collection database

Can I add my own fields?

You define the collections and the vocabulary you use inside them, but the record shape itself is fixed: name, maker, year, condition, status, value, serial or reference number, tags, and notes. Tags and notes are where collection-specific detail usually goes.

Is there a catalogue of known items to pick from?

No. There is no licensed catalogue and no barcode lookup, so nothing is pre-filled for you. That is also why nothing is missing: an object exists in your database as soon as you describe it.

What happens to duplicates when I import?

Rows that fingerprint-match a record already in your workspace are skipped, and the preview tells you how many were skipped before you confirm.

Start with one object

Open KeepsakeGrid