Parts Export
LEGO Mosaic Parts List Generator
A parts list is where a mosaic idea becomes a real project. BMBrick treats the parts list as a planning output tied to the selected size, material style, route, and palette, not as a separate spreadsheet you have to rebuild manually.
Direct Answer
BMBrick generates route-specific mosaic parts files alongside the PDF build plan for 3024 square plates or 98138 round tiles: PAB CSV/JSON when official element IDs are available, Webrick CSV/manual notes for compatible sourcing, BrickLink XML inventory, and a structure BOM CSV.
Best For
Builders who already have a photo and need quantities, colors, routes, and export files before buying parts.
Main Risk
A weak crop can create an expensive parts list for background detail that does not improve the finished mosaic.
Best Companion
Use the photo and generator pages first if the project image is still unstable.
How the workflow works
01 - Stabilize the image
Confirm crop and Magic Cut decisions before treating the count as final.
02 - Choose material style
Part style changes color availability, route cost, and surface character.
03 - Select route
Compare supported route estimates before deciding which export file is most useful.
04 - Export and review
Download the route file and verify quantities before sourcing physical parts.
Parts list export comparison
Each export format exists for a different sourcing workflow.
| Route | File type | Best use | Important limitation |
|---|---|---|---|
| LEGO Pick a Brick | CSV and JSON | Official-route planning | Only colors with verified official data can be exported cleanly |
| Webrick | CSV and manual notes | Compatible-route planning | Some colors require manual page ordering notes |
| BrickLink | XML | Marketplace inventory upload | Final seller availability still changes outside BMBrick |
| Structure | BOM CSV | Base/support planning | Depends on the selected mosaic size and structure settings |
Why route-specific lists matter
A single universal parts list sounds convenient, but real sourcing routes do not behave the same way. PAB, Webrick, and BrickLink use different identifiers, availability assumptions, and purchasing workflows.
BMBrick keeps those differences visible so a builder can understand what the file is for. That matters for searchers who arrive with buying intent: they need a sourceable list, not only a color summary.
- Use PAB exports for official-route planning.
- Use Webrick exports when compatible-route sourcing is acceptable.
- Use BrickLink XML when marketplace inventory workflows are the priority.
How to avoid a bloated parts list
The cheapest parts list is usually created before the export step. Tight crop, subject isolation, and a realistic size choice do more to control cost than small post-export edits.
Use Magic Cut and crop review before locking a file. If the background is not carrying emotional or visual value, it is often better to remove or skip it before the count becomes final.
FAQ
Can I upload the parts list directly to BrickLink?
BMBrick can export BrickLink XML inventory data, which is designed for BrickLink-style upload workflows.
Does BMBrick buy the bricks for me?
No. BMBrick produces planning and export files. Physical parts are purchased separately through the chosen sourcing route.
Does the list include quantities?
Yes. The exports are based on the selected mosaic and include color and quantity data for the route workflow.
Can I change the image after exporting?
You should treat exports as tied to one confirmed project state. Changing crop, size, material, or palette changes the parts list.
Where To Go Next
Next reads: