Every way of sorting a LEGO® collection works on the day you finish it. You know where everything went, because you just put it there. The trouble shows up three months later, halfway through a build, when you need one part and can’t remember which box it ended up in.
Sorting tells you where to start looking: plates with plates, so you head for the plate drawers. That’s enough while you can picture every drawer. It stops being enough when one rule fills six of them, and the only record of which 1×2s went where is your memory. The five methods below are the ones builders actually use. The first four rely on you remembering. The fifth writes it down.
1. Sort by color
Color is the sort that looks finished. Red with red, blue with blue, a wall people photograph. If you build by eye — choosing a palette rather than following a parts list — it can be a genuinely pleasant way to work.
The trouble is how you search. A step in the instructions shows a 1×2 plate in dark bluish gray. The color gets you to the gray drawer, and then the real work starts: finding one shape among every gray part you own. Your eye picks a color out of a pile of identical shapes almost instantly. It’s much slower at picking one shape out of a pile of the same color, and the more you own, the slower it gets.
You’ll still color-sort some things. A small collection. A display build. A few bins you can take in at a glance. Just don’t mistake a beautiful wall for a system that knows where the 1×2 plates are.
2. Sort by part type
Sorting by part type is the sensible default, and the one most builders settle on. Bricks with bricks, plates with plates, tiles with tiles. It matches the way parts lists and marketplaces group pieces, and it uses the thing your eye is good at: in a drawer of 1×2 plates, the dark bluish gray ones stand out.
It holds until the categories have to get honest. Is a bracket a plate? Does a 1×1 round plate go with the plates, or with the rounds? Every system has those arguments, and they multiply as the collection grows. “Plates” stops being one drawer and becomes six, and you still have to remember which of the six got the 1×2s.
Then there’s the long tail: hinges, windscreens, printed parts you don’t want scratched, the three of something you bought for one build. They land in a miscellaneous bin. It starts as a shortcut and becomes the place parts go to die. Sorting by type is still the right default. It tells you the family. It doesn’t tell you the box.
3. Sort by set
Keeping each set in its own box is the lowest-effort option, and it’s the right one if you rebuild sets rather than parting them out. The inventory is the box. The instructions are in the box. You open one thing and you’re building.
Most collections don’t stay that way. You borrow a handful of plates for your own build, then a few more for another, and the set box is no longer the set. Sorting by set assumes the parts go back where they came from. They rarely do.
Even when the sets stay intact, a part you need for something else means remembering which set it came in, or opening several big boxes to check. That makes set boxes a good archive and a poor parts library. They work as long as you build one set at a time. The day you start mixing, the labels describe a collection you no longer have.
4. Type, then color
A lot of builders end up here without naming it. Sort by type, then split by color — but only the parts you own in huge numbers. All the 2×4 bricks in one drawer. The 1×2 plates split across three or four drawers by color, because you own so many that one drawer would be a dig.
The extra split pays only where the count justifies another container. Do it for every part and the number of drawers explodes, and every new purchase can mean a new subdivision. Setting it up is slow. Keeping it current is slower.
Used sparingly, this is as organized as a sorted collection gets. It’s still a refinement of sorting by type, not a map. The rare parts still share a bin, and you’re still the one remembering which shade of gray earned its own drawer.
5. Sort less, index more
The fifth method changes the question. Instead of asking how finely to sort, you ask how to answer one thing fast: which container do I open?
Parts go into fewer, larger bins, sorted only broadly — by type is plenty. Each bin gets a short code on its label, like B4. The code names the bin, not what’s in it, so the day you move parts around you don’t relabel a wall of drawers. Then you keep a list you can search: the part, and the code of the bin it’s in. A spreadsheet can do it. The difference from sorting by type isn’t the bins. It’s that where things are is written down instead of remembered.
The list is the whole method, and it’s also where the method usually fails. Writing it all down on sorting day is easy. Keeping it current three months later, while parts move between builds, is the part most people give up on.
When it works, it fails in the open. A sorted wall can look right while your memory of it goes stale. An index that says B4 when the part is in B7 gets caught the first time you look, and you fix one line. You still dig inside a bin. You stop opening ten of them to find out which one to dig in.
The first four methods are the right answer while you can hold the whole system in your head. Indexing starts to matter when you can’t — more containers than you can picture, more than one cupboard, new parts every month. Call it done when you can put your hand on a named part in about thirty seconds, not when the shelves look tidy.
| Method | Best when | Where it breaks | Finding one part |
|---|---|---|---|
| By color | You build by eye, or the collection is small | One shape among every part of the same color | Right drawer, then a long dig |
| By part type | Most builders, most collections | Vague categories and the miscellaneous bin | Right family, then which drawer? |
| By set | You rebuild sets instead of parting them out | The first build that borrows parts | Easy, if it’s still in its set |
| Type, then color | A few shapes you own in bulk | Splitting everything, until the drawers run out | Fast, if you remember the splits |
| Broad bins and an index | The collection has outgrown your memory | You stop updating the list | Look it up, open one bin |
There isn’t one winner. Color is satisfying to look at. Type is the practical default. Set boxes are honest if you rebuild sets. The hybrid shows up on its own once a few parts get out of hand. What the first four share is that they rely on you remembering, and memory is what fades between one project and the next.
So judge your system by the moment that matters: a half-built model on the table, one part missing, and the question of which box to open. A tidy shelf helps with that. A written-down answer helps more. That record is the part I’m building an app for.