Analyze any schematic
Drop a .litematic, .schem, .nbt or .mcstructure file to see what is inside it, and whether it matches a build already published on Shulkr.
Your file is parsed in your browser and never uploaded. Only a small, non-reversible fingerprint (a few kilobytes of hashes) is sent to check for matches.
Private by design
Parsing happens in your browser. Your file never leaves your device; only a tiny fingerprint is sent.
Checked against Shulkr
The fingerprint is compared with every public schematic in the catalog: exact copies, close matches and builds contained in one another.
Full material list
Every block type in the build, counted and sorted, with required mods detected automatically.
How the similarity check works
Your file is read locally
The schematic is parsed in your browser, the same way the viewer and converter do it. Dimensions, block counts, the material list and required mods all come straight from the file's own data.
A fingerprint is computed, not an upload
For every block, the analyzer hashes its 3×3×3 neighborhood and keeps a small sample of those hashes. The sample describes how the build is shaped and what it is made of, but it cannot be turned back into the build, and it ignores where the build sits and which way it faces.
The fingerprint is compared with the catalog
The sample is scored against the fingerprints of every public schematic on Shulkr. Sharing most hashes reads as a close match; a one-sided overlap means one build appears inside the other; byte-identical builds are recognized exactly. The same detection powers the related-builds credits on schematic pages.
About analyzing schematics
Is my schematic uploaded?
No. The file is parsed on your device. Only the fingerprint, a few kilobytes of hash values, is sent to run the database check, and it cannot be reversed into your build.
How does the similarity check work?
Every block's local neighborhood is hashed, and a sampled set of those hashes forms the build's fingerprint. Two fingerprints that share most of their hashes describe builds with mostly the same structure. The comparison ignores position and rotation, and it looks at shape and materials separately, so a copy in different blocks can still match.
What do the results mean?
Identical means the exact same build, block for block. Closely matches means most of the structure is shared. Contains and appears within mean one build shows up inside the other, like a farm module inside a full base.
Can I check if my build was reposted?
Yes. Drop your original file and the analyzer lists published Shulkr builds that closely match it. The check only sees public schematics, and it detects structural similarity, not authorship, so treat a match as a lead to look into rather than proof.
Which formats are supported?
Litematica (.litematic), WorldEdit and Sponge (.schem), vanilla structure blocks (.nbt) and Bedrock (.mcstructure). Modded blocks are read fine and show up as required mods.