Every set marks a moment, every minifigure carries a character, and every piece earns its place. Collecting LEGO is part memory, part curiosity, and part the quiet joy of building a world that is unmistakably yours.
Explore the sets that shape your collection, from complete builds to display pieces and sets kept simply because they matter. Each catalog match brings together theme, year, lifecycle, parts, minifigs and current market context.
Explore owned MINIFIGs and figure-like PARTs. Counts keep their BrickLink identities separate.
Manage your Collectable series as collections in their own right. Each package shows how many unique minifigures you own versus the official series total, while duplicate physical units remain visible separately.
Click any theme to open its sets and minifigs. Catalog themes are used when available, with closely related labels automatically merged into one consistent theme.
Minifigures you own as incomplete projects. Each card shows the catalog identity and official component breakdown without counting the item as a complete owned minifigure.
A simple view of the parts inside the sets you own: how many there are, which designs and colours appear, and where each part is used.
Explore the market context behind your collection using recent BrickLink price-guide data. Values are references, not guarantees: condition, completeness, packaging and transaction volume can materially change the price.
Collection used value counts complete Sets, add-ons and independent figures. Figures linked to an owned complete Set keep their individual prices but are not added again. Missing prices produce a known subtotal. The legacy sum is not a verified collection total. Historical snapshots are preserved.
Real snapshots captured only after successful data refreshes. Monthly for the latest 12 months, quarterly thereafter.
| Item↕ | Theme↕ | Year↕ | New↕ | Used↕ | Launch↕ | Since launch↕ | 6m sales↕ | Range↕ | Confidence↕ |
|---|
Market confidence is calculated by My Brick Archive from the available six-month sales count and price spread. It is not an official BrickLink rating. “Since launch” is shown only for sets where a EUR launch price and a current New market reference are both available.
Need a hint for my next present? Consider this the officially unofficial gift guide. Family, kids and in-laws: browse freely, take notes, and remember — excellent ideas are hiding in plain sight. 😇
Manage the local collection source, API configuration, access PIN and data-source information used by My Brick Archive.
Unknown never means active or retired — it means the catalog source has not resolved that item yet.
Changes recorded after each completed data refresh. Publication comparisons are labelled separately.
Read-only consistency checks for the unified collection source, catalog references, set/minifig relationships, lifecycle dates and Parts catalogue synchronization. Nothing here changes your collection data.
Temporary access check for the official BrickEconomy Set widget. This uses only their iframe widget — no API key, scraping or collection data is sent by My Brick Archive.
Load the test widget. If values/chart appear, this domain has widget access. An authorization message or blank widget means access is not active yet.
Market history is local project data. It is embedded into the published site for display, but the JSON file itself and its backups are never uploaded to Firebase.
BrickLink My Collection imports must be split by item type. Export separate XML files for Sets, Minifigures, Books and figure-like Parts. Sets are exported as Used + Complete; all other item types are exported as Used.
One label per physical minifig, ready for A4 printing: image, descriptive metadata, Set / Parent Set relationship and direct BrickLink QR.
Incomplete projects are excluded by default. When enabled, every Incomplete label has a yellow border and a separate INCOMPLETE badge; Print All starts the Incomplete group on a new A4 page; Print Selection fills remaining slots with Incomplete labels after complete labels. The QR payload always uses the canonical BrickLink minifig URL.
The day-to-day updater resolves new collection references through the configured APIs and cache. The canonical Parts inventory is maintained separately so a normal update stays fast and compact.
Download these BrickLink files when taking a new offline catalogue snapshot: Catalog Items — Sets, Catalog Items — Minifigures, Catalog Items — Parts, Categories, Colors, Codes and Item Types. These files are maintenance/reference inputs; they are not required for every option 2 run.
If option 2 reports that physical sets and the Parts catalogue are out of sync, it finishes the local data refresh but blocks publication. Then run option 4: it updates only the changed Parts contributions and publishes without repeating the full collection enrichment. Use option 5 for a complete rebuild.
Ownership is never inferred from API responses, caches, catalog metadata or a previous index.html.
Enter your API credentials and Setup access PIN here on your own computer. The exported vault_api.json is read only by the local updater. API secrets and the PIN itself are not embedded into the HTML; only a one-way PIN verifier is written into the site.
PIN changes: after changing the Setup access PIN, export/replace vault_api.json and run update_collection.bat. The new PIN only becomes active after the updater writes its verifier into index.html.
Security: browser local storage and the exported JSON are convenient, not encrypted secret storage. Keep them on a trusted personal computer. The Setup PIN is stored in the JSON, while the HTML receives only a one-way verifier. A short PIN protects against casual access rather than determined inspection.
Active catalog sources are BrickLink and Brickset. Parts are maintained locally in the canonical Parts inventory.