Skip to content
SCRAPMECHWIKI · 1.0 Database

CURRENT 1.0 BLUEPRINT FORMAT

Blueprint BOM Analyzer

Open a Scrap Mechanic blueprint to count its exact blocks, parts, joints, controllers, paint colors, and stored contents. The file stays in your browser.

Open a blueprint

Local only

Choose a .blueprint file exported by Scrap Mechanic or a compatible blueprint.json file. Analysis starts immediately in this browser.

Drop a blueprint file here

1,155 released files validate against this parser. Largest released file: 2.5 MB. Site safety limit: 8 MB.

Your file is read locally by this page. It is not uploaded, stored, or sent to scrapmech.wiki.

Or paste blueprint JSON

Paste the complete JSON exported by the game. It is processed by the same local parser and never submitted.

BLUEPRINT FILE GUIDE

Understand a Scrap Mechanic blueprint bill of materials

A blueprint file describes placed shapes and their structure. The analyzer turns that structure into an exact shape-count bill of materials, but it deliberately does not pretend that the result is a Survival crafting cost or a physics simulation.

BOM units are not the same as placement records

The released shape-count rule contributes 1 for each joint, 1 for each unbounded child, and bounds.x × bounds.y × bounds.z for a bounded block child. A 2 × 3 × 4 block record therefore contributes 24 units even though it is one child record.

This distinction explains why a creation can have a modest number of JSON records but a large block total. The report shows placements and calculated units separately so neither number is mislabeled.

What the parser validates before showing a result

The parser accepts released blueprint formats 2, 3, and 4, checks the body, child, joint, bounds, color, controller, and multi-shape structures, and classifies identities against 1,337 packaged or reviewed shapes. Unknown or modded identities stay counted and are labeled rather than silently discarded.

Validation was tested against 1,155 parseable files shipped with the current release, containing 212,466 child records. That corpus is a compatibility test set; it is not a claim that every Workshop mod uses a public game identity.

Stored items, controllers, paint, and multi-shape parts

Container contents are cargo already stored inside the creation, so they are listed separately and excluded from the build BOM. Paint colors describe placements and do not create extra material rows. Controller records are counted structurally, while opaque serialized controller payloads are not decoded into invented behavior.

A packaged object can contain internal multi-shape components that do not have separate player-facing item pages. The analyzer preserves that structural evidence and labels it instead of presenting an internal UUID as a craftable item.

What this tool cannot infer from a blueprint file

The game’s engine-side Survival blueprint-cost implementation is not present in the released scripts. The analyzer therefore does not claim an exact crafting-resource cost, placement legality, missing-mod resolution, center of mass, stability, collision behavior, or whether a creation will function after spawning.

Use the BOM to audit what the file contains. Use the crafting planner only after you have translated the relevant recognized parts into actual Survival acquisition goals.

Move from file structure to item research

Inspect recognized partsOpen public item pages for names, modes, properties, recipes, and variants.Plan craftable partsCalculate current recipe materials for the Survival goals you choose.Review the evidence policySee why engine-only cost, physics, and opaque data remain outside exact claims.

Blueprint rules and corpus figures were verified against game version 1.0.0.867; selected files are parsed locally in the browser and are not uploaded.